Suspend to disk fails on Asus A8N-E

Hi Chris,

Care to try updating to the 2.6.24-14 kernel. Assuming the issue still exists, care to attach your dmesg output after an attempted suspend/resume cycle as outlined here: https://wiki.ubuntu.com/DebuggingKernelSuspend . Thanks.

I've upgraded to the 2.6.24-14 kernel - still the same. When I hibernate, the screen turns off and the disks stop, but all the fans and lights stay on. And it doesn't resume.

Suspend-to-RAM behaves slightly differently. I can do one suspend-resume cycle, but it fails on the second attempt if I don't do a proper reboot in between. The failure behaves similar (screen goes off and disks stop, but fans and lights stay on).

I've gone through the procedure in the wiki. I did one successful suspend-resume cycle, using the 'sync; echo 1 > /sys/power/pm_trace; /etc/acpi/sleep.sh force' command, and then I did a second one with the same command (which failed as expected). I had to hold the power button to switch the machine off and then reboot as normal.

I've attached the dmesg output as requested, but it's flooded with 'attempt to access beyond end of device' messages (because I'm using DMRAID, see bug 106177), so I've also attached the relevant part of my kern.log (covering both suspend-resume cycles).

To complicate matters, if I do 'sync; echo 1 > /sys/power/pm_trace; /etc/acpi/hibernate.sh force', then suspend-to-disk works consistently every time. Maybe my suspend-to-disk problem is actually related to something higher up (g-p-m?), and my suspend-to-ram problem is a completely different issue.

Thanks Chris.

Would you mind maybe opening up a new bug report regarding the Hibernate issues you are experiencing. It's helpful to the development teams if bug reports target one specific issue. The Hibernate issues may not in fact be kernel related since you mentioned you are able to successfully hibernate from the command line each time.

We'll focus this report on the Suspend/Resume issues you are seeing. I'm reassigning to the kernel team. Thanks.

Leann - I think it might be better to keep the hibernate (suspend to disk) issue in this report (as that was the original issue), and for me to open a new report for suspend to RAM (which you could assign to the kernel team), unless I can change the title of this report (which currently states suspend to disk aka hibernate).

What do you think?

Right, I've done a bit more digging around regarding suspend-to-disk (hibernate). As I stated above, doing 'sync; echo 1 > /sys/power/pm_trace; /etc/acpi/hibernate.sh force' resulted in a successful hibernate-resume cycle. I noticed from my kern.log that when I do that command, I see this line in the log:

Apr 9 18:45:08 chris-desktop kernel: [ 144.098126] PM: suspend-to-disk mode set to 'shutdown'

However, if I hibernate from within GNOME, I see something like:

Apr 9 18:45:08 chris-desktop kernel: [ 144.098126] PM: suspend-to-disk mode set to 'platform'

So I've modified /etc/default/acpi-support and changed HIBERNATE_MODE from shutdown to platform, then attempted the following again (after a reboot):

'sync; echo 1 > /sys/power/pm_trace; /etc/acpi/hibernate.sh force'

This time, the hibernate failed (disks stopped but fans stay on and everything stays lit up - which is the behaviour I see when I hibernate from GNOME), so I had to hold the power button down to turn the machine off. However, when I powered up, it appeared to resume successfully.

Here are the relevant bits of kern.log to go with the above post

I have exactly the same symptoms with kernel 2.6.24-18 on Hardy with an Asus A8SC (though I haven't investigated in as much depth). If I can be of help then please let me know - I'll subscribe to this bug report.

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,

I'll have a go once 2.6.27 is on the daily live CD ISO. In the meantime, I would have tried with 2.6.26, but I can't do that because DMRAID doesn't work for me in Intrepid at the moment, which means I can't mount my swap partition to do the suspend-to-disk :(

i have got a ASUS A8N SLI DELUXE and i have the same problem with Hardy

Now i tried it with intrepid beta, yhe problem now is quite different (not a lot)
the ibernation almost works :
i click on ibernate but after ibernating the pc doesn't turn off (the fans are still turning), i have to unplug power by hand. when i turn it on it resumes correctly
suspension doesn't work as before

should i leave more detail? how? which detail?

I hope to be userrful

thank you a lot

lspci -vvnn and dmideconde are saved after resuming from hibernate
do you need something else? logs after failed suspension?

another testimonial:
a8sc, ubuntu intrepid.
suspend and hibernate do not resume. It worked well with kubuntu 8.04.
Let me know if I should leave any more details here.

thanks

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.

Hope it's useful for anyone: I activated the restricted nvidia driver, and my suspension troubles are over.
(now I have other X issues :) )

FYI, you need to use shutdown instead of platform to suspend this motherboard to disk properly.

At least on Debian you can make shutdown the default mode for g-p-m (and all other pm-utils users) by creating a new file in /etc/pm/config.d with the following line:
HIBERNATE_MODE=shutdown

I'm using the proprietary nVidia driver with this Asus motherboard and I've always had the same symptoms. I recently upgraded to 2.6.28 and the problem with platform mode still persists.

I still don't know how to make a similar change for suspend to ram, or if it would help at all :-(

i have also the same problem with jaunty
cant suspend to ram

Thanks Javier Kohen - adding a file to /etc/pm/config.d as you suggested has enabled me to successfully hibernate my a8n-sli-delux with a Geforce 6600GT running the nVidia 190.42 driver under Karmic.

I was also able to get suspend to ram working from this post:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/347150/comments/12

Chris Coulson, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]