Ubuntu
linux package

[ASUSTeK COMPUTER INC. U38N] suspend/resume failure [non-free: fglrx wl]

Bug #1288319 reported by Joachim Johansson
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

New kernel, new fglrx, new unity. Same problem s always.

ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-15-generic 3.13.0-15.35
ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5
Uname: Linux 3.13.0-15-generic x86_64
NonfreeKernelModules: fglrx wl
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: lightdm 3044 F.... pulseaudio
                      joachim 3941 F.... pulseaudio
 /dev/snd/controlC0: lightdm 3044 F.... pulseaudio
                      joachim 3941 F.... pulseaudio
Date: Wed Mar 5 16:38:50 2014
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=d3fc5a91-cd91-4422-9556-94d092a20e69
InstallationDate: Installed on 2014-02-21 (12 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
InterpreterPath: /usr/bin/python3.4
MachineType: ASUSTeK COMPUTER INC. U38N
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-15-generic.efi.signed root=UUID=d2bc6ca7-191c-4302-aeb2-9cbc60ed7b03 ro nomodeset xforcevesa
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-15-generic N/A
 linux-backports-modules-3.13.0-15-generic N/A
 linux-firmware 1.125
SourcePackage: linux
StagingDrivers: rts5139
Title: [ASUSTeK COMPUTER INC. U38N] suspend/resume failure [non-free: fglrx wl]
UpgradeStatus: Upgraded to trusty on 2014-02-24 (9 days ago)
UserGroups:

dmi.bios.date: 05/29/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: U38N.209
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: U38N
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrU38N.209:bd05/29/2013:svnASUSTeKCOMPUTERINC.:pnU38N:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnU38N:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: U38N
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Revision history for this message
Joachim Johansson (joachim-j) 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-rc5-trusty/

Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Joachim Johansson (joachim-j) wrote :

I can't get fglrx to work with 3.14.0-rc5 at all.

Revision history for this message
Joachim Johansson (joachim-j) wrote :

kernel-unable-to-test-upstream

Joachim Johansson (joachim-j)
tags: added: kernel-unable-to-test-upstream
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Thanks for attempting to test the mainline kernel. Can you also see if this affects the latest 3.13 stable kernel:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.6-trusty/

Revision history for this message
Joachim Johansson (joachim-j) wrote :

After doing several reinstallations, and using several different kernels, it appears that the problem is caused by TLP.

http://linrunner.de/en/tlp/docs/tlp-linux-advanced-power-management.html
https://launchpad.net/~linrunner/+archive/ubuntu/tlp

I will do some further testings, but everything so far points in that direction.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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