[radeon] suspend fails in 14.04 with Juniper and Caicos on an Asus P6T SE

Bug #1338275 reported by skomorokh
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Maarten Lankhorst

Bug Description

Suspend to RAM fails for me with the radeon driver and two cards on an Asus P6T SE motherboard: Juniper and Caicos. Even at console in single user mode (to eliminate Xorg) and with "echo devices > /sys/power/pm_test" and "echo freeze > /sys/power/state" to narrow it down to unloading modules (it works with "freezer" sent to pm_test).

Unloading the radeon module (needed to blacklist with a kernel parameter first) lets everything work.

Tried the stock Ubuntu Trusty 3.13.0 kernel and also tried using 3.14.10 and 3.15.3 from the PPA. All fail, but 3.15 has the screen go white after a bit so that's new.

Tried installing various new X stuff that probably is totally unrelated via ppa:oaibaf/graphics-drivers

Tried disabling dpm with the radeon.dpm=0 parameter.

Tried disabling synchronous suspend with "echo 0 > /sys/power/async".

Not sure what else to try?
---
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-id', '/dev/snd/controlC4', '/dev/snd/pcmC4D0c', '/dev/snd/by-path', '/dev/snd/controlC3', '/dev/snd/hwC3D0', '/dev/snd/pcmC3D3p', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/controlC2', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D3p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: KDE
DistroRelease: Ubuntu 14.04
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: System manufacturer System Product Name
Package: linux (not installed)
ProcFB:
 0 radeondrmfb
 1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic-tuxonice root=/dev/mapper/grp1-root ro resume=swap:/dev/dm-1:0x21ec000 radeon.audio=0 radeon.dpm=1 radeon.modeset=1 pcie_aspm=force acpi_enforce_resources=lax intremap=off
ProcVersionSignature: Ubuntu 3.13.0-30.54~ppa1-generic-tuxonice 3.13.11.2
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-30-generic-tuxonice N/A
 linux-backports-modules-3.13.0-30-generic-tuxonice N/A
 linux-firmware 1.131~gd~t
RfKill:

Tags: trusty
Uname: Linux 3.13.0-30-generic-tuxonice x86_64
UpgradeStatus: Upgraded to trusty on 2014-04-21 (76 days ago)
UserGroups: adm admin cdrom davfs2 dialout fuse lpadmin plugdev pulse pulse-access sambashare ssh video
_MarkForUpload: True
dmi.bios.date: 09/21/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0908
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P6T SE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0908:bd09/21/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TSE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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 1338275

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
tags: added: trusty
Revision history for this message
skomorokh (skomorokh) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
skomorokh (skomorokh) wrote : BootDmesg.txt

apport information

Revision history for this message
skomorokh (skomorokh) wrote : CRDA.txt

apport information

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

apport information

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

apport information

Revision history for this message
skomorokh (skomorokh) wrote : Lsusb.txt

apport information

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

apport information

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

apport information

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

apport information

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

apport information

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

apport information

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

apport information

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

apport information

skomorokh (skomorokh)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Maarten Lankhorst (mlankhorst) wrote :

I'm still lacking the dmesg of when things go wrong, could you attach that?

Changed in linux (Ubuntu):
assignee: nobody → Maarten Lankhorst (mlankhorst)
status: Confirmed → Incomplete
Revision history for this message
skomorokh (skomorokh) wrote :

The /var/log/dmesg.log.1 file doesn't seem to be updated in single user mode, but it doesn't get any extra output from the suspend when it is.

Or are you looking for the output of dmesg at boot from each of the various test runs I did? I gave it a quick go on 3.13.0-30-generic in single user and dumped the output of dmesg to a file for you first.

(NB: Not sure if my NFS shows up there but the very first thing I did for the above tests was temporarily purge the nfs-kernel-server and make sure the modules weren't loaded (checking lsmod | grep nfs) since I actually suspected it first before radeon. However I've since restored that and it'll be in this log.)

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

Turns out the problem was a line in rc.local where I was forcing the GPU into low power mode:

echo low > /sys/class/drm/card1/device/power_dpm_force_performance_level

Took out the kernel parameters and ran in single user but didn't catch that. Leaving radeon dpm on auto or setting it to high won't affect suspend but forcing it to low causes this freeze.

Closing the bug here because I assume it's a radeon driver issue and not at all Ubuntu specific.

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.