Comment 31 for bug 1705748

So last night I installed the kernel and it seems the issue persists:

Aug 3 02:30:59 phs08 kernel: [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.12.0-9-generic root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro

suspend:

Aug 3 02:52:35 phs08 systemd[1]: Reached target Sleep.
Aug 3 02:52:35 phs08 systemd[1]: Starting Suspend...
Aug 3 02:52:35 phs08 systemd-sleep[5407]: Failed to connect to non-global ctrl_ifname: (nil) error: No such file or directory
Aug 3 02:52:35 phs08 systemd-sleep[5408]: /lib/systemd/system-sleep/wpasupplicant failed with error code 255.
Aug 3 02:52:35 phs08 systemd-sleep[5407]: Suspending system...

resume next morning:

Aug 3 09:29:21 phs08 kernel: [ 1300.773097] PM: Syncing filesystems ... done.
Aug 3 09:29:21 phs08 kern

Aug 3 09:29:21 phs08 kernel: [ 1305.552367] PM: resume of devices complete after 1226.588 msecs
Aug 3 09:29:21 phs08 kernel: [ 1305.552777] PM: Finishing wakeup.
Aug 3 09:29:21 phs08 kernel: [ 1305.552778] OOM killer enabled.
Aug 3 09:29:21 phs08 kernel: [ 1305.552778] Restarting tasks ... done.
Aug 3 09:29:24 phs08 kernel: [ 1307.942704] r8169 0000:25:00.0 enp37s0: link up
Aug 3 09:29:27 phs08 kernel: [ 1311.521223] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Aug 3 09:29:27 phs08 kernel: [ 1311.533275] ata1.00: configured for UDMA/133
Aug 3 09:29:27 phs08 kernel: [ 1311.581201] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Aug 3 09:29:28 phs08 kernel: [ 1311.593308] ata2.00: configured for UDMA/133

Aug 3 09:32:45 phs08 kernel: [ 1508.852213] nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10
Aug 3 09:32:45 phs08 kernel: [ 1508.896322] nvme 0000:01:00.0: enabling device (0000 -> 0002)
Aug 3 09:32:45 phs08 kernel: [ 1508.896429] nvme nvme0: Removing after probe failure status: -19
Aug 3 09:32:45 phs08 kernel: [ 1508.920265] nvme0n1: detected capacity change from 500107862016 to 0
Aug 3 09:32:45 phs08 kernel: [ 1508.920536] blk_update_request: I/O error, dev nvme0n1, sector 360686080

"Probably need to change the device to full functional state before S3, like how basic power management works"
I can't see anything in the logs that relates to this or suggests it is happening, what should I look for ?

I notice this in case of relevance
Aug 3 09:29:21 phs08 kernel: [ 1303.986393] CPU: 0 PID: 5407 Comm: systemd-sleep Tainted: G OE 4.12.0-9-generic #10