All of lore.kernel.org
 help / color / mirror / Atom feed
From: "George Spelvin" <linux@horizon.com>
To: jaxboe@fusionio.com, linux-raid@vger.kerne.org,
	linux-scsi@vger.kernel.org
Cc: linux@horizon.com
Subject: Re: [BUG raid1] kernel BUG at drivers/scsi/scsi_lib.c:1113
Date: 27 Sep 2010 07:08:42 -0400	[thread overview]
Message-ID: <20100927110842.2601.qmail@science.horizon.com> (raw)

Has this bug been merged?  I'm getting a boot-time BUG referencing this
line in a raid1 task with 2.6.36-rc5, and I thought the fix had been
merged in.

At least, 2c7d46ec192e4f2b350f67a0e185b9bce646cd6b looks looks like
the fix, but I have that in my kernel (which, to be absolutely clear,
is b30a3f6257ed2105259b404d419b4964e363928c plus a few unrelated local
patches that I just manually reviewed to make absolutely certain),
and I'm still exploding on boot.

If someone would like the full error message, I can find a camera to take
a picture of the screen.

Thanks!

             reply	other threads:[~2010-09-27 11:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-27 11:08 George Spelvin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-08-17 22:09 [BUG raid1] kernel BUG at drivers/scsi/scsi_lib.c:1113 Mathieu Desnoyers
2010-08-17 22:09 ` Mathieu Desnoyers
2010-08-17 22:13 ` Jiri Slaby
2010-08-17 22:31   ` Mathieu Desnoyers
2010-08-18 11:42     ` Jiri Slaby
2010-08-18 14:32       ` James Bottomley
2010-08-18 14:36         ` Jiri Slaby
2010-08-18 14:41           ` James Bottomley
2010-08-18 21:49             ` Jens Axboe
2010-08-18 22:50               ` James Bottomley
2010-08-19  2:59                 ` Jens Axboe
2010-08-19 14:52                   ` James Bottomley
2010-08-19 15:11                     ` Gene Heskett
2010-08-23  9:01                     ` Jens Axboe
2010-08-23 17:08                       ` James Bottomley
2010-08-23 17:18                         ` 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=20100927110842.2601.qmail@science.horizon.com \
    --to=linux@horizon.com \
    --cc=jaxboe@fusionio.com \
    --cc=linux-raid@vger.kerne.org \
    --cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.