Comment 8 for bug 90526

Mostly confirmed.
It seems in my case there also seemed to have been a fsck running just before that happened, however, it was definitely not a routine fsck. (shouldn't a fsck of the root-fs leave the swap partitioned untouched anyway?)
In my case the fsck(?, probably not a full check, since it only took 2 seconds to complete) happened after a (failed) hibernation attempt, here is the message from /var/log/messages:

May 23 15:32:09 hobbes kernel: [ 10.052000] EXT3-fs: INFO: recovery required on readonly filesystem.
May 23 15:32:09 hobbes kernel: [ 10.052000] EXT3-fs: write access will be enabled during recovery.
May 23 15:32:09 hobbes kernel: [ 11.944000] kjournald starting. Commit interval 5 seconds
May 23 15:32:09 hobbes kernel: [ 11.944000] EXT3-fs: recovery complete.

I'm not sure whether this bug is related to hibernations, so here is what I did:
- I tried "Hibernate" from the Gnome shutdown menu a few days ago, which seemed to work.
- However, on wakeup all I saw was a black screen (with sync), and even Ctrl-Alt-F1 didn't work anymore. A remote login showed that Xorg was running at 100% CPU. I then performed a clean shutdown.
- I tried "Hibernate" again yesterday. Again, it did go to sleep. However, this time the machine didn't seem to resume on wakeup, but do a normal, complete reboot.
- During that reboot, the above recovery was run, but it probably was journal related, not a full fsck, since it only took a few seconds.

I don't have uswsusp or similar installed. Using Feisty.
HTH,
Cruncher