From: Chris Wedgwood <cw@f00f.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
chris@freedom2surf.net, linux-kernel@vger.kernel.org
Subject: Re: Repeatable Oops in 2.4t13p4ac2
Date: Fri, 29 Dec 2000 14:46:09 +1300 [thread overview]
Message-ID: <20001229144609.B16930@metastasis.f00f.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0012281305530.12295-100000@freak.distro.conectiva> <E14BghF-0003wu-00@the-village.bc.nu>
In-Reply-To: <E14BghF-0003wu-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Thu, Dec 28, 2000 at 05:18:30PM +0000
On Thu, Dec 28, 2000 at 05:18:30PM +0000, Alan Cox wrote:
For -ac Im working on the assumption I introduced a bug into the
mm code
after discussion with you and further pounding with t13p4+cw (not ac)
I am fairly confident something in ac2 is fishy. I can repeatable get
ac2 to fail with PCMCIA and also reiserfs under load, I absolutely
cannot get these failures without ac2.
This is totally repeatable so if you want further diagnostics please
let me know....
--cw
P.S. Using 2.95.2 if that matters; it's more or less always works but
maybe ac2 triggers something there as some people seem to find
ac2 pretty good?
-
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-12-29 2:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-28 13:20 chris
2000-12-28 11:56 ` Marcelo Tosatti
2000-12-28 15:48 ` Alan Cox
2000-12-28 14:36 ` Marcelo Tosatti
2000-12-28 16:45 ` Alan Cox
2000-12-28 15:06 ` Marcelo Tosatti
2000-12-28 17:18 ` Alan Cox
2000-12-28 18:08 ` chris
2000-12-28 16:31 ` Marcelo Tosatti
2000-12-29 1:46 ` Chris Wedgwood [this message]
2000-12-29 1:52 ` Alan Cox
2000-12-29 1:56 ` Chris Wedgwood
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=20001229144609.B16930@metastasis.f00f.org \
--to=cw@f00f.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=chris@freedom2surf.net \
--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
all inboxes | Powered by JetHome®