[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20210521173125.GC29013@redsun51.ssa.fujisawa.hgst.com>
Date: Sat, 22 May 2021 02:31:25 +0900
From: Keith Busch <kbusch@...nel.org>
To: "Verma, Vishal L" <vishal.l.verma@...el.com>
Cc: "hch@....de" <hch@....de>,
"Williams, Dan J" <dan.j.williams@...el.com>,
"Schofield, Alison" <alison.schofield@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>,
"Weiny, Ira" <ira.weiny@...el.com>,
"Widawsky, Ben" <ben.widawsky@...el.com>
Subject: Re: [BISECTED] nvme probe failure with v5.13-rc1
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.
Powered by blists - more mailing lists