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. ** Attachment added: "dmesg after reboot" http://launchpadlibrarian.net/9506099/dmesg-reboot.log -- kernel 2.6.22-11 fails to resume drive correctly https://bugs.launchpad.net/bugs/139079 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
