From: "marc. h." <heckmann@hbe.ca>
To: Andrew Morton <akpm@zip.com.au>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
linux-kernel@vger.kernel.org
Subject: Re: [problem captured] Re: cerberus on 2.4.17-rc2 UP
Date: Wed, 16 Jan 2002 11:35:17 +0100 [thread overview]
Message-ID: <20020116113516.D4627@hbe.ca> (raw)
In-Reply-To: <20020108164816.A5453@hbe.ca> <E16Nysp-0006tn-00@the-village.bc.nu> <3C3B579D.7B8E534F@zip.com.au>
In-Reply-To: <3C3B579D.7B8E534F@zip.com.au>; from akpm@zip.com.au on Tue, Jan 08, 2002 at 12:33:33PM -0800
ok, the ext3-2.4-0.9.17 patch fixes this bug. thank you. that means that
2.4.17-rc2 with the patch applied makes it through a full *double* cerberus run
succesfully. I also tried the same with ext2 and it made it through as well. I
plan to try and 18-preX as well soon. If only such a test wasn't a day and a
half long...
The only other thing that seems to effecting a lot of people (including a
friend of mine) that I can't re-produce here, is the OOPses... A box that was
stable with 2.4.12 oops'es in short time with 2.4.1[67]. The box in question is
a Dell desktop running a netfilter firewall.
-m
On Tue, Jan 08, 2002 at 12:33:33PM -0800, Andrew Morton wrote:
> Alan Cox wrote:
> >
> > Other people have reported it too. Its clearly a kernel race
>
> Yes, I can generate it at will on two quite different IDE machines
> with the run-bash-shared-mapping script from
> http://www.zip.com.au/~akpm/ext3-tools.tar.gz
>
> It's on my list of things-to-do, filed under "hard". It even happens
> on uniprocessor, with unmask_irq=0.
>
> Interestingly, I _think_ it only ever occurs against the
> swap device. But I need to confirm this. Marc, do you
> have swap on /dev/hda1?
>
--
C3C5 9226 3C03 CDF7 2EF1 029F 4CAD FBA4 F5ED 68EB
key: http://people.hbesoftware.com/~heckmann/
next prev parent reply other threads:[~2002-01-16 10:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-20 12:59 cerberus on 2.4.17-rc2 UP marc. h.
2001-12-21 16:56 ` Marcelo Tosatti
2001-12-22 20:22 ` Marc Heckmann
2002-01-07 11:14 ` marc. h.
2002-01-08 15:48 ` [problem captured] " marc. h.
2002-01-08 16:13 ` Alan Cox
2002-01-08 20:33 ` Andrew Morton
2002-01-08 21:05 ` Alex Scheele
2002-01-09 9:37 ` marc. h.
2002-01-16 10:35 ` marc. h. [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-08 22:15 Manfred Spraul
2002-01-09 9:04 ` Andrew Morton
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=20020116113516.D4627@hbe.ca \
--to=heckmann@hbe.ca \
--cc=akpm@zip.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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