1002:5975 [Acer Aspire 5100] suspend/resume failure

Bug #894308 reported by Chris
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

- Suspending is successful. Resuming results in random flashing artifacts on screen.
GUI is working ok if you manage to see through the artifacts but it is very hard so I just restart.

- Happens every time. Tried nomodeset in kernel line of grub but no go.

- Running Ubuntu 11.10 64-bit updated.
- Don't know which package is responsible, sorry...

$ cat /proc/version_signature
Ubuntu 3.0.0-12.20-generic 3.0.4

$ sudo lspci -vnvn > lspci-vnvn.log
(see attachment)
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: despina 1526 F.... pulseaudio
                      despina 2355 F.... TeamViewer.exe
 /dev/snd/pcmC0D0p: despina 1526 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xb0000000 irq 16'
   Mixer name : 'Realtek ALC883'
   Components : 'HDA:10ec0883,1025009f,00100002 HDA:14f12bfa,1025009f,00090000'
   Controls : 23
   Simple ctrls : 13
DistroRelease: Ubuntu 11.10
HibernationDevice: RESUME=UUID=ecf7ad46-cd33-46d7-96f5-aa756f41f453
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 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 001 Device 002: ID 5986:0100 Acer, Inc Orbicam
 Bus 001 Device 004: ID 12d1:1035 Huawei Technologies Co., Ltd.
MachineType: Acer Aspire 5100
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=59c5075a-4da4-4334-ad5f-9baca27ec73f ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-12-generic N/A
 linux-backports-modules-3.0.0-12-generic N/A
 linux-firmware 1.60
Tags: oneiric running-unity
Uname: Linux 3.0.0-12-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 01/23/2007
dmi.bios.vendor: Acer
dmi.bios.version: V2.73
dmi.board.name: Navarro
dmi.board.vendor: Acer
dmi.board.version: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAcer:bvrV2.73:bd01/23/2007:svnAcer:pnAspire5100:pvrV2.73:rvnAcer:rnNavarro:rvrN/A:cvnAcer:ct10:cvrN/A:
dmi.product.name: Aspire 5100
dmi.product.version: V2.73
dmi.sys.vendor: Acer

Revision history for this message
Chris (cmavr8) wrote :
tags: added: 5100 acer aspire
tags: added: suspend
tags: added: resume
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 894308

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

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

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Chris (cmavr8) wrote : Re: [Acer Aspire 5100] suspend/resume failure

Running apport is very hard, if not undoable. GUI is almost unusable after resume, and network is down which makes remote running impossible.

Please let me know how I can provide more help.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Can you run the 'apport-collect 894308' command before triggering this issue with a suspend/resume? That will provide some details on your machine.

Also, would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please test the latest v3.2-rcN kernel (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the others). 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.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.2-rc1 fixed and issue, the tag would be: 'kernel-fixed-upstream-v3.2-rc1'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. If you believe this bug does not require upstream testing, please add the tag: 'kernel-upstream-testing-not-needed'.

Thanks in advance.

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: needs-upstream-testing
Revision history for this message
Chris (cmavr8) wrote : AcpiTables.txt

apport information

tags: added: apport-collected oneiric running-unity
description: updated
Revision history for this message
Chris (cmavr8) wrote : AlsaDevices.txt

apport information

Revision history for this message
Chris (cmavr8) wrote : AplayDevices.txt

apport information

Revision history for this message
Chris (cmavr8) wrote : ArecordDevices.txt

apport information

Revision history for this message
Chris (cmavr8) wrote : BootDmesg.txt

apport information

Revision history for this message
Chris (cmavr8) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
Chris (cmavr8) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
Chris (cmavr8) wrote : Card0.Codecs.codec.1.txt

apport information

Revision history for this message
Chris (cmavr8) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Chris (cmavr8) wrote : IwConfig.txt

apport information

Revision history for this message
Chris (cmavr8) wrote : Lspci.txt

apport information

Revision history for this message
Chris (cmavr8) wrote : PciMultimedia.txt

apport information

Revision history for this message
Chris (cmavr8) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Chris (cmavr8) wrote : ProcEnviron.txt

apport information

Revision history for this message
Chris (cmavr8) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Chris (cmavr8) wrote : ProcModules.txt

apport information

Revision history for this message
Chris (cmavr8) wrote : PulseSinks.txt

apport information

Revision history for this message
Chris (cmavr8) wrote : PulseSources.txt

apport information

Revision history for this message
Chris (cmavr8) wrote : RfKill.txt

apport information

Revision history for this message
Chris (cmavr8) wrote : UdevDb.txt

apport information

Revision history for this message
Chris (cmavr8) wrote : UdevLog.txt

apport information

Revision history for this message
Chris (cmavr8) wrote : WifiSyslog.txt

apport information

Revision history for this message
Chris (cmavr8) wrote : Re: [Acer Aspire 5100] suspend/resume failure

I run apport, but without su rights.

I will be unable to run it with su rights, or test another kernel until this or next weekend... sorry.

penalvch (penalvch)
summary: - [Acer Aspire 5100] suspend/resume failure
+ 1002:5975[Acer Aspire 5100] suspend/resume failure
summary: - 1002:5975[Acer Aspire 5100] suspend/resume failure
+ 1002:5975 [Acer Aspire 5100] suspend/resume failure
tags: removed: 5100 acer aspire
Revision history for this message
penalvch (penalvch) wrote :

cmavr8, 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 provide the information following https://wiki.ubuntu.com/DebuggingKernelSuspend ? As well, could you please test for this 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 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>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and 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.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thanks in advance.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Chris (cmavr8) wrote :

Christopher, I am sorry but I no longer have access to the laptop with the problem, so I cannot retest it at the moment.

If I happen to have it again I will update this bug.

Thanks

Revision history for this message
penalvch (penalvch) wrote :

cmavr8, this bug report is being closed due to your last comment Please submit any future bugs you may find. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/894308/comments/29 regarding you no longer having the hardware. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Aaron Sosnick (longlegged-guy) wrote :

I also have an Acer Aspire 5100. I just installed Ubuntu 14.04 and I have this exact problem. The machine boots fine, but after a suspend the screen tears/flickers so badly that the machine is unusable. Note that the problem does not occur with hibernate.

Changed in linux (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
Aaron Sosnick (longlegged-guy) wrote :

Also I have tried booting with nomodeset, but then the proper driver isn't run at all, the screen resolution is wrong, and there's no way to change it.

Revision history for this message
Aaron Sosnick (longlegged-guy) wrote :

The screen is fine after hibernate. In fact if I leave a window open with $ sudo pm_hibernate ready to go, I can bring the screen back by hitting enter to hibernate after a suspend/resume. However the wifi disconnects after after hibernate/suspend. Will file/revive a second bug report for that.

Revision history for this message
penalvch (penalvch) wrote :

Aaron Sosnick, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Changed in linux (Ubuntu):
status: Confirmed → Invalid
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.