From: Steven Cole <scole@lanl.gov>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.0-test11-ac2 and ac4 SMP will not run KDE 2.0
Date: Tue, 28 Nov 2000 09:03:38 -0700 [thread overview]
Message-ID: <00112809033800.01270@spc.esa.lanl.gov> (raw)
In-Reply-To: <E140UaD-0003ZI-00@the-village.bc.nu>
In-Reply-To: <E140UaD-0003ZI-00@the-village.bc.nu>
Alan Cox wrote:
>
>Nod. It actually puzzles me since from the kernel view I doubt kde and gnome
>even look different at the syscall level. They may look different to X but
>X isnt the thing that changed
Steven Cole wrote:
>
>Tomorrow when I have access to the two-way P-III problem machine,
>I'll repatch 2.4.0-test11-ac4 with reiserfs-3.6.18,
>which is a little less bleeding edge than reiserfs-3.6.19.
2.4.0-test11-ac2 still freezes starting up KDE 2.0 when patched
with reiserfs-3.6.18.
2.4.0-test12-pre2 both SMP and UP builds also freeze when starting
up KDE 2.0 on this dual cpu box. Those test12-pre2 kernels are
patched with reiserfs-3.6.19.
I guess I'll have to switch over to using Gnome if I want to continue
using kernels later than 2.4.0-test11-ac1 and ReiserFS on this dual
P-III Dell 420.
Can someone else please see if this is reproducable?
The ingredients are:
Dual CPU P-III.
2.4.0-test11-ac2 or later (test12-pre2)
SMP build for -acX. (X > 1).
ReiserFS 3.6.18 or 3.6.19.
KDE 2.0
Thanks very much.
Steven
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-28 16:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-27 20:01 Steven Cole
2000-11-27 20:08 ` Alan Cox
2000-11-27 23:23 ` Steven Cole
2000-11-28 0:55 ` Alan Cox
2000-11-28 16:03 ` Steven Cole [this message]
2000-11-28 4:32 Steven Cole
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=00112809033800.01270@spc.esa.lanl.gov \
--to=scole@lanl.gov \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®