[System manufacturer System Product Name] suspend/resume failure [non-free: fglrx]

Bug #1289418 reported by Jeremiah Corbin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Activated Suspend and it never completed.

ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-16-generic 3.13.0-16.36
ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
Uname: Linux 3.13.0-16-generic x86_64
NonfreeKernelModules: fglrx
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: jdc 3139 F.... pulseaudio
 /dev/snd/controlC0: jdc 3139 F.... pulseaudio
Date: Fri Mar 7 08:31:15 2014
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=7f40e0c3-bcf7-42be-8d78-20672cdb52b2
InstallationDate: Installed on 2014-02-05 (29 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140204)
InterpreterPath: /usr/bin/python3.4
MachineType: System manufacturer System Product Name
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-16-generic.efi.signed root=UUID=70a96916-ca8b-4158-b114-ad2c46e9e380 ro quiet splash nomdmonddf nomdmonisw vt.handoff=7
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.13.0-16-generic N/A
 linux-backports-modules-3.13.0-16-generic N/A
 linux-firmware 1.126
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Title: [System manufacturer System Product Name] suspend/resume failure [non-free: fglrx]
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 05/08/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 6104
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: F2A85-V PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6104:bd05/08/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF2A85-VPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Jeremiah Corbin (corbin-jeremiah) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

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.14 kernel[0].

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.14-rc6-trusty/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
tags: added: kernel-unable-to-test-upstream
Revision history for this message
Jeremiah Corbin (corbin-jeremiah) wrote :

kernel-unable-to-test-upstream

Attempted to install the 3.14.0-rc6 and fglrx messages appeared. (fglrx make.log attached)
ran sudo update-grub and the 3.14.0 kernel is found, but not added to list of kernels at boot. I cannot test.

...
run-parts: executing /etc/kernel/postinst.d/dkms 3.14.0-031400rc6-generic /boot/vmlinuz-3.14.0-031400rc6-generic
Error! Bad return status for module build on kernel: 3.14.0-031400rc6-generic (x86_64)
Consult /var/lib/dkms/fglrx/13.350/build/make.log for more information.
...

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.