[Acer Aspire 8930] suspend/resume failure [non-free: nvidia]

[FiReSTaRT]

Standard resume from suspend. It will suspend but when a resume is attempted, it won't wake up. Just a blank screen.

ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InterpreterPath: /usr/bin/python2.6
MachineType: Acer Aspire 8930
NonfreeKernelModules: nvidia
Package: linux-image-2.6.28-11-generic 2.6.28-11.41
ProcAttrCurrent: unconfined
ProcCmdLine: root=UUID=6dedc8ff-9847-47ac-9ac8-8d6f8a78cb25 ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-11.41-generic
SourcePackage: linux
Tags: resume suspend
Title: [Acer Aspire 8930] suspend/resume failure [non-free: nvidia]
UserGroups:

[FiReSTaRT (dlyh)]

Persists after a fresh install of Jaunty.

[Geert-Johan Riemer (geertjohan-wrong)]

I can confirm this bug.
I have a Acer Aspire 8930G Laptop and I am running Kubuntu 9.04 (linux-x86) using the nVidia driver, version 180.44.
When resuming from suspend to ram* I just get a blank screen, and I have to reset the laptop. However, suspend/resume isn't the only thing that gets me a black screen. When switching to a tty other then 7 (ctrl+alt+1 for instance) I get a black screen also. It is however possible to login at that tty and execute commands (without seeing what you type). So when my laptop gets suspended because of low power I can resume (black screen @ tty7), switch to tty1 (still black), login at tty1 and execute "sudo reboot", instead of resetting the laptop.

Just another case; when I'm in tty7 running KDE and everything is visible and I switch to tty1 (and thus getting black screen) and then switching back to tty7 (KDE) gets me a black screen. However the backlight of LCD is turned on, which isnt the case in the other black screens described here) and just a mouse pointer is visible and moveable on the screen.. when I wait for a while and clicking some buttons (F12 to slide down yakuake program running by default), and thus creating some work for the window manager I get to see everything the right way again, though KDE shows me a message: "Compositing Performance is Slow, The compositing performance was too slow and compositing has been suspended. Press alt+shift+F12 to resume compositing". At this time there are no nice visual effects anymore. pressing alt+shift+F12 gets me all the nice effects back (window shadows, alt+tab 3D, cube, wobbly windows, alpha channel/transparent KDE menu/notifiers, etc.)

I hope this information helps debugging the problem. If any logs/debugging output is required please tell me how. I'm using linux (Kubuntu) for 6 months now, but offcourse I don't know everything.

*It wont suspend to disk (freezes with black screen, but I guess thats another problem.

[Andres Mujica (andres.mujica)]

Hi Firestart

 Thanks for your report, as you reported this bug a while ago we need your help with this tests, so we can work on this issue.

1. Can you confirm this issue exists with the most recent Karmic Koala 9.10 Alpha release? ISO CD images are available at http://cdimage.ubuntu.com/releases/karmic/

2. If the issue remains with Karmic, it would be great to then also test the latest upstream mainline kernel available. This will allow additional upstream developers to examine it. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds

3. Finally, if you can take a look at https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume and provide answers to the questions mentioned under the "Information Gathering" section that would be great.

Thank you so much, and sorry for the late reply.

[Jeremy Foshee (jeremyfoshee)]

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.]

[FiReSTaRT (dlyh)]

I am sorry for not getting back, but I have been busy these days. Yes, the inability to resume still happens under the fully updated stable Karmic. Interestingly enough, moving away from HAL fixed the same issue on an HP-DV9894CA.

[Ján Révay (janci-revay)]

When I suspend (s2ram) my Acer 8930 laptop under both Ubuntu 10.4 and 12.4 same problem appears (and also on fedora). Laptop can hibernate (s2disk) well, but suspend (s2ram) is not working. After suspend it freezes on wakeup and when I press Ctrl+Alt+F1 this text is being periodically printed out:

[4480.58016] ata1: irq_stat 0x00000040, connection status changed
[4505.402689] ata1: SError {DevExch}

[4523.58053] ata1: irq_stat 0x00000040, connection status changed
[4521.415321] ata1: SError {DevExch}

[4535.58853] ata2: irq_stat 0x00000040, connection status changed
[4585.458621] ata2: SError {DevExch}
...

and so on, only the number in Square brackets [] changes.

I tried to install uswsusp and hibernate packages from synaptic but no change,,
I also tried most of options of s2ram with no success. Windows suspends ok.

[Ján Révay (janci-revay)]

Bug is present under both 32-bit and 64-bit version of ubuntu.

[Ján Révay (janci-revay)]

And it happens always. (I never successfully resumed this laptop under linux)

[Brad Figg (brad-figg)]

This change was made by a bot.

[Ján Révay (janci-revay)]

When I resume from suspend (standard boot parameters) I can see login screen and login,, but when I Login laptop freezes. When I boot with kernel parameter 1 and suspend (s2ram -force). I get black screen on wakeup.
When I type s2ram to the terminal this text is printed out.
Machine is unknown.
This machine can be identified by:
    sys_vendor = "Acer"
    sys_product = "Aspire 8930"
    sys_version = "V1.21"
    bios_version = "V1.21"

[penalvch (penalvch)]

FiReSTaRT, 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? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please 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 <replace-with-bug-number>

[Launchpad Janitor (janitor)]

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