From: keith.busch@intel.com (Keith Busch)
Subject: nvme drive kernel 5.0 problem
Date: Tue, 21 May 2019 16:00:07 -0600 [thread overview]
Message-ID: <20190521220007.GB4302@localhost.localdomain> (raw)
In-Reply-To: <e027eae2-0c39-8e83-5a09-fda82d4c2a52@chavero.com.mx>
On Tue, May 21, 2019@04:34:44PM -0500, Iv?n Chavero wrote:
> I think that the real error is this one:
>
> print_req_error: operation not supported error, dev nvme0n1, sector
> 386138112 flags 4801
Weird. There are not very many statuses that translate to a "not
supported" from nvme, and none of them really make sense for a device
to return only during early boot. Let's see if that error is coming
from the drive or somewhere else.
Could you append the following kernel parameter:
trace_event=nvme_setup_cmd,nvme_complete_rq
Then get the output from after the errors?
cat /sys/kernel/debug/tracing/trace
next prev parent reply other threads:[~2019-05-21 22:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 0:20 nvme drive kernel 5.0 problem Iván Chavero
2019-05-16 3:57 ` Ming Lei
2019-05-16 5:50 ` Iván Chavero
2019-05-20 22:12 ` Iván Chavero
2019-05-21 14:20 ` Keith Busch
2019-05-21 21:34 ` Iván Chavero
2019-05-21 22:00 ` Keith Busch [this message]
2019-05-22 0:50 ` Iván Chavero
2019-05-22 1:53 ` Minwoo Im
2019-06-29 16:56 ` Iván Chavero
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=20190521220007.GB4302@localhost.localdomain \
--to=keith.busch@intel.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