public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Cole <elenstev@mesatop.com>
To: 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: Mon, 27 Nov 2000 21:32:40 -0700	[thread overview]
Message-ID: <00112721324000.01098@localhost.localdomain> (raw)

Alan Cox wrote:
>
>> For what its worth, on my single processor home machine, all kernels
>> 2.4.0-test11-ac1,ac2,ac3, ac4 both UP and SMP run both Gnome and
>> KDE 2.0, with reiserfs-3.6.19.  In other words, everything works with
>> everything.
>
>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

Agreed.  I suspect that this could be a rough spot with reiserfs-3.6.19.
I observed one similar freezup while doing
tar zxvf linux-2.4.0-test11.tar.gz 
while running 2.4.0-test11-pre7, patched with reiserfs-3.6.19.

I and others have experienced some off-normal behaviour with 
reiserfs, like crashing when saving a file on top of itself with StarOffice
5.2 when the file was on an NFS server.  That particular bug
was fixed in reiserfs-3.6.14, IIRC.  But even with the few rough edges, 
reiserfs has become essential to our operations, with its ability to recover
so quickly after a UPS has caused problems.  That's why I'm following the
2.4.0 development so closely with reiserfs.

I was never able to reproduce the tar freeze.  The freeze which I
observed with test11-ac2,4 SMP and KDE 2.0 was very reproducable; I saw
it at least 6 times, always in exactly the same place of the startup of
KDE 2.0.

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.

Meanwhile, 2.4.0-test12-pre2 patched with reiserfs-3.6.19 is running
nicely with KDE 2.0 on the uniprocessor home machine.

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/

             reply	other threads:[~2000-11-28  5:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-28  4:32 Steven Cole [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-11-27 20:01 2.4.0-test11-ac2 and ac4 SMP will not run KDE 2.0 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

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=00112721324000.01098@localhost.localdomain \
    --to=elenstev@mesatop.com \
    --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