Comment 56 for bug 1705748

Tried that latest one... still fails after suspend but should I be using nvme_core.default_ps_max_latency_us=1500 ?

But as I have said before it does bother me that the suspend and resume operations seem to overlap and all are logged on resume.

Booted am:

Sep 7 10:02:44 phs08 kernel: [ 0.000000] Linux version 4.12.0-14-generic (root@Linux) (gcc version 7.1.0 (Ubuntu 7.1.0-13ubuntu1) ) #15~pm961+reset SMP Wed Sep 6 13:43:27 CST 2017 (Ubuntu 4.12.0-14.15~pm961+reset-generic 4.12.10)
Sep 7 10:02:44 phs08 kernel: [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.12.0-14-generic root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro

system running all day...

from pm-suspend.log:
Thu Sep 7 19:34:17 BST 2017: performing suspend
Thu Sep 7 20:26:41 BST 2017: Awake.

from kernel.log
(nothing about any suspend operations prior to wakeup time, i.e. all kernel operations relating to suspend are logged on wakeup !)

Sep 7 20:26:41 phs08 kernel: [34307.434357] PM: Syncing filesystems ... done.
Sep 7 20:26:41 phs08 kernel: [34307.498356] PM: Preparing system for sleep (mem)
...
Sep 7 20:26:41 phs08 kernel: [34311.224400] PM: resume of devices complete after 698.454 msecs
Sep 7 20:26:41 phs08 kernel: [34311.224785] PM: Finishing wakeup
...
At 20:28 I successfully saved a spreadsheet file to the nvme disk, that was open before the system was suspended (the file is timestamped with 20:28)

then....
Sep 7 20:29:56 phs08 kernel: [34506.017034] nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0xffff
Sep 7 20:29:56 phs08 kernel: [34506.052638] pci_raw_set_power_state: 5 callbacks suppressed
Sep 7 20:29:56 phs08 kernel: [34506.052642] nvme 0000:01:00.0: Refused to change power state, currently in D3
Sep 7 20:29:56 phs08 kernel: [34506.052779] nvme nvme0: Removing after probe failure status: -19
etc.

So the nvme disk apparently does not become inaccessible until 3 min after the system has woken up !