From: Yi Zhang <yi.zhang@redhat.com>
To: Chaitanya Kulkarni <chaitanyak@nvidia.com>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
Keith Busch <kbusch@kernel.org>
Subject: Re: [bug report] nvme removing after probe failed with pci rescan after nvme sysfs removal
Date: Wed, 22 Sep 2021 19:21:30 +0800 [thread overview]
Message-ID: <CAHj4cs-hrSkU-8RS5zqeZpFkZP9zd+7emdOtmMNAm+e4LeVc7w@mail.gmail.com> (raw)
In-Reply-To: <a214017f-8287-f281-b296-3424aba0131b@nvidia.com>
On Wed, Sep 22, 2021 at 10:32 AM Chaitanya Kulkarni
<chaitanyak@nvidia.com> wrote:
>
> On 9/21/21 6:56 PM, Yi Zhang wrote:
> > Hello
> >
> > I found this issue during the nvme removal test, I did some debug code
> > found it was failed during nvme "CSTS – Controller Status" read, could
> > anyone help check if this is one HW or SW issue?
> >
> >
>
> One easiest way to isolate this issue is to test the steps on the QEMU
> NVMe ctrl and update everyone here...
Hi Chaitanya
I tried another NVMe SSD[1], and it works well, seems this is special
for "Samsung SSD 983 DCT 960GB".
And the kernel I used was upstream 5.15.0-rc2.
[1]
# nvme list
Node SN Model
Namespace Usage Format FW Rev
---------------- --------------------
---------------------------------------- ---------
-------------------------- ---------------- --------
/dev/nvme2n1 3080A09HTAFR Dell Express Flash CD5 960G SFF
1 469.18 MB / 960.20 GB 512 B + 0 B 1.2.0
--
Best Regards,
Yi Zhang
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-09-22 11:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210922020425uscas1p22ca979458bbbb94c243af890bdca04b6@uscas1p2.samsung.com>
2021-09-22 1:56 ` [bug report] nvme removing after probe failed with pci rescan after nvme sysfs removal Yi Zhang
2021-09-22 2:32 ` Chaitanya Kulkarni
2021-09-22 11:21 ` Yi Zhang [this message]
2021-09-23 6:52 ` Chaitanya Kulkarni
2021-09-22 2:33 ` Chaitanya Kulkarni
2021-09-23 16:54 ` Adam Manzanares
2021-09-24 2:33 ` Yi Zhang
2021-09-24 19:16 ` Adam Manzanares
2021-09-24 3:13 ` Keith Busch
2021-09-26 11:14 ` Yi Zhang
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=CAHj4cs-hrSkU-8RS5zqeZpFkZP9zd+7emdOtmMNAm+e4LeVc7w@mail.gmail.com \
--to=yi.zhang@redhat.com \
--cc=chaitanyak@nvidia.com \
--cc=kbusch@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).