From: SungHwan Jung <onenowy@gmail.com>
To: hch@lst.de
Cc: Jason@zx2c4.com, abhijeet.rao@intel.com, alan.adamson@oracle.com,
axboe@fb.com, kbusch@kernel.org, linux-kernel@vger.kernel.org,
linux-nvme@lists.infradead.org, monish.kumar.r@intel.com,
pankydev8@gmail.com, sagi@grimberg.me, yi.zhang@redhat.com
Subject: Re: 2 second nvme initialization delay regression in 5.18 [Was: Re: [bug report]nvme0: Admin Cmd(0x6), I/O Error (sct 0x0 / sc 0x2) MORE DNR observed during blktests]
Date: Mon, 20 Jun 2022 13:34:02 +0900 [thread overview]
Message-ID: <20220620043402.13202-1-onenowy@gmail.com> (raw)
In-Reply-To: <20220615113106.GA10697@lst.de>
Hi again,
I'm sorry to send mail again.
I think it would be to confirm that subsystem-ids for all X5 model and these ids are not used for other ssd by contact with samsung.
But I have no idea how to contant with them, please fowards this to them or if you already have these information, please tests the patch in previous mail.
next prev parent reply other threads:[~2022-06-20 4:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHj4cs_iC+FE8ZAXXZPeia1V3ZX7zRbeASdOP_8c7DLiFozNfA@mail.gmail.com>
2022-04-05 20:00 ` [bug report]nvme0: Admin Cmd(0x6), I/O Error (sct 0x0 / sc 0x2) MORE DNR observed during blktests Jason A. Donenfeld
2022-04-05 20:48 ` Alan Adamson
2022-06-09 8:20 ` 2 second nvme initialization delay regression in 5.18 [Was: Re: [bug report]nvme0: Admin Cmd(0x6), I/O Error (sct 0x0 / sc 0x2) MORE DNR observed during blktests] Jason A. Donenfeld
2022-06-09 8:34 ` Jason A. Donenfeld
2022-06-09 8:40 ` [PATCH] Revert "nvme-pci: add quirks for Samsung X5 SSDs" Jason A. Donenfeld
2022-06-09 9:32 ` 2 second nvme initialization delay regression in 5.18 [Was: Re: [bug report]nvme0: Admin Cmd(0x6), I/O Error (sct 0x0 / sc 0x2) MORE DNR observed during blktests] R, Monish Kumar
2022-06-09 9:38 ` Jason A. Donenfeld
2022-06-10 6:14 ` Christoph Hellwig
2022-06-10 9:19 ` Jason A. Donenfeld
2022-06-13 6:36 ` R, Monish Kumar
2022-06-13 12:20 ` Jason A. Donenfeld
2022-06-13 13:02 ` R, Monish Kumar
2022-06-13 13:55 ` Christoph Hellwig
2022-06-15 10:27 ` Pankaj Raghav
2022-06-15 11:31 ` Christoph Hellwig
2022-06-20 3:36 ` onenowy
2022-06-20 7:09 ` Christoph Hellwig
2022-06-20 4:34 ` SungHwan Jung [this message]
2022-06-10 12:05 ` Pankaj Raghav
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=20220620043402.13202-1-onenowy@gmail.com \
--to=onenowy@gmail.com \
--cc=Jason@zx2c4.com \
--cc=abhijeet.rao@intel.com \
--cc=alan.adamson@oracle.com \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=monish.kumar.r@intel.com \
--cc=pankydev8@gmail.com \
--cc=sagi@grimberg.me \
--cc=yi.zhang@redhat.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