asus eeepc 1101HA won't resume under linux 3.0.0.12; works under 2.6.38

[Jan]

See title. Suspend appears to work fine, the system will suspend and lights start to blink as they should to indicate suspended state, but once suspended the system does not wake up, it does not respond in any way to keyboard/power button/anything, and stays suspended. The only way to recover is to do a hard reset. This is new since upgrading to Oneric with kernel 3.0.0. If I reboot under kernel 2.6.38, suspend/resume works fine, so this is a regression.

(I am also having problems with the video driver, as this system has a poulsbo card, but those appear to be unrelated. The bug persists if I boot with VESA X driver, and under 2.6.38 it also works fine with poulsbo driver.)

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-12-generic 3.0.0-12.20
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: MID [HDA Intel MID], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
ApportVersion: 1.23-0ubuntu3
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: MID [HDA Intel MID], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: jellien 1678 F.... pulseaudio
CRDA: Error: [Errno 2] Bestand of map bestaat niet
Card0.Amixer.info:
 Card hw:0 'MID'/'HDA Intel MID at 0xf3f38000 irq 23'
   Mixer name : 'Realtek ALC269'
   Components : 'HDA:10ec0269,104383ce,00100004'
   Controls : 12
   Simple ctrls : 7
Date: Mon Oct 24 15:41:45 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 002: ID 13d3:5071 IMC Networks
MachineType: ASUSTeK Computer INC. 1101HA
ProcEnviron:
 PATH=(custom, no user)
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=9fb48e72-ce5e-4724-a3be-afc517fb52d9 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-12-generic N/A
 linux-backports-modules-3.0.0-12-generic N/A
 linux-firmware 1.60
SourcePackage: linux
UpgradeStatus: Upgraded to oneiric on 2011-10-20 (3 days ago)
dmi.bios.date: 06/17/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0205
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1101HA
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0205:bd06/17/2009:svnASUSTeKComputerINC.:pn1101HA:pvrx.x:rvnASUSTeKComputerINC.:rn1101HA:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 1101HA
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

[Jan (jankanis)]

For completeness, the video driver bug is #880882. Probably unrelated, but you never know.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please test the latest release candidate kernel (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the others). 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.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.1-rc9 fixed and issue, the tag would be: 'kernel-fixed-upstream-v3.1-rc9'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Thanks in advance.

[Jan (jankanis)]

I tested with the mainline kernel, both version 3.1-rc10 and v3.1 final. Both still have the problem.

I additionally ran into some trouble in that the boot screen would freeze with "waiting for network configuration", and the system would not respond to any keypresses anymore (but sshing into it still worked). If I changed to a different virtual terminal before the freeze, X would start properly, but on the first login attempt X crashes and shows some random characters on a console, before a restarted X would come up. Logging in on this new X instance works normally.
While the boot screen was frozen or while the first instance of X was running, I was unable to change virtual terminals, either through (ctrl+)alt+fnX or through the chvt command in an ssh session. chvt just hangs indefinitely. Once the first X session has been replaced by the second, this all works normally.
These boot anomalities do not occur with ubuntu distribution kernels.

Since I'm also having other problems with the video card of this machine, I also tried blacklisting the poulsbo and/or psb_gfx kernel modules, and running X in vesa or fbdev mode (fbdev is the default, there is no working driver that allows X to not use fbdev), but none of these seemed to have any effect in any way on the suspend/resume bug.

[Jan (jankanis)]

fwiw, the problem is fixed in ubuntu 12.04, suspend and resume works again.

[penalvch (penalvch)]

Jan, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/880865/comments/5 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.