Comment 9 for bug 139079

The dmesg after reboot is not helpful here I think. What happens at resume is that the drive does not resume correctly, the filesystem is mounted read-only, and no logs of the event can be written on disk. This makes it hard to give diagnostics, although dmesg at resume time gives plenty of errors.

If I can get it to work, I will try to debug with a serial console, so I can get the relevant output.