Comment # 5 on bug 1190286 from Felix Niederwanger

Created attachment 852389 [details]
dmesg log with nvme timeouts

Ok, it happened again this morning on the first boot. I got the following from
the dmesg logs (full log is attached)

> [  550.712988] nvme nvme0: I/O 65 QID 7 timeout, aborting
> [  550.747484] nvme nvme0: Abort status: 0x0
> [  643.897054] nvme nvme0: I/O 101 QID 7 timeout, aborting
> [  643.931494] nvme nvme0: Abort status: 0x0
> [  703.033212] nvme nvme0: I/O 81 QID 7 timeout, aborting
> [  703.041825] nvme nvme0: Abort status: 0x0
> [  763.709540] nvme nvme0: I/O 99 QID 7 timeout, aborting
> [  763.748734] nvme nvme0: Abort status: 0x0
> [  797.241362] nvme nvme0: I/O 109 QID 7 timeout, completion polled
> [  839.225551] nvme nvme0: I/O 102 QID 7 timeout, aborting
> [  839.260030] nvme nvme0: Abort status: 0x0
> [  884.537508] nvme nvme0: I/O 66 QID 7 timeout, aborting
> [  884.572305] nvme nvme0: Abort status: 0x0
> [  915.001594] nvme nvme0: I/O 122 QID 7 timeout, aborting
> [  915.036194] nvme nvme0: Abort status: 0x0
> [  960.313707] nvme nvme0: I/O 148 QID 7 timeout, aborting

Here, the laptop froze occasionally for a couple of seconds, before it was
running again. The last time it was completely frozen for at least 5 minutes on
the user login on VT1 (tty1) - see screenshot above.

When rebooting I got also the following error message, which is consistent with
nvme issues:

> systemd-shutdown[1]: Synching filesystem and block devices - timed out, issuing SIGKILL to PID 10499

This is a Dell Latitude 7290 with a WD Black 1 TB nvme disk
(WDS100T3X0C-00SJG0). Those issues only arises after the update to the 5.14
kernel.

I can only suspect that the docking station was just a coincidence, however it
puzzles me still, why the system unfroze itself after disconnecting the docking
station.

I rebooted the laptop and until now it behaves fine, no nvme timeout issues are
present in the dmesg log. So, it also does not happen after every boot process.