On debian (4.9) I didn't notice the issue but I didn't use much.
HOWEVER, when I do apt-get upgrade on debian I do get the issue. It just
updated the kernel file, didn't run the new kernel (a boot would have to
On v4.15 I didn't change the nvme_core.default_ps_max_latency_us=0, I guess. I
did before upgrading to v4.15, I guess. But I can try again.
This is all very strange
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Samsung SSD corruption (fsck needed)
To manage notifications about this bug go to:
ubuntu-bugs mailing list