Comment 94 for bug 1705748

Sorry for being so slow, and not sure I have run the correct tests:

Command line: BOOT_IMAGE=/vmlinuz-4.13.0-34-generic root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro

Suspend and resume:
Feb 24 11:11:14 phs08 kernel: [ 7608.732297] nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10
Feb 24 11:11:14 phs08 kernel: [ 7608.784945] print_req_error: I/O error, dev nvme0n1, sector 136096888
Feb 24 11:11:14 phs08 kernel: [ 7608.784957] BTRFS error (device nvme0n1p5): bdev /dev/nvme0n1p5 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0
Feb 24 11:11:14 phs08 kernel: [ 7608.944330] nvme 0000:01:00.0: RESET SUCCEEDED
Feb 24 11:11:14 phs08 kernel: [ 7608.944337] nvme 0000:01:00.0: enabling device (0000 -> 0002)
Feb 24 11:11:14 phs08 kernel: [ 7608.944496] nvme nvme0: Removing after probe failure status: -19
Feb 24 11:11:14 phs08 kernel: [ 7608.976318] nvme0n1: detected capacity change from 500107862016 to 0
Feb 24 11:11:14 phs08 kernel: [ 7608.976521] print_req_error: I/O error, dev nvme0n1, sector 376046984

Note the force_apst parameter was not used above, tried below with the more recent kernel...

Command line: BOOT_IMAGE=/vmlinuz-4.15.0-9-generic root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro nvme_core.force_apst=1

didn't get to being able to suspend, system hangs requiring reset, :
Feb 24 11:24:10 phs08 kernel: [ 567.842115] INVALID_DEVICE_REQUEST device=00:00.0 address=0xfffffffdf8000000 flags=0x0a00]

will try again with force apst=1 shortly