[TOSHIBA Satellite A30] hibernate/resume failure

[fossfreedom]

resumes after hibernate. However find that cannot connect to the internet (using wicd). Standard client apps seems to function correctly.

Also cannot reboot - nothing happens when choosing reboot option. Have to force a power off and restart. At this point apport wants to report a crash - hence this is why I'm filing this bug.

Very repeatable - basically I cannot resume fully after a hibernate

ProblemType: KernelOops
Annotation: This occured during a previous hibernate and prevented it from resuming properly.
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: hibernate/resume
InterpreterPath: /usr/bin/python2.6
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 002: ID 15d9:0a4c
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: TOSHIBA Satellite A30
Package: linux-image-2.6.28-11-generic 2.6.28-11.40 [modified: lib/modules/2.6.28-11-generic/kernel/sound/pci/ac97/snd-ac97-codec.ko lib/modules/2.6.28-11-generic/kernel/sound/pci/ali5451/snd-ali5451.ko lib/modules/2.6.28-11-generic/kernel/sound/pci/au88x0/snd-au8810.ko lib/modules/2.6.28-11-generic/kernel/sound/pci/au88x0/snd-au8820.ko lib/modules/2.6.28-11-generic/kernel/sound/pci/au88x0/snd-au8830.ko]
ProcAttrCurrent: unconfined
ProcCmdLine: root=UUID=7896b067-cfdb-436e-a24e-13a66b66f0ba ro noapic quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-11.40-generic
SourcePackage: linux
Tags: resume hibernate
Title: [TOSHIBA Satellite A30] hibernate/resume failure
UserGroups:

[Jeremy Foshee (jeremyfoshee)]

Hi DavidM,

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/lucid.

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 356478

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/KernelMainlineBuilds . 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.]

[fossfreedom (fossfreedom)]

Hi there,
  due to a regression in lucid (wireless does not work https://bugs.launchpad.net/bugs/539794 ) I cannot test this bug yet. When the kernel developers fix this bug I will revisit this bug.

thanks

[fossfreedom (fossfreedom)]

I downloaded and installed the following mainline kernel:
2.6.34-999-generic_2.6.34-999.201003151003_i386

I've managed 3 hibernate and resumes + 3 sleep and resumes. The wireless works correctly.

Therefore, upstream at least this issue has been resolved.

However as I said above, I cannot test the current lucid kernel due to the wireless regression.

Hopefully when this is resolved,, I can repeat the tests.

thanks

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]