From: Sasha Levin <sasha.levin@oracle.com>
To: axboe@fb.com
Cc: LKML <linux-kernel@vger.kernel.org>, Dave Jones <davej@redhat.com>
Subject: blk-mq: WARN at block/blk-mq.c:585 __blk_mq_run_hw_queue
Date: Wed, 07 May 2014 11:37:16 -0400 [thread overview]
Message-ID: <536A532C.4050001@oracle.com> (raw)
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()
[ 986.964364] Modules linked in:
[ 986.964996] CPU: 41 PID: 41607 Comm: kworker/u147:1 Not tainted 3.15.0-rc4-next-20140506-sasha-00021-gc164334-dirty #447
[ 986.967025] Workqueue: kblockd blk_mq_run_work_fn
[ 986.967939] 0000000000000009 ffff8802410e1c68 ffffffff94536f8a 0000000000000001
[ 986.970333] 0000000000000000 ffff8802410e1ca8 ffffffff9115febc ffffffff91183ef7
[ 986.973173] ffff8801b478ef60 0000000000000000 ffff8802410e1ce8 ffff8801b3f07978
[ 986.975749] Call Trace:
[ 986.976700] dump_stack (lib/dump_stack.c:52)
[ 986.978875] warn_slowpath_common (kernel/panic.c:430)
[ 986.981924] ? process_one_work (kernel/workqueue.c:2224)
[ 986.984245] warn_slowpath_null (kernel/panic.c:465)
[ 986.986670] __blk_mq_run_hw_queue (arch/x86/include/asm/bitops.h:311 (discriminator 65) block/blk-mq.c:587 (discriminator 65))
[ 986.989000] ? process_one_work (include/linux/workqueue.h:186 kernel/workqueue.c:611 kernel/workqueue.c:638 kernel/workqueue.c:2220)
[ 986.991584] ? get_parent_ip (kernel/sched/core.c:2485)
[ 986.994168] blk_mq_run_work_fn (block/blk-mq.c:777)
[ 986.996379] process_one_work (kernel/workqueue.c:2227 include/linux/jump_label.h:105 include/trace/events/workqueue.h:111 kernel/workqueue.c:2232)
[ 986.998641] ? process_one_work (include/linux/workqueue.h:186 kernel/workqueue.c:611 kernel/workqueue.c:638 kernel/workqueue.c:2220)
[ 987.001352] worker_thread (kernel/workqueue.c:2354)
[ 987.003676] ? rescuer_thread (kernel/workqueue.c:2303)
[ 987.006703] kthread (kernel/kthread.c:210)
[ 987.009161] ? kthread_create_on_node (kernel/kthread.c:176)
[ 987.012536] ret_from_fork (arch/x86/kernel/entry_64.S:553)
[ 987.015272] ? kthread_create_on_node (kernel/kthread.c:176)
Thanks,
Sasha
next reply other threads:[~2014-05-07 15:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 15:37 Sasha Levin [this message]
2014-05-07 15:45 ` blk-mq: WARN at block/blk-mq.c:585 __blk_mq_run_hw_queue Jens Axboe
2014-05-07 15:53 ` Sasha Levin
2014-05-07 15:55 ` Jens Axboe
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=536A532C.4050001@oracle.com \
--to=sasha.levin@oracle.com \
--cc=axboe@fb.com \
--cc=davej@redhat.com \
--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