All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@kernel.org>
To: "Verma, Vishal L" <vishal.l.verma@intel.com>
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>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	"Weiny, Ira" <ira.weiny@intel.com>,
	"Widawsky, Ben" <ben.widawsky@intel.com>
Subject: Re: [BISECTED] nvme probe failure with v5.13-rc1
Date: Sat, 22 May 2021 02:31:25 +0900	[thread overview]
Message-ID: <20210521173125.GC29013@redsun51.ssa.fujisawa.hgst.com> (raw)
In-Reply-To: <e8ad9de961f3bfcb748733b59c189aa577ffa1fd.camel@intel.com>

On Fri, May 21, 2021 at 04:50:15PM +0000, Verma, Vishal L wrote:
> 
> Thanks for looking into it - yes with that the problem goes away.
> Let me chat with the simics folks and see if I can get them to fix it.

Thanks for confirming. It sounds like the simics implementation is
missing a default case in its identify function's CNS check and simply
loses track of the command. I'd wager it probably also times out for any
reserved or unsupported CNS value.

WARNING: multiple messages have this Message-ID (diff)
From: Keith Busch <kbusch@kernel.org>
To: "Verma, Vishal L" <vishal.l.verma@intel.com>
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>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	"Weiny, Ira" <ira.weiny@intel.com>,
	"Widawsky, Ben" <ben.widawsky@intel.com>
Subject: Re: [BISECTED] nvme probe failure with v5.13-rc1
Date: Sat, 22 May 2021 02:31:25 +0900	[thread overview]
Message-ID: <20210521173125.GC29013@redsun51.ssa.fujisawa.hgst.com> (raw)
In-Reply-To: <e8ad9de961f3bfcb748733b59c189aa577ffa1fd.camel@intel.com>

On Fri, May 21, 2021 at 04:50:15PM +0000, Verma, Vishal L wrote:
> 
> Thanks for looking into it - yes with that the problem goes away.
> Let me chat with the simics folks and see if I can get them to fix it.

Thanks for confirming. It sounds like the simics implementation is
missing a default case in its identify function's CNS check and simply
loses track of the command. I'd wager it probably also times out for any
reserved or unsupported CNS value.

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

  reply	other threads:[~2021-05-21 17:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-21  5:00 [BISECTED] nvme probe failure with v5.13-rc1 Verma, Vishal L
2021-05-21  5:00 ` 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 [this message]
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=20210521173125.GC29013@redsun51.ssa.fujisawa.hgst.com \
    --to=kbusch@kernel.org \
    --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=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=vishal.l.verma@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 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.