linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
* [PATCH v2] nvme-pci: Mark Seagate FireCuda 530 as IGNORE_DEV_SUBNQN
@ 2025-06-11  4:06 Anj Duvnjak
  2025-06-11  5:56 ` Christoph Hellwig
  0 siblings, 1 reply; 2+ messages in thread
From: Anj Duvnjak @ 2025-06-11  4:06 UTC (permalink / raw)
  To: linux-nvme; +Cc: Anj Duvnjak

The Seagate FireCuda 530 (PCI ID 1bb1:5018) with firmware versions
SU6SM003 and SU6SM005 reports an invalid SUBNQN field, causing kernel
message:
nvme nvme0: missing or invalid SUBNQN field.

Add the NVME_QUIRK_IGNORE_DEV_SUBNQN to work around this firmware issue.

Tested with both SU6SM003 and SU6SM005 firmware versions.

Signed-off-by: Anj Duvnjak <avian@extremenerds.net>
---
 drivers/nvme/host/pci.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
index 8ff12e415cb5..60f85cdc4fdf 100644
--- a/drivers/nvme/host/pci.c
+++ b/drivers/nvme/host/pci.c
@@ -3673,6 +3673,8 @@ static const struct pci_device_id nvme_id_table[] = {
 	{ PCI_DEVICE(0x1bb1, 0x0100),   /* Seagate Nytro Flash Storage */
 		.driver_data = NVME_QUIRK_DELAY_BEFORE_CHK_RDY |
 				NVME_QUIRK_NO_NS_DESC_LIST, },
+	{ PCI_DEVICE(0x1bb1, 0x5018),   /* Seagate FireCuda 530 NVME SSD */
+		.driver_data = NVME_QUIRK_IGNORE_DEV_SUBNQN, },
 	{ PCI_DEVICE(0x1c58, 0x0003),	/* HGST adapter */
 		.driver_data = NVME_QUIRK_DELAY_BEFORE_CHK_RDY, },
 	{ PCI_DEVICE(0x1c58, 0x0023),	/* WDC SN200 adapter */
-- 
2.46.3



^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH v2] nvme-pci: Mark Seagate FireCuda 530 as IGNORE_DEV_SUBNQN
  2025-06-11  4:06 [PATCH v2] nvme-pci: Mark Seagate FireCuda 530 as IGNORE_DEV_SUBNQN Anj Duvnjak
@ 2025-06-11  5:56 ` Christoph Hellwig
  0 siblings, 0 replies; 2+ messages in thread
From: Christoph Hellwig @ 2025-06-11  5:56 UTC (permalink / raw)
  To: Anj Duvnjak; +Cc: linux-nvme

On Wed, Jun 11, 2025 at 02:06:35PM +1000, Anj Duvnjak wrote:
> The Seagate FireCuda 530 (PCI ID 1bb1:5018) with firmware versions
> SU6SM003 and SU6SM005 reports an invalid SUBNQN field, causing kernel
> message:
> nvme nvme0: missing or invalid SUBNQN field.
> 
> Add the NVME_QUIRK_IGNORE_DEV_SUBNQN to work around this firmware issue.
> 
> Tested with both SU6SM003 and SU6SM005 firmware versions.

The quirk is only for devices with duplicate NQNs that are
actively dangerous, not to surpress a warning about a broken device.



^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2025-06-11  5:56 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-06-11  4:06 [PATCH v2] nvme-pci: Mark Seagate FireCuda 530 as IGNORE_DEV_SUBNQN Anj Duvnjak
2025-06-11  5:56 ` Christoph Hellwig

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).