From: Ed Tomlinson <tomlins@cam.org>
To: Robert Love <rml@tech9.net>, Steven Cole <scole@lanl.gov>
Cc: Steven Cole <elenstev@mesatop.com>,
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: Tue, 22 Oct 2002 17:51:21 -0400 [thread overview]
Message-ID: <200210221751.21283.tomlins@cam.org> (raw)
In-Reply-To: <1035310234.1044.1480.camel@phantasy>
On October 22, 2002 02:10 pm, Robert Love wrote:
> On Tue, 2002-10-22 at 13:20, Steven Cole wrote:
> > 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.
>
> Let me clarify, because this is odd...
>
> CONFIG_PREEMPT + CONFIG_SHAREPTE => OK
>
> CONFIG_PREEMPT + !CONFIG_SHAREPTE => KDE crashes
>
> !CONFIG_PREEMPT + !CONFIG_SHAREPTE => OK
>
> Right?
>
> Sounds like a timing issue to me. Any other errors? It is possible to
> get a trace?
>
> This sounds familiar, so do not think too hard without double
> checking... someone else reported failure with KDE.
Yes, I have been reporting problems since day one. Also sent a few
straces which seem not to have help much. In my case:
CONFIG_PREEMPT + CONFIG_SHAREPTE => Fail
CONFIG_PREEMPT !CONFIG_SHAREPTE => Works
Fun huh?
Ed Tomlinson
--
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/
prev parent reply other threads:[~2002-10-22 21:51 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
2002-10-22 18:10 ` Robert Love
2002-10-22 19:02 ` Steven Cole
2002-10-22 21:51 ` Ed Tomlinson [this message]
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=200210221751.21283.tomlins@cam.org \
--to=tomlins@cam.org \
--cc=akpm@zip.com.au \
--cc=elenstev@mesatop.com \
--cc=linux-mm@kvack.org \
--cc=rml@tech9.net \
--cc=scole@lanl.gov \
/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