[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <MEAP282MB0391131326CF9E3BD5C26FD0B338A@MEAP282MB0391.AUSP282.PROD.OUTLOOK.COM>
Date: Tue, 18 Jul 2023 02:10:18 +0000
From: Sean Wang <wangxiao@...mail.it>
To: Keith Busch <kbusch@...nel.org>
CC: "highenthalpyh@...il.com" <highenthalpyh@...il.com>,
"axboe@...nel.dk" <axboe@...nel.dk>, "hch@....de" <hch@....de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>,
"sagi@...mberg.me" <sagi@...mberg.me>,
"xuwd1@...mail.com" <xuwd1@...mail.com>
Subject: Re: [PATCH] nvme-pci: add NVME_QUIRK_DELAY_BEFORE_CHK_RDY for MAXIO
MAP1602
Could you please point out which patch in 6.5-rc2 for such devices? Thanks
Sent from my mobile device.
> 在 2023年7月17日,16:03,Keith Busch <kbusch@...nel.org> 写道:
>
> On Mon, Jul 17, 2023 at 07:41:26AM +0000, Sean Wang wrote:
>> My two SSDs are from different companies, but they all use MaxIO 1602 nvme controllers.
>>
>> After applying this patch, they could work.
>>
>> Otherwise, here is a workaround to make live cd to recognize these SSDs:
>>
>>
>> echo “1” > /sys/bus/pci/devices/0000:02:00.0/remove
>> sleep 1
>> echo “1” > /sys/bus/pci/rescan
>>
>> Where device id (02:00.0) could be found via
>>
>> lspci -nn -d ::0108
>
> We have a generic solution for such devices as of 6.5-rc2 so it should
> work now; however, it's still recommended to get devices with this
> behavior in the quirk list in order to ensure that the we get udev to
> generate deterministic symlinks. Since this controller is used by
> multiple vendors, though, it's unclear if this quirk applies to all
> variations.
Powered by blists - more mailing lists