Suspend to RAM mostly fails on Ubuntu 8.10 on Optiplex 745

Bug #294025 reported by Nikolaj Sheller
16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned
Nominated for Intrepid by Nikolaj Sheller
Nominated for Jaunty by Nikolaj Sheller

Bug Description

Suspend to RAM occasionally works, but most often fails on Ubuntu Intrepid Ibex 8.10.

When a suspend fails, the following occurs:
1) suspend is selected
2) X screen-saver starts, then hangs
3) Computer never enters suspend
4) Hard drive light flashes occasionally

Power-off is required to get out of this state.

This is seen on a Dell OptiPlex 745 Core 2 6600 with RV516 [Radeon X1300/X1550 Series].
Two monitors are attached (Dual Head), using the radeon 1.29.0 20080528 driver (according to messages log).
According to Synaptic xserver-xorg-video-radeonxserver-xorg-video-ati version 1:6.9.0+git20081003.f9826a56-0ubuntu2 are installed.

Kernel: 2.6.27-7-generic #1 SMP Thu Oct 30 04:12:22 UTC 2008 x86_64 GNU/Linux

Last statements in log when suspend is invoked:

Nov 4 17:06:56 nsh -- MARK --
Nov 4 17:26:56 nsh -- MARK --
Nov 4 17:40:29 nsh kernel: [30894.216729] [drm] Num pipes: 1
Nov 5 08:23:11 nsh syslogd 1.5.0#2ubuntu6: restart.

Revision history for this message
Ian Weisser (ian-weisser) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.

Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance!

Revision history for this message
Nikolaj Sheller (nikolajsheller) wrote :

Here is the requested information:

1) Linux nsh 2.6.27-7-generic #1 SMP Tue Nov 4 19:33:06 UTC 2008 x86_64 GNU/Linux
2&3) Attached subsequently

Revision history for this message
Nikolaj Sheller (nikolajsheller) wrote :
Revision history for this message
Nikolaj Sheller (nikolajsheller) wrote :

Dump of "messages" prior to attached dmesg.log.
The computer had survived a suspend/resume cycle in this log, before failing suspend at the end of attached "messages" file.

Changed in linux:
status: Incomplete → New
Revision history for this message
Nikolaj Sheller (nikolajsheller) wrote :

I tried suspending the machine today, this time with my screensaver disabled.
The machine usually freezes showing the screensaver.
The machine tried to suspend, and then resumed spontaneously without entering suspend.

The following stacktrace appears multiple times:
Nov 14 16:25:52 nsh kernel: [28377.135492] [<ffffffff8027ed4d>] refrigerator+0xed/0x140
Nov 14 16:25:52 nsh kernel: [28377.135494] [<ffffffff8025ebcd>] get_signal_to_deliver+0x28d/0x3a0
Nov 14 16:25:52 nsh kernel: [28377.135496] [<ffffffff80212945>] ? sysret_signal+0x3d/0x67
Nov 14 16:25:52 nsh kernel: [28377.135499] [<ffffffff802124a5>] do_signal+0x75/0x200
Nov 14 16:25:52 nsh kernel: [28377.135501] [<ffffffff80275830>] ? futex_wake+0x100/0x130
Nov 14 16:25:52 nsh kernel: [28377.135503] [<ffffffff802475b0>] ? default_wake_function+0x0/0x10
Nov 14 16:25:52 nsh kernel: [28377.135505] [<ffffffff80276ca6>] ? do_futex+0x86/0x140
Nov 14 16:25:52 nsh kernel: [28377.135507] [<ffffffff80276e1c>] ? sys_futex+0xbc/0x150
Nov 14 16:25:52 nsh kernel: [28377.135510] [<ffffffff80212945>] ? sysret_signal+0x3d/0x67
Nov 14 16:25:52 nsh kernel: [28377.135512] [<ffffffff8021265d>] do_notify_resume+0x2d/0x50
Nov 14 16:25:52 nsh kernel: [28377.135514] [<ffffffff80212ce7>] ptregscall_common+0x67/0xb0

Revision history for this message
Nikolaj Sheller (nikolajsheller) wrote :

This issue seems to have disappeared.
I wonder if some kernel or driver update has resolved the issue?

The scary-looking stacktraces are not present in recent suspend/resume logs (2009-01-27).

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

Since Nikolaj is the original bug reporter and has commented that his appears to have been resolved after an update I'm going to go ahead and close this report. Thanks.

Changed in linux:
status: New → Fix Released
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.