Comment 4 for bug 1910866

I'm on Ubuntu 20.04, and after updating to the HWE 5.8 kernel recently I have also been suffering my nvme drive becoming read only after a period of time. I have now switched back to the 5.4 kernel and not suffered the issue again.

I am on a single disk system so had to run dmesg --follow remotely on another machine to retrieve log information.

Here is a pastebin of around the time my system locks up https://pastebin.ubuntu.com/p/FKsJV8VwRw/ (note it has similar errors, a timeout aborting, then a reset, then i have a call trace etc).

Here is a pastebin of the smartctl output https://pastebin.ubuntu.com/p/W9w2nHYhd2/ the drive itself appears to be fine and not failing (it does seem to increment "Error Information Log Entries" when this lockup happens - but when viewing the error it is just full of 0xffff).

System info when the lockup happened:

Machine: Dell XPS 13 9360
Drive: THNSN5512GPUK NVMe TOSHIBA 512GB
Kernel at the time: $ apt policy linux-image-generic-hwe-20.04
linux-image-generic-hwe-20.04:
  Installed: 5.8.0.36.40~20.04.21
  Candidate: 5.8.0.36.40~20.04.21
  Version table:
 *** 5.8.0.36.40~20.04.21 500
        500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
        100 /var/lib/dpkg/status
     5.4.0.26.32 500
        500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

Let me know if I can provide any more info :-)