| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <MEAP282MB039184E1E94BC16523846876B33CA@MEAP282MB0391.AUSP282.PROD.OUTLOOK.COM>
Date: Sat, 22 Jul 2023 14:42:22 +0000
From: Sean Wang <wangxiao@...mail.it>
To: Josh Taylor <joshuataylorx@...il.com>
CC: "axboe@...nel.dk" <axboe@...nel.dk>, "hch@....de" <hch@....de>,
"highenthalpyh@...il.com" <highenthalpyh@...il.com>,
"kbusch@...nel.org" <kbusch@...nel.org>,
"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
Try latest Manjaro(install with ISO and update the system with around 2GB downloads). That worked for me to recognize my both MAP1602 SSDs: Aigo P7000z and Fanxiang S790.
Sent from my mobile device.
> 在 2023年7月22日，22:08，Josh Taylor <joshuataylorx@...il.com> 写道：
>
> This is my first response to a Kernel patch, so I apologise for any formatting weirdness.
>
> I have a Lexar NM790 (4TB), which uses the MAP1602. It looks like this is going to be a fairly popular controller, as it seems a few are using it - as of July 2023 it looks like ~18 M.2 2280 are using it according to techpowerup (https://www.techpowerup.com/ssd-specs/?f&controllerMfgr=Maxiotech#MAP1602).
>
> I however cannot get this patch to work for me on 6.5-rc2 on ArchLinux, nor with 6.4.4.
>
> This is my dmesg when booting (Linux archiso 6.3.9-arch1-1):
>
>
> [ 6.634874] nvme nvme0: pci function 0000:01:00.0
> [ 6.640698] r8169 0000:27:00.0: enabling device (0000 -> 0003)
> [ 6.643601] nvme nvme0: Device not ready; aborting initialisation, CSTS=0x0
>
>
> When doing a suspend, then resuming, I can then re-initialise the device using the rescan steps in the previous email.
>
> I then get this in my dmesg (Linux archiso 6.3.9-arch1-1):
>
>
> [ 130.948667] pci 0000:01:00.0: Removing from iommu group 14
> [ 131.983938] pci 0000:01:00.0: [1d97:1602] type 00 class 0x010802
> [ 131.983963] pci 0000:01:00.0: reg 0x10: [mem 0xfcf00000-0xfcf03fff 64bit]
> [ 131.984212] pci 0000:01:00.0: 31.504 Gb/s available PCIe bandwidth, limited by 8.0 GT/s PCIe x4 link at 0000:00:01.1 (capable of 63.012 Gb/s with 16.0 GT/s PCIe x4 link)
> [ 131.984346] pci 0000:01:00.0: Adding to iommu group 14
> [ 132.031556] pci 0000:01:00.0: BAR 0: assigned [mem 0xfcf00000-0xfcf03fff 64bit]
> [ 132.031662] nvme nvme0: pci function 0000:01:00.0
> [ 132.044095] nvme nvme0: allocated 40 MiB host memory buffer.
> [ 132.088892] nvme nvme0: 16/0/0 default/read/poll queues
>
>
> The "allocated 40 MiB host memory buffer" part is interesting, none of my other drives have this, as this is a DRAM-less drive.
>
> # nvme get-feature /dev/nvme0 -f 0x0c -H
> get-feature:0x0c (Autonomous Power State Transition), Current value:0x00000001
> Autonomous Power State Transition Enable (APSTE): Enabled
> Auto PST Entries .................
> Entry[ 0]
> .................
> Idle Time Prior to Transition (ITPT): 100 ms
> Idle Transition Power State (ITPS): 3
> .................
> Entry[ 1]
> .................
> Idle Time Prior to Transition (ITPT): 100 ms
> Idle Transition Power State (ITPS): 3
> .................
> Entry[ 2]
> .................
> Idle Time Prior to Transition (ITPT): 100 ms
> Idle Transition Power State (ITPS): 3
> .................
> Entry[ 3]
> .................
> Idle Time Prior to Transition (ITPT): 2000 ms
> Idle Transition Power State (ITPS): 4
> .................
> Entry[ 4]
> .................
> Idle Time Prior to Transition (ITPT): 0 ms
> Idle Transition Power State (ITPS): 0
> .................
> Entry[ 5]
> .................
> Idle Time Prior to Transition (ITPT): 0 ms
> Idle Transition Power State (ITPS): 0
> .................
> Entry[ 6]
> .................
> Idle Time Prior to Transition (ITPT): 0 ms
> Idle Transition Power State (ITPS): 0
> .................
> Entry[ 7]
> .................
> Idle Time Prior to Transition (ITPT): 0 ms
> Idle Transition Power State (ITPS): 0
> .................
> Entry[ 8]
> .................
> Idle Time Prior to Transition (ITPT): 0 ms
> Idle Transition Power State (ITPS): 0
> .................
> Entry[ 9]
> .................
> Idle Time Prior to Transition (ITPT): 0 ms
> Idle Transition Power State (ITPS): 0
> .................
> Entry[10]
> .................
> Idle Time Prior to Transition (ITPT): 0 ms
> Idle Transition Power State (ITPS): 0
> .................
> Entry[11]
> .................
> Idle Time Prior to Transition (ITPT): 0 ms
> Idle Transition Power State (ITPS): 0
> .................
> Entry[12]
> .................
> Idle Time Prior to Transition (ITPT): 0 ms
> Idle Transition Power State (ITPS): 0
> .................
> Entry[13]
> .................
> Idle Time Prior to Transition (ITPT): 0 ms
> Idle Transition Power State (ITPS): 0
> .................
> Entry[14]
> .................
> Idle Time Prior to Transition (ITPT): 0 ms
> Idle Transition Power State (ITPS): 0
> .................
> Entry[15]
> .................
> Idle Time Prior to Transition (ITPT): 0 ms
> Idle Transition Power State (ITPS): 0
> .................
> Entry[16]
> .................
> Idle Time Prior to Transition (ITPT): 0 ms
> Idle Transition Power State (ITPS): 0
> .................
> Entry[17]
> .................
> Idle Time Prior to Transition (ITPT): 0 ms
> Idle Transition Power State (ITPS): 0
> .................
> Entry[18]
> .................
> Idle Time Prior to Transition (ITPT): 0 ms
> Idle Transition Power State (ITPS): 0
> .................
> Entry[19]
> .................
> Idle Time Prior to Transition (ITPT): 0 ms
> Idle Transition Power State (ITPS): 0
> .................
> Entry[20]
> .................
> Idle Time Prior to Transition (ITPT): 0 ms
> Idle Transition Power State (ITPS): 0
> .................
> Entry[21]
> .................
> Idle Time Prior to Transition (ITPT): 0 ms
> Idle Transition Power State (ITPS): 0
> .................
> Entry[22]
> .................
> Idle Time Prior to Transition (ITPT): 0 ms
> Idle Transition Power State (ITPS): 0
> .................
> Entry[23]
> .................
> Idle Time Prior to Transition (ITPT): 0 ms
> Idle Transition Power State (ITPS): 0
> .................
> Entry[24]
> .................
> Idle Time Prior to Transition (ITPT): 0 ms
> Idle Transition Power State (ITPS): 0
> .................
> Entry[25]
> .................
> Idle Time Prior to Transition (ITPT): 0 ms
> Idle Transition Power State (ITPS): 0
> .................
> Entry[26]
> .................
> Idle Time Prior to Transition (ITPT): 0 ms
> Idle Transition Power State (ITPS): 0
> .................
> Entry[27]
> .................
> Idle Time Prior to Transition (ITPT): 0 ms
> Idle Transition Power State (ITPS): 0
> .................
> Entry[28]
> .................
> Idle Time Prior to Transition (ITPT): 0 ms
> Idle Transition Power State (ITPS): 0
> .................
> Entry[29]
> .................
> Idle Time Prior to Transition (ITPT): 0 ms
> Idle Transition Power State (ITPS): 0
> .................
> Entry[30]
> .................
> Idle Time Prior to Transition (ITPT): 0 ms
> Idle Transition Power State (ITPS): 0
> .................
> Entry[31]
> .................
> Idle Time Prior to Transition (ITPT): 0 ms
> Idle Transition Power State (ITPS): 0
> .................
Powered by blists - more mailing lists