suspend bug (ubuntu-8.10-alternate-amd64)

[Mihail]

First of all, great thanks for Ubuntu!
And again I have a problem with suspend/hibernate.
Box is Dell Inspiron 1521. Few months ago I installed Ubuntu 8.04 x64 on it. Problem with suspend/hibernate was solved by installing proprietary Wi-Fi driver. But now it doesn't help.
1) when I try to suspend, mouse pointer comes to upper-left corner of the screen and nothing else happens, so I have to just hold power button until computer turns off.
2) if I bring wlan0 interface down before suspending, computer goes to sleep (but very slowly, about minute or so), and when I try to wake it up, I see the same thing: mouse pointer in upper-left corner of the black screen. Hard disk indicator shows that some file operations are taking place.

There is some info in attachment (I cleaned up dmesg before doing experiment to make it more informative).

[ira (chayut)]

I have a similar problem. When resuming from Suspend I get an unlock screen with the cursor blinking in the text box for my password. This blinks once or twice and then stops blinking. My keyboard and mouse are unresponsive and the system seems locked up. Holding down the power button until the system is powered off is the only way out of this.

Attached are my log files in a tar archive.

[Mihail (mikhail.lukin)]

As I understand, this problem can't be solved normally. To use hibernate/suspend feature I removed proprietary ATI driver. Now it works, but video performance is pretty low.

[Chris Crisafulli (itnet7)]

I have tied basically three similar bugs together under this original one.

3gun, I see that you have already posted most of the debug info from acpi, but please try and see if disabling acpi during booting as suggested with the proprietary driver re-installed will make and difference to the freezing after the suspend. Then try and provide any other missing info from the DebuggingACPI link.

If everyone else could use both links and make one attachment that includes all of the requested output, we can narrow down whether or not this is and acpi-support issue, or possible kernel related issues coming out of suspend.
Thanks for your time in submitting any extra info that can help narrow this down.

Please include the information requested at https://wiki.ubuntu.com/DebuggingACPI as separate attachments, and https://wiki.ubuntu.com/DebuggingGNOMEPowerManager.

I will change the package and status when we have some extra stuff to move forward with, for now I have left it genric package ubuntu, and marked it incomplete since we are awaiting more info and troubleshooting.

[Mihail (mikhail.lukin)]

Thanks, Chris!
Since I have 8.10 I cant find out just how to pass boot params to the kernel :(
There is many more than 3 bug reports on this issue. As far as I understood, the problem is that fglrx is having problems with SLUB-enabled kernels. With this driver uninstalled, suspend/hybernate works fine.
Will https://wiki.ubuntu.com/DebuggingACPI information still be useful for you?

[Mihail (mikhail.lukin)]

Some additional info on this issue. That is what appears in logs just before system hangs when trying to resume:

debug

Jan 24 16:31:01 3gun kernel: [ 572.509799] PM: Finishing wakeup.

syslog

Jan 24 16:31:04 3gun atieventsd[5356]: Enabling displays
Jan 24 16:31:04 3gun atieventsd[5356]: Attempting to enable displaymask FFFFFFFF

[ira (chayut)]

I had a similar problem with Linux Mint (based on Ubuntu 8.10) on my Dell 1521. I deactivated the ATI/AMD video driver and now Suspend works. Hibernate still doesn't work (it tries and then comes back up immediately), but this might be due to the fact that I have a swap file instead of a swap device.

[Crayboff (mwaboff)]

This problem was solved for me when I upgraded to Jaunty :)

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]