[Acer, inc. Aspire 4530] suspend/resume failure

[Asif Youssuff]

This time without the nvidia blob...

ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InterpreterPath: /usr/bin/python2.6
MachineType: Acer, inc. Aspire 4530
Package: linux-image-2.6.28-11-generic 2.6.28-11.41
ProcAttrCurrent: unconfined
ProcCmdLine: root=UUID=174a75e7-79b8-415d-9b91-d8f326394e3a ro quiet splash quiet
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
Title: [Acer, inc. Aspire 4530] suspend/resume failure
UserGroups:

[Leann Ogasawara (leannogasawara)]

I pointed @yoasif to the following wiki:

https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume

[Asif Youssuff (yoasif)]

I rebooted using the no_console_suspend option in grub.

After initiating a pm-suspend in VT1, the computer appeared to suspend successfully. The power button/light blinked slowly with an amber color.

I attempted to resume the machine by pressing the power button.

no output appeared on the screen, and the machine did not successfully resume. the machine began to wake up (the dvdrom made a seek/turn on sound and the hdd light blinked a bit), but besides that, nothing.

tried it a total of three times, nothing each time. trying to show VT1 again did nothing as well.

...

then i tried Suspend Debugging, dmesg | grep "hash matches" returns:

[ 5.208328] hash matches /build/buildd/linux-2.6.28/drivers/base/power/main.c:350
[ 5.208340] scsi_device 0:0:0:0: hash matches
[ 5.208344] scsi_disk 0:0:0:0: hash matches
[ 5.208346] sd 0:0:0:0: hash matches

not sure exactly where to go from here, so i'd appreciate some help in tracking this down.

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.