I've just booted into the 5.4.5 upstream kernel from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.5/ and I'm seeing that the NVMe drive _is_ detected correctly:
$ ls /dev/nvme* /dev/nvme0 /dev/nvme0n1 /dev/nvme0n1p1 /dev/nvme0n1p2 /dev/nvme0n1p3 /dev/nvme0n1p4
The journal messages do look very similar, so maybe there isn't much to be gleaned from them in the failing case:
$ journalctl -b0 | grep nvme Dec 20 12:12:13 surprise kernel: nvme nvme0: pci function 0000:01:00.0 Dec 20 12:12:13 surprise kernel: nvme nvme0: missing or invalid SUBNQN field. Dec 20 12:12:13 surprise kernel: nvme nvme0: allocated 64 MiB host memory buffer. Dec 20 12:12:13 surprise kernel: nvme nvme0: 15/0/0 default/read/poll queues Dec 20 12:12:13 surprise kernel: nvme nvme0: Identify Descriptors failed (2) Dec 20 12:12:13 surprise kernel: nvme nvme0: Identify Descriptors failed (2) Dec 20 12:12:13 surprise kernel: nvme0n1: p1 p2 p3 p4
I've just booted into the 5.4.5 upstream kernel from https:/ /kernel. ubuntu. com/~kernel- ppa/mainline/ v5.4.5/ and I'm seeing that the NVMe drive _is_ detected correctly:
$ ls /dev/nvme*
/dev/nvme0
/dev/nvme0n1
/dev/nvme0n1p1
/dev/nvme0n1p2
/dev/nvme0n1p3
/dev/nvme0n1p4
The journal messages do look very similar, so maybe there isn't much to be gleaned from them in the failing case:
$ journalctl -b0 | grep nvme
Dec 20 12:12:13 surprise kernel: nvme nvme0: pci function 0000:01:00.0
Dec 20 12:12:13 surprise kernel: nvme nvme0: missing or invalid SUBNQN field.
Dec 20 12:12:13 surprise kernel: nvme nvme0: allocated 64 MiB host memory buffer.
Dec 20 12:12:13 surprise kernel: nvme nvme0: 15/0/0 default/read/poll queues
Dec 20 12:12:13 surprise kernel: nvme nvme0: Identify Descriptors failed (2)
Dec 20 12:12:13 surprise kernel: nvme nvme0: Identify Descriptors failed (2)
Dec 20 12:12:13 surprise kernel: nvme0n1: p1 p2 p3 p4