linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Steven Cole <scole@lanl.gov>
To: Steven Cole <elenstev@mesatop.com>
Cc: Andrew Morton <akpm@zip.com.au>, linux-mm@kvack.org
Subject: Re: 2.5.44-mm2 CONFIG_SHAREPTE necessary for starting KDE 3.0.3
Date: 22 Oct 2002 11:20:36 -0600	[thread overview]
Message-ID: <1035307236.13083.183.camel@spc9.esa.lanl.gov> (raw)
In-Reply-To: <1035306108.13078.178.camel@spc9.esa.lanl.gov>

On Tue, 2002-10-22 at 11:01, Steven Cole wrote:
> Greetings all,
> 
> My experience with 2.5.44-mm2 and KDE 3 runs counter to the experience
> of some others.  I've booted several kernels this morning on my UP test
> box and found that starting KDE 3.0.3 using XFree86 4.2.1 _requires_
> that CONFIG_SHAREPTE=y for my system.  All kernels were UP and PREEMPT.
> With CONFIG_X86_UP_IOAPIC=y and nmi_watchdog=1, the results were the
> same.
> 
> If SHAREPTE is not set, then the KDE startup fails with a frozen pointer
> after the initial dark blue screen changes to black.  This does appear
> to be KDE-related.  When Gnome is my default desktop, that works just
> fine with 2.5.44-mm2 and CONFIG_SHAREPTE not set.
> 

After reading my own mail, I realized that I should have checked to see
if disabling PREEMPT did any good in this case. 

I just booted 2.5.44-mm2 without PREEMPT and without SHAREPTE, and KDE
3.0.3 was able to start up OK.

Steven  

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

  reply	other threads:[~2002-10-22 17:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-22 17:01 Steven Cole
2002-10-22 17:20 ` Steven Cole [this message]
2002-10-22 18:10   ` Robert Love
2002-10-22 19:02     ` Steven Cole
2002-10-22 21:51     ` Ed Tomlinson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1035307236.13083.183.camel@spc9.esa.lanl.gov \
    --to=scole@lanl.gov \
    --cc=akpm@zip.com.au \
    --cc=elenstev@mesatop.com \
    --cc=linux-mm@kvack.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox