[ASUSTeK Computer Inc. F3JP] suspend/resume failure
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Similar to
https:/
I suspect that the suspend fails if it is repeated suspend. Tried to suspend after boot, the wake up imediately after suspend was succesful.
ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfebfc000 irq 16'
Mixer name : 'Realtek ALC660-VD'
Components : 'HDA:10ec0660,
Controls : 23
Simple ctrls : 15
Date: Thu Oct 29 19:57:43 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/
Failure: suspend/resume
HibernationDevice: RESUME=
InterpreterPath: /usr/bin/python2.6
MachineType: ASUSTeK Computer Inc. F3JP
Package: linux-image-
ProcCmdLine: root=UUID=
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron: PATH=(custom, no user)
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.24
SourcePackage: linux
Tags: resume suspend
Title: [ASUSTeK Computer Inc. F3JP] suspend/resume failure
Uname: Linux 2.6.31-14-generic i686
UserGroups:
WpaSupplicantLog:
dmi.bios.date: 05/23/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 208
dmi.board.
dmi.board.name: F3JP
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: F3JP
dmi.product.
dmi.sys.vendor: ASUSTeK Computer Inc.
Hi Vaidotas,
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 463541
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/KernelMainl ineBuilds . 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.]