From: Christoph Hellwig <hch@lst.de>
To: "J. Hart" <jfhart085@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>,
linux-nvme@lists.infradead.org, kbusch@kernel.org, axboe@fb.com,
sagi@grimberg.me
Subject: Re: nvme nvme0: I/O 0 (I/O Cmd) QID 1 timeout, aborting, source drive corruption observed
Date: Thu, 15 Dec 2022 10:09:41 +0100 [thread overview]
Message-ID: <20221215090941.GA5062@lst.de> (raw)
In-Reply-To: <d4c4eea9-e573-df0c-cca5-536bcff6c0a9@gmail.com>
On Thu, Dec 15, 2022 at 06:07:32PM +0900, J. Hart wrote:
> My apologies....I am not sure what is meant by "stay DMAs". Is there
> something I can look for here ?
I mean stray, sorry. There isn't really anything you can look for.
Either it really is a device problem, in which case the IOMMU should
catch it. Or it is a kernel problem somewhere, in which case
CONFIG_KASAN would catch. So maybe enable that as well, but it will
slow down the kernel a LOT.
next prev parent reply other threads:[~2022-12-15 9:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 1:38 nvme nvme0: I/O 0 (I/O Cmd) QID 1 timeout, aborting, source drive corruption observed J. Hart
2022-12-15 8:23 ` Christoph Hellwig
2022-12-15 9:07 ` J. Hart
2022-12-15 9:09 ` Christoph Hellwig [this message]
2022-12-15 9:15 ` J. Hart
2022-12-15 13:33 ` J. Hart
2022-12-15 17:34 ` Keith Busch
2022-12-15 22:30 ` J. Hart
2022-12-16 6:39 ` Christoph Hellwig
2022-12-16 19:08 ` Keith Busch
2023-01-18 10:27 ` Mark Ruijter
2022-12-16 23:16 ` Keith Busch
2022-12-17 1:28 ` J. Hart
2022-12-19 14:41 ` Keith Busch
2022-12-20 1:10 ` J. Hart
2022-12-20 16:56 ` Keith Busch
2022-12-21 7:50 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2022-12-17 12:07 J. Hart
2022-12-17 15:07 J. Hart
2022-12-17 16:14 J. Hart
2022-12-17 21:57 J. Hart
2022-12-18 6:20 J. Hart
2022-12-18 12:08 J. Hart
2022-12-19 14:45 ` Keith Busch
2022-12-19 23:40 ` J. Hart
2022-12-20 18:10 ` Keith Busch
2022-12-20 14:04 ` J. Hart
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=20221215090941.GA5062@lst.de \
--to=hch@lst.de \
--cc=axboe@fb.com \
--cc=jfhart085@gmail.com \
--cc=kbusch@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.