1002:6739 14.04 randomly reboots

[Michael Murphy]

I've noticed after installing Ubuntu 14.04 on my computer, that a DPM issue exists. DPM needs to be disabled by default like in kernel 3.14 so that the live CD or desktop session does not instantly reboot the machine.

WORKAROUND: Edit grub.cfg on the bootable flash drive and adding radeon.dpm=0 to the boot options, along with cd'ing to /target/etc/default and editing grub with the same change before rebooting after installation to bypass it.

---
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 2789 F.... pulseaudio
 /dev/snd/controlC1: ubuntu 2789 F.... pulseaudio
CasperVersion: 1.340
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: System manufacturer System Product Name
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz.efi root=UUID=E3B4-EDF6 debian-installer/language=en keyboard-configuration/layoutcode=us iso-scan/filename=/username-14.04-desktop-amd64.iso boot=casper file=/cdrom/preseed/username.seed noprompt quiet splash radeon.dpm=0 --
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-24-generic N/A
 linux-backports-modules-3.13.0-24-generic N/A
 linux-firmware 1.127
RfKill:

Tags: trusty
Uname: Linux 3.13.0-24-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 06/17/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2102
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4A79XTD EVO
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.:bvr2102:bd06/17/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A79XTDEVO:rvrRevX.0X:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Michael Murphy (mmstick)]

apport information

[Michael Murphy (mmstick)]

apport information

[Michael Murphy (mmstick)]

apport information

[Michael Murphy (mmstick)]

apport information

[Michael Murphy (mmstick)]

apport information

[Michael Murphy (mmstick)]

apport information

[Michael Murphy (mmstick)]

apport information

[Michael Murphy (mmstick)]

apport information

[Michael Murphy (mmstick)]

apport information

[Michael Murphy (mmstick)]

apport information

[Michael Murphy (mmstick)]

apport information

[Michael Murphy (mmstick)]

apport information

[Michael Murphy (mmstick)]

apport information

[Michael Murphy (mmstick)]

I have two systems with Radeon HD 6850 graphics card, and one off-site with a Richland APU. All have been affected since the early RCs of kernel 3.13 in December and still affected today. The only systems not affected are my RadeonSI-based Kabini APU laptop and my RadeonSI-based Radeon HD 7950.

[penalvch (penalvch)]

Michael Murphy, regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1297464/comments/15 :
>"I have two systems with Radeon HD 6850 graphics card, and one off-site with a Richland APU. All have been affected since the early RCs of kernel 3.13 in December and still affected today."

This report will only focus on the hardware noted in the Bug Description. If you have other hardware having issues, please file one bug report per machine via a terminal:
ubuntu-bug linux

Despite this, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-3.15-rc2

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Michael Murphy (mmstick)]

I always test the latest kernel as soon as they released with a script that pulls the latest Ubuntu mainline kernel. As I originally stated in the description, only kernel 3.13 is affected. Kernels 3.14-rc1 through 3.15-rc2 are not affected since they have disabled DPM for Northern Islands graphics chips due to outstanding bugs like what this bug report is all about. I already reported this bug upstream in December.

[Michael Murphy (mmstick)]

The bug is also already well confirmed, as the other bug report active here is the exact same bug.

[Michael Murphy (mmstick)]

Also, it doesn't have problems booting. Booting is not the problem. The problem is DPM does a power cycle randomly after it has booted.

[Michael Murphy (mmstick)]

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309578 This is the exact same bug report (I even have the exact same hardware offsite in my Richland machine, which is affected by the bug worse) It may be different hardware than what I uploaded with apport, but it's the same architecture (Northern Islands) and therefore has the same Radeon DPM issues.

[Michael Murphy (mmstick)]

No need to run any bisecting. You can see where the change was with cgit ( https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=919cf555c04e16dafb1fba56904eb23889a812c3 ). Technically, it's not fixed upstream. They just applied the aforementioned workaround of disabling DPM for Northern Islands until they figure out how to fix it. Another bug report on bugzilla related to the bug can be found here: https://bugzilla.kernel.org/show_bug.cgi?id=68571 which shows how even with kernel 3.14, manually enabling DPM, since it is disabled by default now, with radeon.dpm=1 still causes the problems. In kernel 3.12 and prior, DPM was disabled by default since it was buggy, but for some reason it was enabled by default with 3.13, leading to these problems.

[Michael Murphy (mmstick)]

This bug is fixed in kernel 3.16: https://bugs.freedesktop.org/show_bug.cgi?id=72921

[Andy Whitcroft (apw)]

@Michael -- the fix you propose for the issue was applied to 14.04 in the upstream stable update v3.13.3, the commit below:

  commit 318729d307dc565a1c44bb02a8710b5a4f0b4037
  Author: Alex Deucher <email address hidden>
  Date: Sat Jan 11 10:55:55 2014 -0500

    drm/radeon: disable dpm on BTC

    commit 919cf555c04e16dafb1fba56904eb23889a812c3 upstream.

That commit (and v3.13.3 in general) are contained in the Ubuntu 3.13.0-10.30 upload, which would imply that fix was in the kernel in the -release pocket, in Ubuntu 3.13.0-24.46, and it cirtainly seems to be correctly applied there.

That said it does appear some other fixes have been applied in this area which may well have reenabled it for some of these cards. It appears some further investigation is needed, to determine why the fixes for this have not worked and to feed this back to stable.

[Michael Murphy (mmstick)]

DPM doesn't need to be disabled in Linux 3.16 because the issue was fixed by enabling BAPM.