Hi, What information exactly expected to be archived by mentioned experiment? 1) Logging of failed suspend/resume is not possible in this situation. 2) Filesystem corruption and kernel crash during mount attempt are already documented. 3) Filesystem recovery procedure incompetence is obvious here.
If its worth something, suspend/resume issues are the same on Fedora14 and RedHat6, not sure regarding kernel crash since their filesystem recovery procedure is different. My observetions shows that, occasionally, VFS awakes before block device on USB device becomes ready (probably due to delayed/forced USB host reset). After failure, XFS retries and survives, while EXT fails immediately and remounts root as R/O. The big questions here, is why EXT leaves filesystem in broken state in firsts place? Isn't it supposed to commit both data and journal before suspend? I am pretty sure mainline Linux also affected, but I am ready to perform validation. Since suspend/resume part of an issue is reconstructable only if root filesystem is EXT4 and on USB, LiveCD is not an option. Is it ok to install clean system on USB? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/706795 Title: Terminated suspend causes ext4 corruptions which crashes kernel on mount attempt -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
