From: Jens Axboe <axboe@fb.com>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Dave Jones <davej@redhat.com>
Subject: Re: blk-mq: WARN at block/blk-mq.c:585 __blk_mq_run_hw_queue
Date: Wed, 7 May 2014 09:55:16 -0600 [thread overview]
Message-ID: <536A5764.4020606@fb.com> (raw)
In-Reply-To: <536A56E4.5020909@oracle.com>
On 05/07/2014 09:53 AM, Sasha Levin wrote:
> On 05/07/2014 11:45 AM, Jens Axboe wrote:
>> On 05/07/2014 09:37 AM, Sasha Levin wrote:
>>> Hi all,
>>>
>>> While fuzzing with trinity inside a KVM tools guest running the latest -next
>>> kernel I've stumbled on the following spew:
>>>
>>> [ 986.962569] WARNING: CPU: 41 PID: 41607 at block/blk-mq.c:585 __blk_mq_run_hw_queue+0x90/0x500()
>>
>> I'm going to need more info than this. What were you running? How as kvm
>> invoked (nr cpus)?
>
> Sure!
>
> It's running in a KVM tools guest (not qemu), with the following options:
>
> '--rng --balloon -m 28000 -c 48 -p "numa=fake=32 init=/virt/init zcache ftrace_dump_on_oops debugpat kvm.mmu_audit=1 slub_debug=FZPU rcutorture.rcutorture_runnable=0 loop.max_loop=64 zram.num_devices=4 rcutorture.nreaders=8 oops=panic nr_hugepages=1000 numa_balancing=enable'.
>
> So basically 48 vcpus (the host has 128 physical ones), and ~28G of RAM.
>
> I've been running trinity as a fuzzer, which doesn't handle logging too well,
> so I can't reproduce it's actions easily.
>
> There was an additional stress of hotplugging CPUs and memory during this recent
> fuzzing run, so it's fair to suspect that this happened as a result of that.
Aha!
> Anything else that might be helpful?
No, not too surprising given the info that cpu hotplug was being
stressed at the same time. blk-mq doesn't quiesce when this happens, so
it's very unlikely that there are races between updating the cpu masks
and flushing out the previously queued work.
next prev parent reply other threads:[~2014-05-07 15:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 15:37 blk-mq: WARN at block/blk-mq.c:585 __blk_mq_run_hw_queue Sasha Levin
2014-05-07 15:45 ` Jens Axboe
2014-05-07 15:53 ` Sasha Levin
2014-05-07 15:55 ` Jens Axboe [this message]
2014-05-09 3:22 ` Sasha Levin
2014-05-09 3:27 ` Jens Axboe
2014-05-09 12:12 ` Shaohua Li
2014-05-09 14:22 ` 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=536A5764.4020606@fb.com \
--to=axboe@fb.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sasha.levin@oracle.com \
/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