Suspend [to RAM and to disk] broken in 2.6.20-15

[smt6k]

Binary package hint: linux-source-2.6.20

I upgraded from 6.10 (in which suspend to ram and disk both worked flawlessly) to 7.04, only to discover that now both suspends are broken. I spent quite a long time trying to diagnose the problem, thinking it very unlikely that the new kernel was to blame. Out of desperation I tried switching back to 2.6.17, and lo and behold: it just works. I don't really know why; I didn't see anything in the logs I looked through that would tell me, but I am new to Ubuntu (been a Gentoo user for quite a few years before this) and have no idea how you folks debug your suspend operations. I'd be happy to run any tests or produce any log files that could come in handy.

[Tomas Thiemel (thiemel)]

Hi,
I dist-upgraded from 6.10 to 7.04 and I have the same problem - suspend to disk and suspend to RAM does not work.
When I suspend to RAM and restore, kernel locks up with flashing CAPS-LOCK and SCROLL-LOCK LEDs on keyboard.

New version, new problems :-(((

(I have MSI-S270 notebook with AMD64 Turion MT-32 CPU; Linux 2.6.20.3-ubuntu1 #6 Wed Apr 25 09:43:27 CEST 2007 x86_64 GNU/Linux)

[Tomas Thiemel (thiemel)]

Here is some PM_DEBUG message (linux-source-2.6.20.3/Documentation/power/s2ram.txt)

...
[ 16.314911] ACPI: (supports S0 S1 S3 S4 S5)
[ 16.315204] Magic number: 0:150:167
[ 16.315247] hash matches drivers/base/power/resume.c:28
[ 16.315340] hash matches device ttyq7
[ 16.315549] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
...

It is alway connected with some "tty??" device...

[Tomas Thiemel (thiemel)]

I solved this problem.
It seems to be problem with ATI X200M graphic card...
When I used FGLRX driver, I had strange problems.
Now, I use RADEON driver and I have (almost) no problems. I had some problems with display when I resumed from S3 state, but it was X200M bug - in BIOS, I chaged ammount of graphic RAM to the smalles number (16MB) and everything works OK. (Whed I had 64MB, I had problems with resuming.)

So you can mark this "bug" as * SOLVED *.

[smt6k (smt6k)]

I don't have an ATi card... So that probably wouldn't have fixed it for me; but oddly enough it "magically" fixed itself over time... and I know computers aren't organic things and that someone must have changed something, but it wasn't me. Also, now sound is broken on resume. And sometimes on reboot after resume if I don't give it a minute to chill between boots. But this is on old kernels too for me.

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Leann Ogasawara (leannogasawara)]

Per comments posted previously, I'm marking this bug as Fix Released.