[bug report]nvme0: Admin Cmd(0x6), I/O Error (sct 0x0 / sc 0x2) MORE DNR observed during blktests

[Alan Adamson]

Hi Jason,

It’s a harmless error, but we are looking at suppressing it.

Alan

> On Apr 5, 2022, at 1:00 PM, Jason A. Donenfeld <Jason at zx2c4.com> wrote:
> 
> Hi Alan,
> 
> I too am seeing this. Tracking it down to the same commit, I decided to
> enable NVME_VERBOSE_ERRORS to get some more information. Now on boot and
> everytime I wake up from sleep, I see:
> 
> [   89.098578] nvme nvme0: Shutdown timeout set to 8 seconds
> [   89.098683] nvme0: Identify(0x6), Invalid Field in Command (sct 0x0 / sc 0x2) MORE
> [   89.119363] nvme nvme0: 16/0/0 default/read/poll queues
> 
> With that middle line in red.
> 
> Question is: is this actually an error? If not, maybe it shouldn't be
> printed as a KERN_ERR. And if it's printed as a KERN_INFO, maybe it
> should only do so when CONFIG_NVME_VERBOSE_ERRORS=y? Or do you think
> there is actually some other diagnostic value in having this print
> always?
> 
> Using a Samsung SSD 970 EVO Plus 2TB, firmware version 2B2QEXM7, in case
> that's useful info.
> 
> I also noticed a ~2 second boot delay on 5.18-rc1:
> 
> [    0.917631] pstore: Using crash dump compression: deflate
> [    0.917807] Key type encrypted registered
> [    0.951840] ACPI: battery: Slot [BAT0] (battery present)
> [    3.146765] nvme nvme0: Shutdown timeout set to 8 seconds
> [    3.146918] nvme0: Identify(0x6), Invalid Field in Command (sct 0x0 / sc 0x2) MORE
> [    3.188852] nvme nvme0: 16/0/0 default/read/poll queues
> [    3.198163]  nvme0n1: p1 p2
> [    3.199554] Freeing unused kernel image (initmem) memory: 12952K
> 
> I haven't looked into it much, but I assume it's also NVMe related? Or
> maybe the vconsole is just initializing faster so I see text where
> before I didn't. Not sure.
> 
> Regards,
> Jason