From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: NeilBrown <neilb@suse.de>
Cc: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
linux-raid@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: raid1d crash at boot
Date: Mon, 21 Nov 2011 08:04:30 +0100 [thread overview]
Message-ID: <1321859070.3654.7.camel@dabdike> (raw)
In-Reply-To: <20111121123729.47c72c3b@notabene.brown>
On Mon, 2011-11-21 at 12:37 +1100, NeilBrown wrote:
> Thank for the report.
> However as this crash is clearly in the SCSI layer it makes sense to reported
> it to linux-scsi - so I have cc:ed this reply there.
>
> NeilBrown
>
>
> On Sat, 19 Nov 2011 14:41:39 +0100 Michał Mirosław <mirq-linux@rere.qmqm.pl>
> wrote:
>
> > I get following BUG_ON tripped while booting, before rootfs is mounted by
> > Debian's initrd. This started to happen for kernels since sometime
> > during 3.1-rcX.
> >
> > [ 6.246170] ------------[ cut here ]------------
> > [ 6.246246] kernel BUG at /mnt/src-tmp/jaja/git/qmqm/drivers/scsi/scsi_lib.c:1153!
I can tell you what it is:
/*
* Filesystem requests must transfer data.
*/
BUG_ON(!req->nr_phys_segments);
But the fault is in the layer above SCSI. It means something sent a
request with REQ_TYPE_FS but no actual data attached ... this is
supposed to be impossible, hence the bug on.
James
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-11-21 7:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111119134139.GA30570@rere.qmqm.pl>
2011-11-21 1:37 ` raid1d crash at boot NeilBrown
2011-11-21 7:04 ` James Bottomley [this message]
2011-11-21 8:27 ` NeilBrown
2011-11-22 0:50 ` Michał Mirosław
2011-11-22 1:26 ` NeilBrown
2011-11-22 12:03 ` Michał Mirosław
2011-11-22 12:10 ` Michał Mirosław
2012-01-07 12:53 ` Michał Mirosław
2012-01-09 1:35 ` NeilBrown
2012-01-09 20:30 ` Michał Mirosław
2012-01-05 21:30 raid 1 bug with write-mostly and administrative failed disk Art -kwaak- van Breemen
2012-01-05 21:39 ` Art -kwaak- van Breemen
2012-01-06 21:41 ` Art -kwaak- van Breemen
2012-01-09 1:34 ` NeilBrown
2012-01-09 13:25 ` Art -kwaak- van Breemen
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=1321859070.3654.7.camel@dabdike \
--to=james.bottomley@hansenpartnership.com \
--cc=linux-raid@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mirq-linux@rere.qmqm.pl \
--cc=neilb@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).