Comment 97 for bug 1705748

In case it helps, further test with 4.13.0-34

Feb 24 11:48:40 phs08 kernel: [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.13.0-34-generic root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro nvme_core.force_apst=1

... boots fine, appears ok then suspend overnight...

Feb 25 11:54:43 phs08 kernel: [ 775.372073] sd 0:0:0:0: [sda] Starting disk
Feb 25 11:54:43 phs08 kernel: [ 775.372077] sd 1:0:0:0: [sdb] Starting disk
Feb 25 11:54:43 phs08 kernel: [ 775.372156] serial 00:05: activated
Feb 25 11:54:43 phs08 kernel: [ 775.555973] r8169 0000:25:00.0 enp37s0: link down
Feb 25 11:54:43 phs08 kernel: [ 775.658010] nvme 0000:01:00.0: RESET SUCCEEDED

seems okay for 5 mins... then...

Feb 25 11:59:39 phs08 kernel: [ 1072.862588] nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10
Feb 25 11:59:39 phs08 kernel: [ 1072.906660] print_req_error: I/O error, dev nvme0n1, sector 30511480
Feb 25 11:59:40 phs08 kernel: [ 1073.054471] nvme 0000:01:00.0: RESET SUCCEEDED
Feb 25 11:59:40 phs08 kernel: [ 1073.054478] nvme 0000:01:00.0: enabling device (0000 -> 0002)
Feb 25 11:59:40 phs08 kernel: [ 1073.054650] nvme nvme0: Removing after probe failure status: -19
Feb 25 11:59:40 phs08 kernel: [ 1073.078418] nvme0n1: detected capacity change from 500107862016 to 0

... usual i/o errors and hard reset needed.