Comment 16 for bug 1792660

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