Ubuntu 10.10 crashes on resume from suspend on Asus Eee 701

Bug #663784 reported by Christopher Neville-Smith
48
This bug affects 9 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

When I suspend my Asus Eee 701 (either manually or by closing the lid), the system crashes on resume. It sometimes shows the mouse pointer, but that doesn't move.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-22-generic-pae 2.6.35-22.35
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic-pae 2.6.35.4
Uname: Linux 2.6.35-22-generic-pae i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: chris 1421 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf3eb8000 irq 44'
   Mixer name : 'Realtek ALC269'
   Components : 'HDA:10ec0269,10438330,00100004'
   Controls : 11
   Simple ctrls : 7
Date: Wed Oct 20 11:20:16 2010
HibernationDevice: RESUME=UUID=4891c0b5-67e4-466b-b16f-94a54da6b765
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Beta i386 (20100318)
MachineType: ASUSTeK Computer INC. 701SD
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic-pae root=UUID=a17186d0-8dd1-4d86-a575-5875e708382e ro quiet splash
ProcEnviron:
 LANG=en_GB.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
RfKill:
 0: eeepc-wlan: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
StagingDrivers: r8187se
Title: [STAGING]
WifiSyslog:

dmi.bios.date: 10/06/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0602
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 701SD
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.:bvr0602:bd10/06/2008:svnASUSTeKComputerINC.:pn701SD:pvr0501:rvnASUSTeKComputerINC.:rn701SD:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 701SD
dmi.product.version: 0501
dmi.sys.vendor: ASUSTeK Computer INC.

Revision history for this message
Christopher Neville-Smith (chris-neville-smith) wrote :
Revision history for this message
Giulio Franco (giulio-franco) wrote :

I have the same problem on a MSI Wind U100.
I can avoid the crash either calling s2ram from a terminal or disabling wifi before it reconnects and then killing and restarting NetworkManager.

Revision history for this message
Giulio Franco (giulio-franco) wrote :

Solved on my pc by adding the line:
SUSPEND_MODULES="r8187se"
to the file /etc/pm/config.d/unload_module. This way, the wifi driver, which caused my pc to freeze, is unloaded before suspend and reloaded on resume.
May work on EeePc too, replacing r8187se (which is my wifi card) with the eeepc wifi module name.

Revision history for this message
Christopher Neville-Smith (chris-neville-smith) wrote :

Okay, I can add that when the wireless is disabled, you can safely suspend and resume without the crash, so, yes, it looks like the wireless driver is causing the crash.

I'll look into adding the relevant line to the relevant file, but any chance of a permanent fix?

Revision history for this message
NateC (natec99) wrote :

Nice! G Franco's fix (comment #3) seems to have worked on my MSI Wind U100 after first test.

I think there are many duplicates of this problem.

Revision history for this message
Jason Mitchell (jvonmitchell) wrote :

Giulio F deserves an upvote, if launchpad had upvotes.

Revision history for this message
wavesailor (wavesailor) wrote :

My Fujitsu Lifebook S7020 does the same thing when resuming from suspend. It does not do it all the time and the only pattern I can find is that if I quickly log-in then it does not do it i.e. I use the "blank" screen-saver with password protection on.

Not sure if the solution above would work for me as I have a different wi-fi card (Intel Corporation PRO/Wireless 2200BG)

Revision history for this message
wavesailor (wavesailor) wrote :

I did notice the was the last entry in kernel.log:
Feb 2 10:14:45 LIFEBOOK-S7020 kernel: [31140.448476] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id

Not sure what it means??

Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Matthew Wire (devel-mrwire) wrote :

Also affects me on 11.10. Fix in #3 works for me.

Revision history for this message
penalvch (penalvch) wrote :

Christopher Neville-Smith, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, could you please provide the information following https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume ? As well, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ . However, note you can only test Suspend, not Hibernate, when using a LiveCD. If the issue remains, run the following command in the development release from a Terminal (Applications->Accessories->Terminal) as it will automatically gather and attach updated debug information to this report.

apport-collect -p linux <BUGNUMBER>

Additionally, if you could try to reproduce this with the upstream mainline kernel 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.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

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

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thanks in advance.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.