Same SOM+Kernel with a custom board without a PCIE Hub, so that the NVME is directly connected. → works
Same custom Board with PCIE Hub and with JetPack 4.7.3 → works
So i think it’s a timing probing issue within the nvme-pci driver.
The reason why we’re switching from 4.7.3 to 5.0.2 is because of the CBoot, since it also had a problem which was similar to this: Boot Jetson xavier NX using M.2 Key-M SSD
What also is interesting in the UEFI i see the correct NVME as a boot option.
Attached is the dmesg output & the PCIE hub logic in the actual board.
lspci is detecting the device, but not the nvme driver. If i manually bind the nvme driver to the device it is the similar output like above (60s timeout).
@WayneWWW there are some interesting news from this topic. The UEFI has the possibility to load the Kernel from NVME directly (so extlinux.conf), it hangs when it tries to mount the rootfs from NVME. So I think that the nvme or pci drivers from JP5 aren’t working with the PCIE Hub. Attached the overview picture.
We are also struggling with the same issue, after jetpack upgrade 4.6.2 → 5.0.2
I get these errors in the kern.log I have tried pcie_aspm=off
[ 66.528788] nvme nvme0: I/O 4 QID 0 timeout, disable controller
[ 66.531231] nvme nvme0: Identify Controller failed (-4)
[ 66.533274] nvme nvme0: Removing after probe failure status: -5