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 (Ubuntu)
Status: New = Fix Released
--
Suspend to RAM mostly fails on Ubuntu 8.10 on Optiplex 745
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).
--
Suspend to RAM mostly fails on Ubuntu 8.10 on Optiplex 745
https://bugs.launchpad.net/bugs/294025
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:
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
23) Attached subsequently
** Attachment added: dmesg.log
http://launchpadlibrarian.net/19587070/dmesg.log
--
Suspend to RAM mostly fails on Ubuntu 8.10 on Optiplex 745
** Attachment added: lspci-vvnn.log
http://launchpadlibrarian.net/19587072/lspci-vvnn.log
--
Suspend to RAM mostly fails on Ubuntu 8.10 on Optiplex 745
https://bugs.launchpad.net/bugs/294025
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
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.
** Attachment added: messages
http://launchpadlibrarian.net/19587112/messages
--
Suspend to RAM mostly fails on Ubuntu
** Changed in: linux (Ubuntu)
Status: Incomplete = New
--
Suspend to RAM mostly fails on Ubuntu 8.10 on Optiplex 745
https://bugs.launchpad.net/bugs/294025
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
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
