From: Jens Axboe <axboe@kernel.dk>
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Cc: Damien Le Moal <Damien.LeMoal@wdc.com>
Subject: Re: [bug report] block/005 hangs with NVMe device and linux-block/for-next
Date: Mon, 1 Nov 2021 06:41:19 -0600 [thread overview]
Message-ID: <30d7ccec-c798-3936-67bd-e66ae59c318b@kernel.dk> (raw)
In-Reply-To: <20211101083417.fcttizyxpahrcgov@shindev>
On 11/1/21 2:34 AM, Shinichiro Kawasaki wrote:
> I tried the latest linux-block/for-next branch tip (git hash b43fadb6631f and
> observed a process hang during blktests block/005 run on a NVMe device.
> Kernel message reported "INFO: task check:1224 blocked for more than 122
> seconds." with call trace [1]. So far, the hang is 100% reproducible with my
> system. This hang is not observed with HDDs or null_blk devices.
>
> I bisected and found the commit 4f5022453acd ("nvme: wire up completion batching
> for the IRQ path") triggers the hang. When I revert this commit from the
> for-next branch tip, the hang disappears. The block/005 test case does IO
> scheduler switch during IO, and the completion path change by the commit looks
> affecting the scheduler switch. Comments for solution will be appreciated.
I'll take a look at this.
--
Jens Axboe
next prev parent reply other threads:[~2021-11-01 12:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 8:34 [bug report] block/005 hangs with NVMe device and linux-block/for-next Shinichiro Kawasaki
2021-11-01 12:41 ` Jens Axboe [this message]
2021-11-01 23:01 ` Jens Axboe
2021-11-02 2:22 ` Shinichiro Kawasaki
2021-11-02 3:07 ` Chaitanya Kulkarni
2021-11-02 8:19 ` Shinichiro Kawasaki
2021-11-02 8:28 ` Damien Le Moal
2021-11-02 3:44 ` Ming Lei
2021-11-02 8:28 ` Shinichiro Kawasaki
2021-11-02 9:02 ` Shinichiro Kawasaki
2021-11-02 10:48 ` Ming Lei
2021-11-02 11:24 ` Shinichiro Kawasaki
2021-11-02 12:26 ` Ming Lei
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=30d7ccec-c798-3936-67bd-e66ae59c318b@kernel.dk \
--to=axboe@kernel.dk \
--cc=Damien.LeMoal@wdc.com \
--cc=linux-block@vger.kernel.org \
--cc=shinichiro.kawasaki@wdc.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