From: Jens Axboe <axboe@fb.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
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 12:10:57 -0600 [thread overview]
Message-ID: <5346DEB1.4050507@fb.com> (raw)
In-Reply-To: <1397112333.3671.179.camel@pasglop>
On 04/10/2014 12:45 AM, Benjamin Herrenschmidt wrote:
> On Wed, 2014-04-09 at 21:52 -0600, Jens Axboe wrote:
>> On 2014-04-09 21:35, Benjamin Herrenschmidt wrote:
>>> 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 ! :-)
>>
>> Excellent! I was hoping it was the same bug :-)
>> I'll amend the commit and add your tested-by.
>
> A colleague was complaining of yet another oddball block related crash
> today on another machine when doing rsync's with upstream (this machine
> booted fine but crashed later on, but then it has less CPUs... maybe
> that's relevant) and these patches fixed it too.
Pull request is now in, jfyi.
--
Jens Axboe
prev parent reply other threads:[~2014-04-10 18:11 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
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 [this message]
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=5346DEB1.4050507@fb.com \
--to=axboe@fb.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=benh@kernel.crashing.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox