You are not logged in.

#1 2022-12-18 22:53:41

Dasiel
Member
Registered: 2022-12-18
Posts: 1

NVME Quirk bogus data - missing NVME Drive

Hey all,

I have run into the following issue after upgrading to latest ArchLinux kernel - 6.0.12-arch1-1

I have 2 same NVME drives, but after the upgrade partitions on one of the NVME are not displayed. This is because of the following error:

[    1.366197] nvme nvme1: globally duplicate IDs for nsid 1
[    1.366199] nvme nvme1: VID:DID 1987:5013 model:GIGABYTE GP-GSM2NE3256GNTD firmware:EDFM00.2.

After some googling I have found out that this is caused because of following checks being introduced in the Linux Kernel:
nvme: check that EUI/GUID/UUID are globally unique
nvme: add a quirk to disable namespace identifiers

From what I understand it seems that my Gigabyte NVME is not included in that list:

# lspci -nn -d ::0108
01:00.0 Non-Volatile memory controller [0108]: Phison Electronics Corporation PS5013 E13 NVMe Controller [1987:5013] (rev 01)
04:00.0 Non-Volatile memory controller [0108]: Phison Electronics Corporation PS5013 E13 NVMe Controller [1987:5013] (rev 01)

At least I don't see any such entry for Phison in here: pci.c

	{ PCI_DEVICE(0x1987, 0x5012),	/* Phison E12 */
		.driver_data = NVME_QUIRK_BOGUS_NID, },
	{ PCI_DEVICE(0x1987, 0x5016),	/* Phison E16 */
		.driver_data = NVME_QUIRK_IGNORE_DEV_SUBNQN |
				NVME_QUIRK_BOGUS_NID, },
	{ PCI_DEVICE(0x1987, 0x5019),  /* phison E19 */
		.driver_data = NVME_QUIRK_DISABLE_WRITE_ZEROES, },
	{ PCI_DEVICE(0x1987, 0x5021),   /* Phison E21 */

What would you suggest to get this fixed? From what I understand following entry should be added to that file and the Linux kernel should be recompiled:

	{ PCI_DEVICE(0x1987, 0x5013),	/* Phison  */
		.driver_data = NVME_QUIRK_BOGUS_NID, },

However I have no clue how to easily recompile current arch linux kernel to get this fixed, plus I also run ZFS and I don't really want to maintain my own custom kernel build. Any suggests how to quickly get this fixed? Or at least how to quickly build my own kernel based on the current configuration of Arch kernel?

Thank you very much!

Offline

#2 2022-12-18 22:59:36

Slithery
Administrator
From: Norfolk, UK
Registered: 2013-12-01
Posts: 5,776

Re: NVME Quirk bogus data - missing NVME Drive

Dasiel wrote:

Or at least how to quickly build my own kernel based on the current configuration of Arch kernel?

https://wiki.archlinux.org/title/Kernel … ild_System


No, it didn't "fix" anything. It just shifted the brokeness one space to the right. - jasonwryan
Closing -- for deletion; Banning -- for muppetry. - jasonwryan

aur - dotfiles

Offline

#3 2022-12-19 00:11:24

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,143

Re: NVME Quirk bogus data - missing NVME Drive

Have you checked if there is a bug report and, if so, if including the quirk has been considered as a solution?

See e.g. https://bugzilla.kernel.org/show_bug.cgi?id=216049. See especially https://bugzilla.kernel.org/show_bug.cgi?id=216049#c13 for the fastest way to get a fix into the kernel.

Edit: https://bbs.archlinux.org/viewtopic.php?id=277378 may also be helpful.

Last edited by cfr (2022-12-19 00:29:18)


CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

Board footer

Powered by FluxBB