Intrepid regression, suspend doesn't work EXT3-fs error

[Thomas Novin]

Binary package hint: linux-source-2.6.27

Hello. Since I upgraded to Intrepid suspend-to-ram doesn't work. I have followed the steps detailed on https://wiki.ubuntu.com/DebuggingKernelSuspend but I think I failed to save the dmesg data.

Steps to reproduce:

1. Do a suspend (seems to work fine)
2. Wait
3. Resume by pressing power button.
4. 1 minute later, watch the display change from strange colors and to later on display (with a dimmed display) this data:

Starting System Tools Backend: OK
...
Starting TiMidity++ ALSA : OK

[39747.744205] EXT3-fs error (device sda5) ext3_find_entry: reading directory #674448 offset 0
[39747.744429] EXT3-fs error (device sda5) ext3_find_entry: reading directory #674448 offset 0
[39758.8281501] EXT3-fs error (device sda5) ext3_find_entry: reading directory #557213 offset 0

Then nothing.

I am able to change to tty1 by using CTRL-ALT-F1. I am able to type my login but hangs after enter.

I am able to reboot by using ctrl-alt-prtscr+REISUB

Linux thnov-desktop 2.6.27-3-generic #1 SMP Wed Sep 10 16:02:00 UTC 2008 i686 GNU/Linux

$ lsb_release -rd
Description: Ubuntu intrepid (development branch)
Release: 8.10

[Thomas Novin (thomasn80)]

$ mount
/dev/sda5 on / type ext3 (rw,errors=remount-ro)

[Thomas Novin (thomasn80)]

Just re-confirming that this is still an issue.

[Tobias Stegmann (punischdude)]

Same thing over here.

[Thomas Novin (thomasn80)]

This is OK for me now! Resume takes a bit to long (10-15 secs) IMHO but it works.

I have a Intrepid install which is up-to-date as of CEST 081020 21:03.

[Steve Beattie (sbeattie)]

Marking as Fix Released based on Thomas' comment. Tobias, if you're still having problems, please reopen this bug (set its status to New).

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.