From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at buffer.c:827! and scsi modules no load at boot w/ initrd - test12pre7
Date: 7 Dec 2000 14:19:40 -0800 [thread overview]
Message-ID: <90p2ds$2hs$1@penguin.transmeta.com> (raw)
In-Reply-To: <3A2FF076.946076FC@haque.net>
In article <3A2FF076.946076FC@haque.net>,
Mohammad A. Haque <mhaque@haque.net> wrote:
>
>I'm getting a BUG at boot in buffer.c:827. Oops/ksymoops at teh end of
>this message. I also noticed that the driver for my scsi card isn't
>loading at boot if compiled as a module using initrd. This is what I get
>during the boot process.
This is a new BUG-check, where "UnlockPage()" actually verifies that the
page was locked before it unlocks it.
Trying to unlock a page that isn't locked is a nasty bug - if it happens
it probably also means that with some bad luck that unlock could have
unlocked the page that somebody _else_ had locked, and expected to stay
locked until it was unlocked properly.
(It may also be that the BUG() is due to exactly that - somebody else
who didn't have the lock unlocked the page from under you, and the
_proper_ unlocker will in that case be the one that oopses).
Do you have something special that triggers this? Can you test if it
only happens with initrd, for example?
Linus
-
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-07 22:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-07 20:17 kernel BUG at buffer.c:827! and scsi modules no load at boot w/ initrd - test12pre7 Mohammad A. Haque
2000-12-07 22:19 ` Linus Torvalds [this message]
2000-12-07 22:54 ` Mohammad A. Haque
2000-12-08 2:52 ` Mohammad A. Haque
2000-12-10 23:16 ` Mohammad A. Haque
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='90p2ds$2hs$1@penguin.transmeta.com' \
--to=torvalds@transmeta.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