From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jens Axboe <axboe@fb.com>
Cc: Jan Kara <jack@suse.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Brian J King <bjking1@us.ibm.com>
Subject: Re: [BUG] kernel BUG at /.../block/cfq-iosched.c:3145!
Date: Thu, 10 Apr 2014 13:35:37 +1000 [thread overview]
Message-ID: <1397100937.3671.160.camel@pasglop> (raw)
In-Reply-To: <5346012A.50901@fb.com>
On Wed, 2014-04-09 at 20:25 -0600, Jens Axboe wrote:
> On 2014-04-09 19:36, Benjamin Herrenschmidt wrote:
> > On Wed, 2014-04-09 at 19:31 -0600, Jens Axboe wrote:
> >> OK, I think we're seeing different symptoms of the same bug. Stay
> >> tuned, will have something for you to test shortly, I hope.
> >
> > Ah thanks. I'll defer the bisection then (it's painful on that machine
> > for various reasons....)
>
> Can you try with these two patches applied?
Booted to login prompt once ... and twice. Much better ! :-)
Thanks a lot !
Not sure if it's related, but in the "good" boots (with the patch),
I see a truckload of:
systemd-udevd[3264]: starting version 204
sr 2:6:0:0: [sr0]
Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sr 2:6:0:0: [sr0]
Sense Key : Illegal Request [current]
sr 2:6:0:0: [sr0]
Add. Sense: Logical block address out of range
sr 2:6:0:0: [sr0] CDB:
Read(10): 28 00 00 00 00 00 00 00 01 00
end_request: critical target error, dev sr0, sector 0
Buffer I/O error on device sr0, logical block 0
[ OK ] Started udev Kernel Device Manager.
sr 2:6:0:0: [sr0]
Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sr 2:6:0:0: [sr0]
Sense Key : Illegal Request [current]
sr 2:6:0:0: [sr0]
Add. Sense: Logical block address out of range
sr 2:6:0:0: [sr0] CDB:
etc...
I might have a crap coaster in that drive. It doesn't prevent
the machine from working otherwise, so far...
Cheers,
Ben.
next prev parent reply other threads:[~2014-04-10 3:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 4:44 [BUG] kernel BUG at /.../block/cfq-iosched.c:3145! Benjamin Herrenschmidt
2014-04-09 13:35 ` Jens Axboe
2014-04-09 23:47 ` Benjamin Herrenschmidt
2014-04-10 0:02 ` Benjamin Herrenschmidt
2014-04-10 1:31 ` Jens Axboe
2014-04-10 1:36 ` Benjamin Herrenschmidt
2014-04-10 1:38 ` Jens Axboe
2014-04-10 2:25 ` Jens Axboe
2014-04-10 3:35 ` Benjamin Herrenschmidt [this message]
2014-04-10 3:52 ` Jens Axboe
2014-04-10 6:45 ` Benjamin Herrenschmidt
2014-04-10 13:47 ` Jens Axboe
2014-04-10 18:10 ` 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=1397100937.3671.160.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=axboe@fb.com \
--cc=bjking1@us.ibm.com \
--cc=fweisbec@gmail.com \
--cc=jack@suse.cz \
--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 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.