From: Keith Busch <kbusch@kernel.org>
To: Ming Lei <ming.lei@redhat.com>
Cc: davidc502 <davidc502@tds.net>,
linux-block@vger.kernel.org, ilnux-nvme@lists.infradead.org
Subject: Re: fstrim error - AORUS NVMe Gen4 SSD
Date: Wed, 24 Jul 2019 15:30:54 -0600 [thread overview]
Message-ID: <20190724213054.GA5921@localhost.localdomain> (raw)
In-Reply-To: <20190723043803.GB13829@ming.t460p>
On Tue, Jul 23, 2019 at 12:38:04PM +0800, Ming Lei wrote:
> From the IO trace, discard command(nvme_cmd_dsm) is failed:
>
> kworker/15:1H-462 [015] .... 91814.342452: nvme_setup_cmd: nvme0: disk=nvme0n1, qid=7, cmdid=552, nsid=1, flags=0x0, meta=0x0, cmd=(nvme_cmd_dsm nr=0, attributes=4)
> <idle>-0 [013] d.h. 91814.342708: nvme_complete_rq: nvme0: disk=nvme0n1, qid=7, cmdid=552, res=0, retries=0, flags=0x0, status=8198
>
> And the returned error code is 0x8198, I am not sure how to parse the
> 'Command Specific Status Values' of 0x98, maybe Christoph, Keith or our other
> NVMe guys can help to understand the failure.
The 198h status code is still marked reserved in the latest spec for an
NVM command set, so not sure what to make of it. I think we would have
to refer back to the vendor.
next prev parent reply other threads:[~2019-07-24 21:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-21 2:41 fstrim error - AORUS NVMe Gen4 SSD davidc502
[not found] ` <4b76413b-1af4-a406-5b16-6789b2b7012a@tds.net>
2019-07-23 0:06 ` davidc502
2019-07-23 2:19 ` Ming Lei
[not found] ` <4a7ec7aa-f6ee-f9dc-4a17-38f2b169c721@tds.net>
2019-07-23 4:38 ` Ming Lei
2019-07-23 21:38 ` davidc502
2019-07-23 21:56 ` davidc502
2019-07-24 1:45 ` Ming Lei
2019-07-24 21:30 ` Keith Busch [this message]
2019-07-26 13:26 ` davidc502
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=20190724213054.GA5921@localhost.localdomain \
--to=kbusch@kernel.org \
--cc=davidc502@tds.net \
--cc=ilnux-nvme@lists.infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.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