hibernate/resume failure
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Much the same as Bug #301353 but June 2 2009 comment says to report a new bug if same results are found in another model. I have a DX5000 with same bug. Just upgraded to Ubuntu 9.10 and system does not always restart after hibernate. Needs to be rebooted. Only happens occasionally (once in 10-20 times of starting).
Results of ubuntu-bug -p linux:
/usr/lib/
return self._cache(
/usr/lib/
return self._cache(
/usr/lib/
return self._cache(
hook /usr/share/
Traceback (most recent call last):
File "/usr/lib/
symb[
File "/usr/share/
nm = apport.
AttributeError: 'module' object has no attribute 'nonfree_
hook /usr/share/
Traceback (most recent call last):
File "/usr/lib/
symb[
TypeError: add_info() takes exactly 2 arguments (1 given)
/usr/lib/
if self._cache(
/usr/lib/
origins = self._cache(
ProblemType: KernelOops
Annotation: This occured during a previous hibernate and prevented it from resuming properly.
Architecture: i386
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/
Failure: hibernate/resume
InterpreterPath: /usr/bin/python2.6
Package: linux-image-
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron: PATH=(custom, no user)
ProcVersionSign
SourcePackage: linux
Tags: resume hibernate
Title: hibernate/resume failure
Uname: Linux 2.6.31-9-generic i686
UserGroups:
Hi Bob,
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? Can you try with the latest development release of Ubuntu? ISO CD images are available from http:// cdimage. ubuntu. com/releases/ .
If it remains an issue, could you run the following command from a Terminal (Applications- >Accessories- >Terminal) . It will automatically gather and attach updated debug information to this report.
apport-collect -p linux 425987
Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https:/ /wiki.ubuntu. com/KernelMainl ineBuilds . Once you've tested the upstream kernel, please remove the 'needs- upstream- testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs- upstream- testing' text. Please let us know your results.
Thanks in advance.
[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]