[ASUSTeK Computer Inc. A6VA] suspend/resume failure

Bug #334587 reported by lifi
36
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

clean install, tried it after the first boot and it hung after trying to resume from suspend

ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InterpreterPath: /usr/bin/python2.5
Lsusb:
 Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 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 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: ASUSTeK Computer Inc. A6VA
Package: linux-image-2.6.28-8-generic 2.6.28-8.26
ProcAttrCurrent: unconfined
ProcCmdLine: User Name=UUID=10fc2ac3-acb4-49ca-b220-a92215a191ab ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-8.26-generic
SourcePackage: linux
StressLog: Error: [Errno 2] No such file or directory: '/var/lib/pm-utils/stress.log'
Tags: resume suspend
Title: [ASUSTeK Computer Inc. A6VA] suspend/resume failure
UserGroups:

Revision history for this message
lifi (lifi) wrote :
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

*This is an automated response*

Could you please take a look the triage and debugging guide at https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume, specifically the Information Gathering section. Please provide any answers to the additional questions outlined there. Thanks.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
staho (staho) wrote :

Information Gathering
• Did the machine break while going to sleep or waking up?
It seems to be at wakeup: after suspend the diode is blinking, so it should be. Then I push the power button and the computer begins the wakeup, yet the screen never goes on and there is no reaction for the keyboard.
• Is it reproducible?
Yes. 100%.
• Did it work before?
It did. I may be wrong, but it did work in stable 8.10. In late 8.10 at least.
• Do you end up with flashing caps-lock or similar?
No, just some disk activity and pure darkness, including LEDs.
• Hibernate specific information.
n/a
• Other information.
none

I hope it helps.

Revision history for this message
Shiranui (yoann-seu) wrote :

I had the same problem in 8.10. However, when ATi proprietary drivers are enabled, the laptop does resume.

Revision history for this message
lifi (lifi) wrote :

Bad luck... I can't test it anymore, because my notebook is broken... -.- I can confirm the information from staho.

@Shiranui... Well, Could be... But the proprietary driver doesnt support my gpu in jaunty...

Revision history for this message
r2d2 (r2d2-c3p0) wrote :

Yes... It's like in other versions of ubuntu: without fglrx it's a 'one way' in standby. But with fglrx I got meny problems. So I wait a little...

Revision history for this message
Shiranui (yoann-seu) wrote :

Problem remains in Jaunty final. Anything we can do to get it fixed?

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi lifi,

I just want to try to keep this up to date. Can anyone confirm this issue remains with the latest Karmic 9.10 Alpha development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/karmic . You should be able to test suspend using a LiveCD. Please let us know your results. Thanks.

Revision history for this message
Shiranui (yoann-seu) wrote :

This issue remains with Karmic Alpha 3 (Live CD), in a different way though: the laptop won't enter suspend mode. Screen turns black with a blinking caret and nothing happens.

Revision history for this message
r2d2 (r2d2-c3p0) wrote :

Tested today (installed from iso image alpha 3)

The behaviour is like it was before: Suspend to disk works fine (with "hibernate" or not - I don't know) - Suspend to RAM shut the machine down, but on key press (any key for me like enter or spatium) results in a black screen.

After update to latest kernel (and after reboot) the same problem. But it looks like a kernel problem, because ping or ssh says "unreachable".

...But suspend to disk works fine ;-)

I will make any tests next days...

neo

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Incomplete → Triaged
Revision history for this message
Yann Dìnendal (yannbreliere) wrote :

I have the same problem: when I do "Mettre en veille" (I think it's "suspend to RAM"), it looks like it succeed suspending, but when I try to resume, it looks like there is some activity but the screen remains desperately black.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Triaged a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Triaged → Won't Fix
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.