Asus z71v usually fails to recover from suspend-to-ram (since Edgy)

[Stoanhart]

I first started using Ubuntu with Dapper, which suspended and resumed fine. In Dapper, powering on the laptop from suspend mode caused all fans to spin up to full speed for about 10 seconds, then they would quit and the screen would come on.

I am currently (9 Apr. 2007) running an up-to-date beta of feisty. While the system suspends just fine, the laptop fails almost every time to come out of suspend. The fans still come on to full power, but the system just stays in that state until a hard shutdown is performed.

I have had this problem since Edgy. In Edgy, occasionally the system would proceed beyond the fan stage after a very long delay. When that happened, sometimes the X session would appear, and sometimes not. Manually switching to VT7 often brought the laptop into a state where it could at least be shut down properly, but it was definately not properly resumed, as most drivers were not loaded, and many services not running. This has not yet occurred with Feisty, but I have not tested it as extensively yet.

Sometimes, the system does resume. Strangely, it seems to depend on how long it had been suspended for. If the system is put to sleep, then immediately (ie: within a minute or two) resumed, it usually works. Currently, with feisty, it works almost every time. Sometimes in Feisty, on a successful resume, I get a message that VBETool has crashed. I went to submit the bug, but there are already many duplicates. See:

https://bugs.launchpad.net/bugs/90742

When testing Edgy, I tried to debug this problem by going into the /etc/acpi/resume.d/ directory and going through each script, adding debug lines after every significant step that would add to a log file, so that I could see where the process hung up. However, either all of the scripts ran and the system started, or nothing ran at all. Thus, this problem must be in the kernel or some other very early process, since the scripts were never called on failed resumes. Since VBEtool crashes, I suspect it may have something to do with the NVidia card in my laptop.

I have included the lspci and dmesg output, taken immediately upon reboot after a failed resume.

I hope someone has some suggestions, since suspend is critical to my using feisty.

Thank you,
Pascal

[Sitsofe Wheeler (sitsofe)]

Thank you for your bug report.

There are signs of the nvidia binary module in the dmesg output (thanks for attaching it) It's probably worth setting POST_VIDEO=false in /etc/default/acpi-support and seeing if things are any better. If not you could try using NvAGP as described on https://help.ubuntu.com/community/NvidiaLaptopBinaryDriverSuspend ...

[Sitsofe Wheeler (sitsofe)]

Stoanhart:
It would also be interesting to know whether suspend/resume works correctly if you use the nv driver.

[Sitsofe Wheeler (sitsofe)]

Speculatively punting to linux-restricted-modules-2.6.20...

[Stoanhart (stoanhart)]

Thank you for the responses, Sitsofe

I will try the acpi-support stuff. However, I did think of the nv suggestion too, and tried it just a little while before your response. Unfortunately, it still did not recover from suspend, so it seems it may not be related to nvidia afterall. I used the "Restricted Drivers" tool to disable the nvidia driver then restarted the laptop, so I assume that the nvidia kernel modules was not loaded when I went into suspend.

[Sitsofe Wheeler (sitsofe)]

Because this occurs without the nvidia binary drivers too I'm going to punt this over to linux-source as it sounds related to other drivers...

[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)]

*This is an automated response*

This bug report is being closed because we received no response to the previous request for information. Please reopen this if it is still an issue in the actively developed pre-release of Jaunty Jackalope 9.04 - http://cdimage.ubuntu.com/releases/jaunty . To reopen the bug report simply change the Status of the "linux" task back to "New".