Comment 5 for bug 1774950

Assuming using UKUU to try various kernels is fine, I have tried the following kernels and experienced the same suspend failure:

4.17.0
(4.17.0-041700.201806032231)

4.16.13
(4.16.13-041613.201805300810)

4.15.18
(4.15.18-041518.201804190330)

4.15.1
4.15.1-041501.201802031831

Using the latest 4.14 kernel (4.14.47-041447.201805301730) allows suspend to work as expected.

The kern.log shows that for a failed suspend on the 4.15, 4.16 and 4.17 kernels it only gets as far as

PM: suspend entry (deep)

and there are no further entries until startup (after having to shut the machine down)

A succesful suspend using the 4.14 kernel gives the kern.log entries as

Jun 4 23:27:28 PAviX360 kernel: [ 50.875164] PM: suspend entry (deep)
Jun 4 23:27:28 PAviX360 kernel: [ 50.875167] PM: Syncing filesystems ... done.
Jun 4 23:27:33 PAviX360 kernel: [ 50.883987] Freezing user space processes ... (elapsed 0.
001 seconds) done.
Jun 4 23:27:33 PAviX360 kernel: [ 50.885799] OOM killer disabled.
Jun 4 23:27:33 PAviX360 kernel: [ 50.885800] Freezing remaining freezable tasks ... (elaps
ed 0.001 seconds) done.

etc...

So when it fails at 'PM: suspend entry (deep)' using 4.15 kernels and later, it does not move on to PM: Syncing filesystems etc.