Hi Zhanglei, thanks for the test and screenshot. I can't say for sure, but based on the screenshot, seems they are still running 4.15.0-29 - I'm seeing the BOOT_IMAGE entry in the /proc/cmdline. Specifically, this doesn't mean much (one can boot like a 4.4 kernel and add a BOOT_IMAGE of a 4.15, no harm), but it's a clue that customer didn't boot the right kernel, and the patch that restores the old behavior to nvme driver when the parameter is used is not present in 4.15.0-29.
So, I'd ask a new test, this time customer could run "uname -r", "cat /proc/cmdline" and after that, "ls -l /sys/block/*" to check the mapping between the nvme devices. Cheers, Guilherme -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792660 Title: nvme name floated after boot with 4.15.0 kernel Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: nvme device name such as /dev/nvme?n?p? would be floated that is symbol link to different real ssd device after reboot in 4.15.0 kernel for 16.04.5 HWE and 18.04 GA-kernel. This are not found on 16.04.5 GA- kernel ( 4.4.0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
