Unfortunately there seems no improvement, system boots fine, and operates fine, but nvme disappears again after suspend. However I didn't see any spontaneous disappearance of device (so could be some progress ? but will need to test for longer to be certain)
Unfortunately there seems no improvement, system boots fine, and operates fine, but nvme disappears again after suspend. However I didn't see any spontaneous disappearance of device (so could be some progress ? but will need to test for longer to be certain)
log extracts:
Jul 28 09:36:18 phs08 kernel: [ 0.000000] Command line: BOOT_IMAGE= /vmlinuz- 4.12.0- 8-generic root=UUID= f7ae652b- cbf6-48b8- bc6a-d3963957ab 57 ro
...booted and runs fine, then suspend... sleep[7216] : Suspending system... sleep[7216] : System resumed.
Jul 28 11:28:57 phs08 systemd-
... and resume
Jul 28 12:24:36 phs08 kernel: [ 6773.441351] PM: resume of devices complete after 1369.759 msecs
Jul 28 12:24:36 phs08 kernel: [ 6773.441664] PM: Finishing wakeup.
Jul 28 12:24:36 phs08 systemd-
Jul 28 12:27:40 phs08 kernel: [ 6957.315181] nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10
Jul 28 12:27:40 phs08 kernel: [ 6957.339506] nvme 0000:01:00.0: enabling device (0000 -> 0002)
Jul 28 12:27:40 phs08 kernel: [ 6957.339612] nvme nvme0: Removing after probe failure status: -19
Jul 28 12:27:40 phs08 kernel: [ 6957.375614] nvme0n1: detected capacity change from 500107862016 to 0
But one thing I note, is that the kernel records re-starting conventional spinning disks:
Jul 28 12:24:36 phs08 kernel: [ 6772.072165] sd 0:0:0:0: [sda] Starting disk
Jul 28 12:24:36 phs08 kernel: [ 6772.072166] sd 1:0:0:0: [sdb] Starting disk
but there seems no equivalent for the nvme drive (unless "nvme 0000:01:00.0: enabling device (0000 -> 0002)" is the equivalent.