All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "kbusch@kernel.org" <kbusch@kernel.org>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Cc: "hch@lst.de" <hch@lst.de>,
	"Williams, Dan J" <dan.j.williams@intel.com>,
	"Schofield, Alison" <alison.schofield@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Weiny, Ira" <ira.weiny@intel.com>,
	"Widawsky, Ben" <ben.widawsky@intel.com>
Subject: [BISECTED] nvme probe failure with v5.13-rc1
Date: Fri, 21 May 2021 05:00:29 +0000	[thread overview]
Message-ID: <40071b11108987556d0473f9d968fe7dcd3f304a.camel@intel.com> (raw)

Hi,

I ran into this failure to probe an nvme device in an emulator
(simics). It looks like there is a ~60 second wait followed by a
timeout and a failure to boot (the root device is an nvme disk) with
these messages in the log:

   [   67.174010] nvme nvme0: I/O 5 QID 0 timeout, disable controller
   [   67.175793] nvme nvme0: Removing after probe failure status: -4

I bisected this to:
   5befc7c26e5a ("nvme: implement non-mdts command limits") 

It's not immediately obvious to me what's causing the problem.
Reverting the above commit fixes it. It is easily reproducible - I'd be
happy to provide more info about the emulated device or test out
patches or theories.

It is of course possible that the emulated device is behaving in some
non spec-compliant way, in which case I'd appreciate any help figuring
out what that is.

Thanks,
-Vishal

WARNING: multiple messages have this Message-ID (diff)
From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "kbusch@kernel.org" <kbusch@kernel.org>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Cc: "hch@lst.de" <hch@lst.de>,
	"Williams, Dan J" <dan.j.williams@intel.com>,
	"Schofield, Alison" <alison.schofield@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Weiny, Ira" <ira.weiny@intel.com>,
	"Widawsky, Ben" <ben.widawsky@intel.com>
Subject: [BISECTED] nvme probe failure with v5.13-rc1
Date: Fri, 21 May 2021 05:00:29 +0000	[thread overview]
Message-ID: <40071b11108987556d0473f9d968fe7dcd3f304a.camel@intel.com> (raw)

Hi,

I ran into this failure to probe an nvme device in an emulator
(simics). It looks like there is a ~60 second wait followed by a
timeout and a failure to boot (the root device is an nvme disk) with
these messages in the log:

   [   67.174010] nvme nvme0: I/O 5 QID 0 timeout, disable controller
   [   67.175793] nvme nvme0: Removing after probe failure status: -4

I bisected this to:
   5befc7c26e5a ("nvme: implement non-mdts command limits") 

It's not immediately obvious to me what's causing the problem.
Reverting the above commit fixes it. It is easily reproducible - I'd be
happy to provide more info about the emulated device or test out
patches or theories.

It is of course possible that the emulated device is behaving in some
non spec-compliant way, in which case I'd appreciate any help figuring
out what that is.

Thanks,
-Vishal
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

             reply	other threads:[~2021-05-21  5:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-21  5:00 Verma, Vishal L [this message]
2021-05-21  5:00 ` [BISECTED] nvme probe failure with v5.13-rc1 Verma, Vishal L
2021-05-21 14:57 ` Keith Busch
2021-05-21 14:57   ` Keith Busch
2021-05-21 16:50   ` Verma, Vishal L
2021-05-21 16:50     ` Verma, Vishal L
2021-05-21 17:31     ` Keith Busch
2021-05-21 17:31       ` Keith Busch

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=40071b11108987556d0473f9d968fe7dcd3f304a.camel@intel.com \
    --to=vishal.l.verma@intel.com \
    --cc=alison.schofield@intel.com \
    --cc=ben.widawsky@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=hch@lst.de \
    --cc=ira.weiny@intel.com \
    --cc=kbusch@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    /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.