[Asus M5A97] hibernate/resume failure [non-free: fglrx]

Bug #1065437 reported by karl anliot
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

chose hibernate from the menu, with the purpose of quickly testing hibernate. when booting, the system noted how it correctly loaded the hibernation file, but nothing else happened for 3 minutes, at which point i failed the test.

ProblemType: KernelOops
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-17-generic 3.5.0-17.28
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
NonfreeKernelModules: fglrx
Annotation: This occured during a previous hibernate and prevented it from resuming properly.
ApportVersion: 2.6.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: anliot 1696 F.... lxpanel
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Date: Thu Oct 11 05:30:45 2012
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: hibernate/resume
HibernationDevice: RESUME=UUID=0d467182-6086-42a8-a978-a6d0fc664704
InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.1)
InterpreterPath: /usr/bin/python3.2mu
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: To be filled by O.E.M. To be filled by O.E.M.
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=8f3b3f46-97a9-45f2-8566-368a6785e727 ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-17-generic N/A
 linux-backports-modules-3.5.0-17-generic N/A
 linux-firmware 1.94
RfKill:

SourcePackage: linux
Title: [To be filled by O.E.M. To be filled by O.E.M.] hibernate/resume failure [non-free: fglrx]
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 11/24/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0901
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A97
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0901:bd11/24/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.

Revision history for this message
karl anliot (kanliot) wrote :
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.6 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. Please only remove that one tag and leave the other tags. 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, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6-quantal/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
tags: added: needs-upstream-testing
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
nfsd (in4mer+launchpad)
Changed in linux (Ubuntu):
status: Expired → Confirmed
Revision history for this message
nfsd (in4mer+launchpad) wrote :

I reopened this bug without getting too far into exactly what was wrong; I've opened a new bug in an effort to cover the spread; the difference hinges on hibernate reporting failure because it can't find iw (this bug), and hibernate reporting failure because iw returns nonzero 100% of the time (other bug).

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1094867

Revision history for this message
penalvch (penalvch) wrote :

karl anliot, as per http://www.asus.com/Motherboards/M5A97/#support_Download_8 an update is available for your BIOS (1605). If you update to this, does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Thank you for your understanding.

tags: added: bios-outdated-1605 regression-potential
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
summary: - hibernate/resume failure [non-free: fglrx]
+ [Asus M5A97] hibernate/resume failure [non-free: fglrx]
Revision history for this message
Greg (cebif) wrote :

I have a similar maniboard: M5A97 R2.0 and have the same bug occuring randomly, not every time I resume from hibernate. Would it be relevant for me to supply information about BIOS and/or test upstream kernel?

Revision history for this message
Greg (cebif) wrote :

I am also using kernel 3.8.0-29-generic with Ubuntu 13.04. So my kernel is already advanced from the linux-image-3.5.0-17-generic 3.5.0-17.28 reported.

Revision history for this message
penalvch (penalvch) wrote :

Greg, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository 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.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documention in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

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.