On resume from suspend, system is unresponsive

[strowger]

Acer Aspire One notebook crashes on resume from suspend.

Happens every resume, same every time.

On resume, the previous screen display is restored, but the keyboard and mouse are unresponsive. System appears to be completely hung.

This doesn't appear to be an exact duplicate of any other bugs - I may of course be wrong - but the key points are

  * Happens every time.
  * Previous display is restored, am never left with blank screen.

ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: strowger 2400 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0x58540000 irq 16'
   Mixer name : 'Realtek ALC268'
   Components : 'HDA:10ec0268,1025015b,00100101'
   Controls : 9
   Simple ctrls : 6
Date: Sat Sep 19 22:19:46 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InterpreterPath: /usr/bin/python2.6
MachineType: Acer AOA110
Package: linux-image-2.6.31-10-generic 2.6.31-10.34
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-10-generic root=UUID=f7f623ca-4e1d-4c69-b2b9-c90ff6ecec36 ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-10.34-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-10-generic N/A
 linux-firmware 1.19
SourcePackage: linux
Tags: resume suspend ubuntu-unr
Title: [Acer AOA110] suspend/resume failure
Uname: Linux 2.6.31-10-generic i686
UserGroups:

dmi.bios.date: 10/06/2008
dmi.bios.vendor: Acer
dmi.bios.version: v0.3309
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAcer:bvrv0.3309:bd10/06/2008:svnAcer:pnAOA110:pvr1:rvnAcer:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
dmi.product.name: AOA110
dmi.product.version: 1
dmi.sys.vendor: Acer

[strowger (strowger)]

Exactly the same behaviour using the previous (2.6.31-9-generic) kernel, and the 2.6.31-7-generic kernel I also had.

Exactly the same behaviour running "sudo pm-suspend" at the console.

[strowger (strowger)]

Possibly related to/same bug as #389784.

I do not have any memory cards or USB devices attached.

[strowger (strowger)]

Booting the system with "pciehp.pciehp_force=1" in the kernel commandline fixes this.

I can now reliably resume the system from suspend.

[Jeremy Foshee (jeremyfoshee)]

Hi strowger,

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 433268

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

[strowger (strowger)]

Seems fixed for me as of 2.6.31-20.