I believe we have been seeing this same issue on two systems with those same drives (Samsung SSD 990 PRO with Heatsink 1TB, firmware 4B2QJXD7). I have just applied the "nvme_core.default_ps_max_latency_us=0" workaround on one system and will see if it has any effect.
I agree with Jon; it is hard to spot this issue without remote logging, since the SSD stops accepting writes until the system is forcibly restarted. I am not sure if this is a hardware issue or a software issue, but it does seem to be increasingly well documented with this particular drive. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2097618 Title: NVME Unable to change power state from D3cold to D0, device inaccessible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2097618/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
