From: Keith Busch <kbusch@kernel.org>
To: Andreas Hindborg <a.hindborg@kernel.org>
Cc: Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [bug report] nvme: fio workload hangs on 16m random read
Date: Thu, 6 Mar 2025 13:51:11 -0700 [thread overview]
Message-ID: <Z8oKvwPd4UBY1awm@kbusch-mbp> (raw)
In-Reply-To: <87a59x6g5u.fsf@kernel.org>
On Thu, Mar 06, 2025 at 09:46:37PM +0100, Andreas Hindborg wrote:
> Hi All,
>
> My CI system has found an issue for the following fio workload:
>
> root@debian:~# insmod /mnt/v6.14-rc5-build/drivers/nvme/host/nvme-core.ko
> root@debian:~# insmod /mnt/v6.14-rc5-build/drivers/nvme/host/nvme.ko poll_queues=1
>
> "fio" "--group_reporting" "--name=default" "--filename=/dev/nvme0n1"
> "--readwrite=randread" "--blocksize=16777216" "--direct=1" "--numjobs=1"
> "--ioengine=io_uring" "--iodepth=1" "--hipri=1" "--time_based=1"
> "--runtime=3000"
>
> fio will hang, some times immediately, some times after a few minutes.
>
> I observed this on v6.14-rc1 and v6.14-rc5. It is not present in v6.13.
>
> Can any of you reproduce this? I was able to reproduce this on real
> hardware and in qemu.
Could you try adding this patch to your kernel?
https://lore.kernel.org/io-uring/92b0a330-4782-45e9-8de7-3b90a94208c2@kernel.dk/
next prev parent reply other threads:[~2025-03-06 20:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 20:46 [bug report] nvme: fio workload hangs on 16m random read Andreas Hindborg
2025-03-06 20:51 ` Keith Busch [this message]
2025-03-07 7:51 ` Andreas Hindborg
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=Z8oKvwPd4UBY1awm@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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