http://bugzilla.opensuse.org/show_bug.cgi?id=1190286 http://bugzilla.opensuse.org/show_bug.cgi?id=1190286#c10 --- Comment #10 from Felix Niederwanger <felix.niederwanger@suse.com> --- Created attachment 852683 --> http://bugzilla.opensuse.org/attachment.cgi?id=852683&action=edit dmesg log with nvme timeouts on 5.14.2-1-default kernel I could observe those nvme timeouts this morning also on the 5.14.2-1-default kernel
[ 663.178681] nvme nvme0: I/O 316 QID 2 timeout, aborting [ 663.212948] nvme nvme0: Abort status: 0x0 [ 695.946443] nvme nvme0: I/O 314 QID 2 timeout, aborting [ 695.946654] nvme nvme0: Abort status: 0x0 [ 735.882658] nvme nvme0: I/O 284 QID 2 timeout, aborting [ 735.891212] nvme nvme0: Abort status: 0x0 [ 767.630652] nvme nvme0: I/O 285 QID 2 timeout, aborting [ 767.665078] nvme nvme0: Abort status: 0x0 [ 873.866909] nvme nvme0: I/O 288 QID 2 timeout, aborting [ 873.901802] nvme nvme0: Abort status: 0x0 [ 904.074947] nvme nvme0: I/O 289 QID 2 timeout, aborting [ 904.109535] nvme nvme0: Abort status: 0x0 [ 934.283056] nvme nvme0: I/O 290 QID 2 timeout, aborting [ 934.291613] nvme nvme0: Abort status: 0x0 [ 964.491053] nvme nvme0: I/O 291 QID 2 timeout, aborting [ 964.525606] nvme nvme0: Abort status: 0x0 [ 994.699056] nvme nvme0: I/O 292 QID 2 timeout, aborting [ 994.733555] nvme nvme0: Abort status: 0x0 [ 1189.007101] nvme nvme0: I/O 274 QID 2 timeout, aborting [ 1189.015735] nvme nvme0: Abort status: 0x0 [ 1228.427041] nvme nvme0: I/O 279 QID 2 timeout, aborting [ 1228.435632] nvme nvme0: Abort status: 0x0 [ 1258.507427] nvme nvme0: I/O 290 QID 2 timeout, aborting [ 1258.515919] nvme nvme0: Abort status: 0x0 [ 1288.587228] nvme nvme0: I/O 299 QID 2 timeout, aborting [ 1288.595821] nvme nvme0: Abort status: 0x0 [ 1318.795237] nvme nvme0: I/O 318 QID 2 timeout, completion polled [ 1449.867351] nvme nvme0: I/O 313 QID 2 timeout, aborting [ 1449.901707] nvme nvme0: Abort status: 0x0 [ 1479.883443] nvme nvme0: I/O 314 QID 2 timeout, aborting [ 1479.918007] nvme nvme0: Abort status: 0x0
After rebooting the system was behaving nicely again. Has anyone an idea what's going on here? I have not touched the hardware and those issues only occurred after updating TW to 5.14. Could the nvme contact be loose? Should I disassemble the laptop and unplug and replug the nvme just to see if that makes a difference? I'm absolutely puzzled here. Attaching also the dmesg log of the failure state for completeness. -- You are receiving this mail because: You are the assignee for the bug.