I still have this issue with booting, though it seems to be less frequent. However, I can see in the kernel logs when I boot into linux successfully that my other drive is being thrown out because of the duplicate subnqn:
nvme nvme1: ignoring ctrl due to duplicate subnqn (nqn.2017-12.org.nvmexpress:uuid:11111111-2222-3333-4444-555555555555).
I'm having some trouble testing this on my own since I'm not experienced with kernel dev, but I wonder if this duplicate entry in the device table in drivers/nvme/host/pci.c is the issue:
I still have this issue with booting, though it seems to be less frequent. However, I can see in the kernel logs when I boot into linux successfully that my other drive is being thrown out because of the duplicate subnqn:
nvme nvme1: ignoring ctrl due to duplicate subnqn (nqn.2017- 12.org. nvmexpress: uuid:11111111- 2222-3333- 4444-5555555555 55).
I'm having some trouble testing this on my own since I'm not experienced with kernel dev, but I wonder if this duplicate entry in the device table in drivers/ nvme/host/ pci.c is the issue:
{ PCI_VDEVICE(INTEL, 0xf1a6), NO_DISABLE, }, IGNORE_ DEV_SUBNQN, },
.driver_data = NVME_QUIRK_
{ PCI_VDEVICE(INTEL, 0xf1a6), /* Intel 760p/Pro 7600p */
.driver_data = NVME_QUIRK_
I believe it should be just
{ PCI_VDEVICE(INTEL, 0xf1a6), /* Intel 760p/Pro 7600p */ IGNORE_ DEV_SUBNQN | QUIRK_NO_ DISABLE, },
.driver_data = NVME_QUIRK_
NVME_