Andreas Hohenegger, 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-rc5 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. ** Description changed: - I am opening a new bug for this issue because the previously reported bug - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/785078 - does not allow me to submit requested details as it was reported by others. No information about the current state was provided by the previous reporters. - The symptom is that occasionaly after resume from suspend or hibernate (possibly only if both are used after each other) the system does not restore. Instead the screen is in console mode and shows a message like PM: Device 00:0b failed to resume: error -19 It is not possible to change to a terminal or perform any other action than forced shutdown. So the complete workspace is lost. The message above is sometimes also shown after successfull resume so it does not need to be the reason for the system freeze. I will try provide more information as soon as the bug shows in my logs. My system is the current ubuntu 11.10 on a Lenovo thinkpad T61 (same as that of previous reporters) with intel grapics. No ultrabay connected (this has been an issue in previous reports). ** Tags added: needs-kernel-logs ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/979801 Title: resume from suspend still fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/979801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
