Comment 79 for bug 1678184

I think I hit this problem, but with the 256 GB Lite-On (or LiteOn) NVMe M.2 PCIe CX2 Series Enterprise Solid-State Drive Model CA1-8B256 that came standard in my 2017 Dell Precision Tower 3420.

I'm on the HWE Kernel with the "linux-generic-hwe-16.04" package, having installed from the Ubuntu 16.04.2 LTS amd64 ISO file. I didn't notice any file system errors until I upgraded to the "linux-image-4.8.0-53-generic" package on May 25, 2017. Below is my upgrade schedule showing when the errors occurred:

2017-04-04 Upgraded to 4.8.0-46.49
2017-04-24 Upgraded to 4.8.0-49.52 ← Adds NVMe APST support (LP: #1664602)
2017-05-01 Upgraded to 4.8.0-51.54
2017-05-16 Upgraded to 4.8.0-52.55
2017-05-25 Upgraded to 4.8.0-53.56 ← Started noticing errors on NVMe drive

First my Thunderbird Lightning calendar database got corrupted so I couldn't add events. One time the system just froze, with the mouse cursor and keyboard not working. Yesterday, the root file system remounted read-only after waking from suspend.

This morning I added "nvme_core.default_ps_max_latency_us=0" to the Grub configuration, and after repairing the file system errors with "e2fsck", everything seems to be working fine so far:

/etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash swapaccount=1 nvme_core.default_ps_max_latency_us=0"

I'm considering moving back to the GA 16.04 kernel, just to be more conservative in my system updates. Is the general advice to use the HWE kernel only if we need support for some new hardware, but otherwise, stay on the GA kernel?

Is there anything in Kernel version 4.8.0-53 that may have caused the problem or made it more likely to appear?