From: Jens Axboe <axboe@suse.de>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: William Lee Irwin III <wli@holomorphy.com>,
Ivan Gyurdiev <ivg2@cornell.edu>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: kernel BUG at include/linux/blkdev (2.5.70)
Date: Wed, 28 May 2003 08:11:36 +0200 [thread overview]
Message-ID: <20030528061136.GH845@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.50.0305280130160.15323-100000@montezuma.mastecende.com>
On Wed, May 28 2003, Zwane Mwaikambo wrote:
> On Tue, 27 May 2003, William Lee Irwin III wrote:
>
> > On Tue, May 27, 2003 at 11:23:29PM -0400, Ivan Gyurdiev wrote:
> > > Out of nowhere on mozilla open (after it worked fine all afternoon):
> > > ------------[ cut here ]------------
> > > kernel BUG at include/linux/blkdev.h:408!
> > > invalid operand: 0000 [#1]
> > > CPU: 0
> > > EIP: 0060:[<c02322be>] Tainted: P
> > > EFLAGS: 00010046
> > > EIP is at blk_queue_start_tag+0x8e/0x100
> >
> > This appears to be tainted by a proprietary module. Please reproduce
> > without it or forward the bugreport to the originator of the module.
>
> Looks valid;
>
> We tried to remove the previous request.. but there was none. The BUG
> check looks odd (what happens to the first tag?)
Previous request, what are you talking about?
do_ide_request()
ide_do_request()
start_request(drive, rq); /* this rq is _never_ off the list */
__ide_do_rw_disk(drive, rq);
idedisk_start_tag(drive, rq);
blkdev_dequeue_request(rq); /* boom */
It does _not_ look valid.
--
Jens Axboe
next prev parent reply other threads:[~2003-05-28 5:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-28 3:23 kernel BUG at include/linux/blkdev (2.5.70) Ivan Gyurdiev
2003-05-28 5:29 ` William Lee Irwin III
2003-05-28 5:38 ` Zwane Mwaikambo
2003-05-28 5:52 ` William Lee Irwin III
2003-05-28 6:11 ` Jens Axboe [this message]
2003-05-28 6:16 ` Zwane Mwaikambo
2003-05-28 6:30 ` Jens Axboe
2003-05-28 6:08 ` Jens Axboe
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=20030528061136.GH845@suse.de \
--to=axboe@suse.de \
--cc=ivg2@cornell.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.com \
--cc=zwane@linuxpower.ca \
/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