Bug 97931 - GPU lockup with Radeon HD 4670
Summary: GPU lockup with Radeon HD 4670
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: drivers_video-dri
Depends on:
Reported: 2015-05-08 15:55 UTC by joe.r.floss.user
Modified: 2016-03-23 18:54 UTC (History)
2 users (show)

See Also:
Kernel Version: 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt9-3 (2015-04-23) x86_64 GNU/Linux
Tree: Mainline
Regression: No

xserver-xorg package info (1.73 KB, application/octet-stream)
2015-05-08 15:55 UTC, joe.r.floss.user
Kernel log for GPU lockup (85.57 KB, text/plain)
2015-05-08 15:58 UTC, joe.r.floss.user
dmesg output (101.64 KB, text/plain)
2015-05-09 09:50 UTC, joe.r.floss.user
Xorg.log (47.47 KB, text/plain)
2015-05-09 09:51 UTC, joe.r.floss.user
Info related to the xserver-xorg package (83.61 KB, text/plain)
2015-05-09 09:53 UTC, joe.r.floss.user

Description joe.r.floss.user 2015-05-08 15:55:05 UTC
Created attachment 176201 [details]
xserver-xorg package info


I have a bug that regularly happens when running FlightGear (which uses OpenGL a lot). The kernel messages are very similar to those from bug 68571 ("GPU lockup on AMD Radeon HD6850 with DPM=1"). The symptoms are: screen goes blank for a few seconds, reappears, goes blank again, reappears garbled, alternates between blank and garbled a few times, and if I don't reboot quickly enough, I seem to recall (not sure about this one) that the whole system may crash in a way that requires a hard reset. My kernel command line is:

BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=... ro init=/bin/systemd ipv6.disable=1

This bug is present on Debian unstable, I had it yesterday; it is also present in the just-released jessie. I am attaching the kernel log from yesterday's occurrence of the bug. My graphics adapter is:

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV730 XT [Radeon HD 4670] (prog-if 00 [VGA controller])
        Subsystem: PC Partner Limited / Sapphire Technology Device e100
        Flags: bus master, fast devsel, latency 0, IRQ 50
        Memory at e0000000 (64-bit, prefetchable) [size=256M]
        Memory at fb9e0000 (64-bit, non-prefetchable) [size=64K]
        I/O ports at be00 [size=256]
        [virtual] Expansion ROM at fb900000 [disabled] [size=128K]
        Capabilities: [50] Power Management version 3
        Capabilities: [58] Express Legacy Endpoint, MSI 00
        Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
        Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
        Kernel driver in use: radeon

If there is something I can test to help solve this bug, please say so. I wonder if there are graphics adapters with decent OpenGL support using free drivers that don't suffer from this kind of bug...

Comment 1 Alex Deucher 2015-05-08 15:57:03 UTC
Please attach your xorg log and dmesg output.
Comment 2 joe.r.floss.user 2015-05-08 15:58:51 UTC
Created attachment 176211 [details]
Kernel log for GPU lockup

Kernel log obtained with [AMD/ATI] RV730 XT [Radeon HD 4670] (driver: radeon)
Comment 3 joe.r.floss.user 2015-05-08 16:05:15 UTC
dmesg output is now attached. As for the Xorg log, I don't have one corresponding to the lockup, unfortunately. I can attach a current one, or wait for the next lockup and make sure I keep the log this time. Sorry, and thanks for your help!
Comment 4 joe.r.floss.user 2015-05-09 09:50:23 UTC
Created attachment 176271 [details]
dmesg output
Comment 5 joe.r.floss.user 2015-05-09 09:51:50 UTC
Created attachment 176281 [details]
Comment 6 joe.r.floss.user 2015-05-09 09:53:07 UTC
Created attachment 176291 [details]
Info related to the xserver-xorg package
Comment 7 joe.r.floss.user 2015-05-09 09:59:01 UTC

I had the lockup again this morning. I attached 3 files corresponding to this lockup: dmesg output, Xorg.log and data gathered by reportbug for the xserver-xorg package (which includes versions of related packages).

I could work in a virtual console after the lockup once I stopped kdm, however restarting it was useless because it immediately started with garbled display.


Note You need to log in before you can comment on or make changes to this bug.