From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: cw@f00f.org (Chris Wedgwood)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox),
marcelo@conectiva.com.br (Marcelo Tosatti),
chris@freedom2surf.net, linux-kernel@vger.kernel.org
Subject: Re: Repeatable Oops in 2.4t13p4ac2
Date: Fri, 29 Dec 2000 01:52:07 +0000 (GMT) [thread overview]
Message-ID: <E14BoiI-0004ch-00@the-village.bc.nu> (raw)
In-Reply-To: <20001229144609.B16930@metastasis.f00f.org> from "Chris Wedgwood" at Dec 29, 2000 02:46:09 PM
> 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.
The PCMCIA thing is unlikely to be related (there are no changes on any PCMCIA
that actually worked on 13pre4). Reiserfs might be the trigger because the
quota code changed, but if it did touch it I'd expect it to have failed
to compile
> This is totally repeatable so if you want further diagnostics please
> let me know....
I'm going to go and do a detailed audit of the mm bits I have differing from
Linus. For one I'd be much happier to differ in drivers with Linus and avoid
differing in mm/vm internals stuff.
Alan
-
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:21 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
2000-12-29 1:52 ` Alan Cox [this message]
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=E14BoiI-0004ch-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=chris@freedom2surf.net \
--cc=cw@f00f.org \
--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®