nvme-pci: add quirk for Memblaze Pblaze5 (0x1c5f:0x0555)
PATCH 1/1 nvme-pci: add quirk for Memblaze Pblaze5 (0x1c5f:0x0555)
The Memblaze Pblaze5 NVMe device (PCI ID 0x1c5f:0x0555) is detected as a controller on recent kernels (tested on 5.15.85 and 6.8.4), but no namespace is exposed.
Tools like lsblk and fdisk do not report any block device.
dmesg shows:
nvme nvme0: missing or invalid SUBNQN field.
The device works correctly on older kernels (e.g. 4.19), suggesting a compatibility issue with newer namespace handling.
This indicates the device does not properly support the Namespace Descriptor List feature.
Applying NVME_QUIRK_NO_NS_DESC_LIST allows the namespace to be discovered correctly.
--- drivers/nvme/host/pci.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/nvme/host/pci.c +2 -0
@@ -4104,6 +4104,8 @@ static void nvme_error_resume(struct pci_dev *pdev) .driver_data = NVME_QUIRK_DELAY_BEFORE_CHK_RDY, }, { PCI_DEVICE(0x1c5f, 0x0540), /* Memblaze Pblaze4 adapter */ .driver_data = NVME_QUIRK_DELAY_BEFORE_CHK_RDY, }, + { PCI_DEVICE(0x1c5f, 0x0555), /* Memblaze Pblaze5 adapter */ + .driver_data = NVME_QUIRK_NO_NS_DESC_LIST, }, { PCI_DEVICE(0x144d, 0xa821), /* Samsung PM1725 */ .driver_data = NVME_QUIRK_DELAY_BEFORE_CHK_RDY, }, { PCI_DEVICE(0x144d, 0xa822), /* Samsung PM1725a */
Signature · 1 line
1.8.3.1
Quoted 15 lines · Tao Jiang
The Memblaze Pblaze5 NVMe device (PCI ID 0x1c5f:0x0555) is detected as a controller on recent kernels (tested on 5.15.85 and 6.8.4), but no namespace is exposed.
Tools like lsblk and fdisk do not report any block device.
dmesg shows:
nvme nvme0: missing or invalid SUBNQN field.The device works correctly on older kernels (e.g. 4.19), suggesting a compatibility issue with newer namespace handling.
This indicates the device does not properly support the Namespace Descriptor List feature.
Quoted 6 lines
Applying
NVME_QUIRK_NO_NS_DESC_LISTallows the namespace to be discovered correctly.Signed-off-by Tao Jiang<[email protected]>---
Looks good.
Me, another broken device :( I wonder how these people test their hardware..
Quoted 9 lines · Tao Jiang
The Memblaze Pblaze5 NVMe device (PCI ID 0x1c5f:0x0555) is detected as a controller on recent kernels (tested on 5.15.85 and 6.8.4), but no namespace is exposed.
Tools like lsblk and fdisk do not report any block device.
dmesg shows:
nvme nvme0: missing or invalid SUBNQN field.
Quoted 8 lines
The device works correctly on older kernels (e.g. 4.19), suggesting a compatibility issue with newer namespace handling.
This indicates the device does not properly support the Namespace Descriptor List feature.
Applying
NVME_QUIRK_NO_NS_DESC_LISTallows the namespace to be discovered correctly.
Thanks, applied to nvme-7.1.