From: Keith Busch <kbusch@kernel.org>
To: andreas.thalhammer@linux.com
Cc: linux-nvme@lists.infradead.org, Jens Axboe <axboe@fb.com>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>
Subject: Re: Bug 216809 - nvme nvme0: I/O 0 (I/O Cmd) QID 1 timeout, aborting
Date: Fri, 13 Oct 2023 08:32:30 -0600 [thread overview]
Message-ID: <ZSlU_kQOtpyQEJK0@kbusch-mbp> (raw)
In-Reply-To: <4933a8ea-56d4-4094-b9fd-bc16fc5dd920@gmx.net>
On Fri, Oct 13, 2023 at 03:25:37AM +0200, Andreas Thalhammer wrote:
> I'd like to make you aware of
> Bug 216809 - nvme nvme0: I/O 0 (I/O Cmd) QID 1 timeout, aborting
>
> https://bugzilla.kernel.org/show_bug.cgi?id=216809
>
> I personally don't see the reported errors AND system freeze on my own
> systems, but the reporters do, which are:
> jfhart085@gmail.com
> Nelson G <konoha02@yahoo.com>
Does the device just stop responding entirely, or is it just reponding
exceptionally slowly? Output from something like "iostat -X 1" that
includes the period timeouts occur would be useful to see what workload
is being thrown at the device, and how it is handling it.
If the device is responding very slowly, suggestions I might have
include:
a. Enable discards if you've disabled them
b. Disable discards if you've enabled them
c. If not already enabled, use an io scheduler, like mq-deadline or kyber
If the device isn't responding at all, which appears to be the case in
one of the dmesg's from the bz, then suggestion is report a bug to the
device vendor.
prev parent reply other threads:[~2023-10-13 14:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 1:25 Bug 216809 - nvme nvme0: I/O 0 (I/O Cmd) QID 1 timeout, aborting Andreas Thalhammer
2023-10-13 14:32 ` Keith Busch [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=ZSlU_kQOtpyQEJK0@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=andreas.thalhammer@linux.com \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--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