[Acer Aspire 1350] suspend/resume problem

Bug #330647 reported by AlbertH
4
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Resume process fails on my Acer Aspire 1350.

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
InterpreterPath: /usr/bin/python2.5
Lsusb:
 Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 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
OopsText: suspend/resume problem

Originator: Steve Conklin <email address hidden>
Package: linux-image-2.6.28-7-generic 2.6.28-7.20
ProcAttrCurrent: unconfined
ProcCmdLine: User Name=UUID=0f1170a7-6826-4e38-a0d7-6d8353a908d9 ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-7.20-generic
SourcePackage: linux
StressLog: Error: [Errno 2] No such file or directory: '/var/lib/pm-utils/stress.log'
Tags: resume suspend
Title: suspend/resume problem
UserGroups:

Revision history for this message
AlbertH (alberthilbert) wrote :
Revision history for this message
Andy Whitcroft (apw) wrote :

Did the machine break while going to sleep, or while coming back from sleep? Is this reproducible say over 10 cycles. Has suspend ever worked in the past, if so which kernel release (cat /proc/version_signature)? Please include any information as to the circumstances leading up to this failure, for example did your battery run out? Did the machine lock up, did any messages come out? If it is reproducible could you try the suspend from VT1, press ctrl-alt-F1, login, and run pm-suspend there. If you could test and report back here that would be helpful.

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

The sleeping process seems to work fine, the problem arises resuming the machine. Latter process seems never to be completed and stops right after the LCD back-light is turned on (but the screen remains black). At that point, the keyboard seems not to work, for example nothing happens pressing Caps-Lock.
If I resume after a suspend from VT1, the screen is restored but the keyboard still doesn't work, moreover the following message is displayed every 60 - 70 seconds:
BUG: soft lockup - CPU#0 stuck for 61s! [NetworkManager: 3483]
I use kubuntu since 6.10, in the past, on my machine, Suspend/Resume has worked only with Kubuntu 8.04, if I remember fine. If that information is important for you, I can try to test it with a liveCD.

Revision history for this message
AlbertH (alberthilbert) wrote :

I confirm that issue is related to NetworkManager. If I kill it before suspending, the resume process is successful. Anyway, restarting NetworkManager after "resume" freezes the system.

Revision history for this message
AlbertH (alberthilbert) wrote :

After last upgrades, suspend/resume does work. The only remaining issue is the wireless driver (rtl8180) is not loaded on resume and I must launch it manually. However this is a huge improvement for me.
Thanks...

Revision history for this message
Przemek K. (azrael) wrote :

Does this issue still appear in Ubuntu 9.10 or 10.04?

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

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, 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.]

tags: added: kj-expired
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.

Other bug subscribers

Remote bug watches

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