[ASUSTeK Computer INC. 1000HE] suspend/resume failure

Bug #415855 reported by Nicholas Christian Langkjær Ipsen
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

My WiFi connectivity is always very stable after resuming from suspend, this may be the cause. The error report window opened up during an apt-get update.

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: 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: seph 2904 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf7eb8000 irq 16'
   Mixer name : 'Realtek ALC269'
   Components : 'HDA:10ec0269,1043834a,00100004'
   Controls : 12
   Simple ctrls : 7
Date: Tue Aug 18 21:43:09 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=20f7898f-a979-4ed8-aa9e-190307590694
InterpreterPath: /usr/bin/python2.6
MachineType: ASUSTeK Computer INC. 1000HE
Package: linux-image-2.6.31-6-generic 2.6.31-6.25
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-6-generic root=UUID=f654b4ca-80d3-4feb-8dfc-57e106991a4a ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-6.25-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-6-generic N/A
 linux-firmware 1.16
SourcePackage: linux
Tags: resume suspend ubuntu-unr
Title: [ASUSTeK Computer INC. 1000HE] suspend/resume failure
Uname: Linux 2.6.31-6-generic i686
UserGroups:

dmi.bios.date: 03/05/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0607
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1000HE
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.:bvr0607:bd03/05/2009:svnASUSTeKComputerINC.:pn1000HE:pvrx.x:rvnASUSTeKComputerINC.:rn1000HE:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 1000HE
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

Revision history for this message
Nicholas Christian Langkjær Ipsen (ncli) wrote :
Revision history for this message
^_Pepe_^ (jose-angel-fernandez-freire) wrote :

Hi,

Please, can you tell us whether this is still an issue for you?

If so, please, can you include new logs with last kernel, 2.6.31-16? You just only have to run the following command from a
Terminal (Applications->Accessories->Terminal) while running Karmic. It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 415855.

I'd also encourage you to test last kernel version (Lucid upstream) 2.6.32 located on http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32/ and come back here with your results.

Thanks in advance

tags: added: karmic
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
^_Pepe_^ (jose-angel-fernandez-freire) wrote :

Thank you for taking the time to report this crash and helping to make
Ubuntu better. This particular crash has already been reported and is a
duplicate of bug #445437, so is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Please continue to report any other bugs you may
find.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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