AMD radeon hangs/crashes

[Petter Adsen]

Ubuntu 3.19.0-15.15-generic 3.19.3

On boot, there are error messages from the radeon driver (see dmesg output), and lightdm fails to start the X server - it simply hangs without errors. Logging in on the console and running startx works, but if the screen saver kicks in, the X server hangs again and needs to be manually killed and restarted.

This started happening after one of the two latest kernel upgrades on vivid, I didn't reboot after the -14 update, so I don't know whether that or -15 caused this.

Please contact me If further information is needed, I can't attach more than one file.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-generic 3.19.0.15.14
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: petter 18079 F.... pulseaudio
 /dev/snd/controlC1: petter 18079 F.... pulseaudio
CurrentDesktop: XFCE
Date: Thu Apr 23 12:26:01 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-03-08 (45 days ago)
InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: System manufacturer System Product Name
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=f99b1ed0-5a42-4536-9899-d3e982f1c048 ro
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-15-generic N/A
 linux-backports-modules-3.19.0-15-generic N/A
 linux-firmware 1.143
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to vivid on 2015-03-21 (32 days ago)
dmi.bios.date: 04/01/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2002
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: Crosshair IV Extreme
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.:bvr2002:bd04/01/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnCrosshairIVExtreme:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Petter Adsen (ducasse)]

lspci output

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Petter Adsen, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to 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 by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-3.XY-rcZ

Where XY and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-3.XY-rcZ

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.

[penalvch (penalvch)]

Petter Adsen, the next step is to fully reverse commit bisect from kernel 3.19 to 4.0 in order to identify the last bad commit, followed immediately by the first good one. Once this commit has been identified, then it may be reviewed as a candidate for backporting into your release. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Petter Adsen (ducasse)]

Look, guys - no offense intended, but I'm just not going to invest that amount of time in tracking down which commit causes/fixes a bug when I can just run an unofficial kernel.

If anyone else gets bitten by this and have to run an official Ubuntu-supplied kernel then I might consider doing it, but since it seems only I am affected I won't bother. I suggest you close this.

Petter

[Launchpad Janitor (janitor)]

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