From: Andrew Morton <akpm@digeo.com>
To: Lawrence Walton <lawrence@the-penguin.otak.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: OOPs report
Date: Wed, 28 May 2003 15:53:42 -0700 [thread overview]
Message-ID: <20030528155342.45d1e437.akpm@digeo.com> (raw)
In-Reply-To: <20030528151620.GA21579@the-penguin.otak.com>
Lawrence Walton <lawrence@the-penguin.otak.com> wrote:
>
> Hello all I have a oops report, happened overnight don't know why,
> other then it looks devfs related.
>
> ..
> kernel BUG at include/linux/list.h:140!
yes, sorry. -mm has extra list_head debugging goodies, and they detect
bugs in devfs.
We're still hoping to do something radical with devfs but if that doesn't
happen then we'll need to plug this bug somehow.
If it's a problem then you can just delete the two BUG_ON's from
include/linux/list.h:list_del().
next prev parent reply other threads:[~2003-05-28 22:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-28 15:16 OOPs report Lawrence Walton
2003-05-28 22:53 ` Andrew Morton [this message]
2003-05-28 23:05 ` Dave Jones
2003-05-28 23:55 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2009-01-02 8:42 OOPS report Daryl Radivojevic
2009-01-05 10:04 ` Oliver Neukum
2005-09-27 19:09 David J. M. Karlsen
2003-05-26 18:35 Oops report Petro
2003-01-25 17:05 Asher Yanich
2001-12-27 20:51 Mark Hindley
2000-12-22 10:48 Bill K.
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=20030528155342.45d1e437.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=lawrence@the-penguin.otak.com \
--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