Doesn't wake up from system sleep with nForce4 motherboard

Bug #182156 reported by Kyle Dassoff
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

When my computer enters system sleep, it will not wake up. It will return from a display-only sleep, but when the whole computer sleeps, it will not return. The most response I've managed to achieve is a system beep when pressing Ctrl+Alt+Del, but nothing else happens, and the only thing I can do is a hard reset.

nVidia nForce 4 Ultra motherboard from MSI
Athlon 64 3500+ Socket 939
nVidia GeForce 6800GT from Leadtek

Tags: cft-2.6.27
Revision history for this message
Kyle Dassoff (kbjbfg70) wrote :

I'm also using a generic PS/2 keyboard and a Logitech USB mouse that runs through a PS/2 converter.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Kyle,

Can you be a little more specific what you mean by "sleep"? Do you mean you are attempting to Suspend (Suspend to RAM) or are you attempting to Hibernate (Suspend to Disk)? If you are attempting to Suspend (Suspend to Ram) the following wiki may help: https://wiki.ubuntu.com/DebuggingKernelSuspend. Thanks.

Changed in linux:
status: New → Incomplete
Revision history for this message
Kyle Dassoff (kbjbfg70) wrote :

I found out that I had S3 Suspend to RAM disabled in the BIOS, so it was the S1 Standby state that I was having problems with.
Also, I could not find the pm_trace file mentioned in the wiki article, though I am using the latest kernel for Gutsy Gibbon.

I enabled S3 in my BIOS and tested that too. I had a slightly different set of problems waking up from that.
When it awoke I was given the virtual console with kernel messages rather than my desktop. I could manually switch to the virtual console X was running on, but I got only a blank white screen and a responsive mouse pointer. I could kill X with Ctrl+Alt+Backspace, so it was probably a bug caused by Compiz. But then I found my onboard network controllers were not enabled (no connectivity, not even listed in the Network configuration dialog in GNOME) until I reboot my computer, and my sound might not have been enabled either.
Should I file a separate bug for that, since it's waking from a different power state?

Also, my computer will wake fine from both S1 and S3 in Windows, so it shouldn't be a motherboard or BIOS problem.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Kyle,

The Hardy Heron Alpha series was recently released. I was under the impression you were running Hardy. Hardy Alpha2 and subsequent releases contain an updated version of the kernel. You can download and try the new Hardy Heron Alpha release from http://cdimage.ubuntu.com/releases/hardy/ . You should be able to then test the new kernel via the LiveCD. Please note that you can only test Suspend from the LiveCD, not Hibernate. If you can, please verify if this bug still exists or not and report back your results. General information regarding the release can also be found here: http://www.ubuntu.com/testing/ . Thanks!

Revision history for this message
Kyle Dassoff (kbjbfg70) wrote :

Hi,
I tested with the Hardy Alpha 3 LiveCD in both S1 and S3 sleep modes.
With my BIOS set to S1, the Suspend button was missing in the Quit dialog in Gnome. The sleep option in the Power Management settings was not, so I let my computer idle until it went to S1. Once the idle time sent it to S1, I was switched to a virtual terminal with the kernel message 'kbd activation failed'. Then my computer shut down entirely.

With my BIOS set to S3, I could click the Suspend button. But when I pressed the power button to wake up the computer, I received no display, and my computer was unresponsive as far as I could tell. All I could do was a hard reset. After rebooting my computer, I still don't get a display until I turn off my monitor and turn it back on. My system clock is now also off by 6 hours in the future.

Hope this helps.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Thanks Kyle,

Hardy Alpha 4 will be out within a day or two. It would be helpful if you could restest and just verify the issue still exists. If the issue still exists, if you could attach your dmesg output after a suspend/resume cycle as outlined in https://wiki.ubuntu.com/DebuggingKernelSuspend that would also be helpful. Thanks.

Revision history for this message
Connor Imes (ckimes) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

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.

Revision history for this message
Connor Imes (ckimes) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.