kernel problem on suspend - EEE PC 1000HE

[tadr]

After a suspend (which failed to resume) I recieved a KDE notification that there had been a some kernel problem during suspend.

I had a freshly updated Jaunty kubuntu as of yesterday (2009-04-10).
Great work on improving the support for this netbook BTW. I barely know what gcc is but I know my way around grub and would be glad to help debug this.

tadr@spaz:~$ uname -a
Linux spaz 2.6.28-11-generic #41-Ubuntu SMP Wed Apr 8 04:38:53 UTC 2009 i686 GNU/Linux

ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly. The resume processing hung very near the end and will have appeared to have completed normally.
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: late resume
InterpreterPath: /usr/bin/python2.6
MachineType: ASUSTeK Computer INC. 1000HE
Package: linux-image-2.6.28-11-generic 2.6.28-11.41
ProcAttrCurrent: unconfined
ProcCmdLine: root=UUID=ef27dd29-3d28-41bc-ad1d-4a781f9df9cf ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-11.41-generic
SourcePackage: linux
Tags: resume suspend resume-late-hang
Title: [ASUSTeK Computer INC. 1000HE] late resume failure
UserGroups:

[Jeffrey Hearn (cowbellemoo)]

Is this error reproducible? Does it always fail to suspend properly, or only sometimes, such as with this previous bug report (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/353122)?

[tadr (tom-a-d-riley)]

This is a question I should have asked myself before filing the bug report.

I set the lid close event to "suspend to disk" reboooted, closed lid,
resumed, suspended, and resumed. Repeated this 5 times:
no problems with resume. WLAN reconnect was hit and miss.

I did the same thing with "suspend to ram". Same results.

However I did run into the error message one more time in some tests before
I got organized about it :(

On Sat, Apr 11, 2009 at 12:30 PM, Jeffrey Hearn <email address hidden>wrote:

> Is this error reproducible? Does it always fail to suspend properly, or
> only sometimes, such as with this previous bug report
> (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/353122)?
>
> --
> kernel problem on suspend - EEE PC 1000HE
> https://bugs.launchpad.net/bugs/359646
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” source package in Ubuntu: New
>
> Bug description:
> After a suspend (which failed to resume) I recieved a KDE notification that
> there had been a some kernel problem during suspend.
>
> I had a freshly updated Jaunty kubuntu as of yesterday (2009-04-10).
> Great work on improving the support for this netbook BTW. I barely know
> what gcc is but I know my way around grub and would be glad to help debug
> this.
>
> tadr@spaz:~$ uname -a
> Linux spaz 2.6.28-11-generic #41-Ubuntu SMP Wed Apr 8 04:38:53 UTC 2009
> i686 GNU/Linux
>
> ProblemType: KernelOops
> Annotation: This occured during a previous suspend and prevented it from
> resuming properly. The resume processing hung very near the end and will
> have appeared to have completed normally.
> Architecture: i386
> DistroRelease: Ubuntu 9.04
> ExecutablePath: /usr/share/apport/apportcheckresume
> Failure: late resume
> InterpreterPath: /usr/bin/python2.6
> MachineType: ASUSTeK Computer INC. 1000HE
> Package: linux-image-2.6.28-11-generic 2.6.28-11.41
> ProcAttrCurrent: unconfined
> ProcCmdLine: root=UUID=ef27dd29-3d28-41bc-ad1d-4a781f9df9cf ro quiet splash
> ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
> ProcEnviron: PATH=(custom, no user)
> ProcVersionSignature: Ubuntu 2.6.28-11.41-generic
> SourcePackage: linux
> Tags: resume suspend resume-late-hang
> Title: [ASUSTeK Computer INC. 1000HE] late resume failure
> UserGroups:
>

[Jeffrey Hearn (cowbellemoo)]

Seems to be a periodic problem like the other bug. I'm going to mark this one as a duplicate report and the other as confirmed.