https://bugs.freedesktop.org/show_bug.cgi?id=93288

Bug ID: 93288 Summary: dpm malfunction on radeon hawaii r9 390X Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel@lists.freedesktop.org Reporter: dev@illwieckz.net QA Contact: dri-devel@lists.freedesktop.org

Hi, I encounter many problems with radeonsi and dpm (I never got it working, even with previous radeon cards I owned).

While running linux 4.2 two months ago I got a a graphical hang with a "[drm:radeon_pm_resume [radeon]] *ERROR* radeon: dpm resume failed" message.

To get this bug I just had to boot my system and wait less than 10min before it hangs. The system was still usable by ssh, but the "reboot" never complete.

I was running 4.2 kernel on Ubuntu Wily with mesa git (I'm using some nightly build packages). I have a radeon R9 390X (Hawaii), lspci says that:

01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii XT [Radeon R9 290X] [1002:67b0] (rev 80) (prog-if 00 [VGA controller])

dmesg says that: [drm:radeon_pm_resume [radeon]] *ERROR* radeon: dpm resume failed

I 'll join a detailed lspci entry, a complete dmesg log and a screen photo.

The only way to run the radeon R9 390X is to run radeon.dpm=0 and it was needed too for a radeon HD 7970 I had in the past.

Right now, I tried to reboot with radeon.dpm=1 and I got a graphical hang then some weird stuff printed on screen. I rebooted my computer to not burn my CPU (see https://bugs.freedesktop.org/show_bug.cgi?id=93101 ), so currently the only information I have is the ones was syslogged.

It printed things like that:

Dec 8 01:32:07 gollum kernel: [ 82.262780] radeon 0000:01:00.0: ring 3 stalled for more than 10368msec Dec 8 01:32:07 gollum kernel: [ 82.262790] radeon 0000:01:00.0: GPU lockup (current fence id 0x000000000000155c last fence id 0x0000000000001655 on ring 3) Dec 8 01:32:08 gollum kernel: [ 82.366721] radeon 0000:01:00.0: ring 4 stalled for more than 10472msec Dec 8 01:32:08 gollum kernel: [ 82.366729] radeon 0000:01:00.0: ring 0 stalled for more than 10472msec Dec 8 01:32:08 gollum kernel: [ 82.366737] radeon 0000:01:00.0: GPU lockup (current fence id 0x000000000000089a last fence id 0x000000000000089b on ring 4) Dec 8 01:32:08 gollum kernel: [ 82.366744] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000000ce4 last fence id 0x0000000000000d0e on ring 0) Dec 8 01:32:27 gollum kernel: [ 101.898853] radeon 0000:01:00.0: Saved 3901 dwords of commands on ring 0. Dec 8 01:32:27 gollum kernel: [ 101.898870] radeon 0000:01:00.0: GPU softreset: 0x00000009

Right now I'm running:

- Ubuntu Wily 15.10 + Oibaf PPA - Linux 4.3 - libdrm-radeon1 2.4.65+git1512011830.42f2f9~gd~w - xserver-xorg-video-radeon 7.6.99+git1512040732.78fbca~gd~w - xserver-xorg 7.7+7ubuntu4 - libgl1-mesa-dri 11.2~git1512061930.d108b6~gd~w

And dmesg | grep radeon says:

[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.3.0-040300-generic root=/dev/mapper/gollum--vg-gollum--disk ro quiet splash nomdmonddf nomdmonisw libata.atapi_passthru16=0 radeon.dpm=0 vt.handoff=7 [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.3.0-040300-generic root=/dev/mapper/gollum--vg-gollum--disk ro quiet splash nomdmonddf nomdmonisw libata.atapi_passthru16=0 radeon.dpm=0 vt.handoff=7 [ 1.958053] [drm] radeon kernel modesetting enabled. [ 1.962224] fb: switching to radeondrmfb from VESA VGA [ 1.962529] radeon 0000:01:00.0: Invalid ROM contents [ 1.962629] radeon 0000:01:00.0: VRAM: 8192M 0x0000000000000000 - 0x00000001FFFFFFFF (8192M used) [ 1.962631] radeon 0000:01:00.0: GTT: 2048M 0x0000000200000000 - 0x000000027FFFFFFF [ 1.962710] [drm] radeon: 8192M of VRAM memory ready [ 1.962711] [drm] radeon: 2048M of GTT memory ready. [ 1.962888] [drm] radeon: power management initialized [ 1.968997] radeon 0000:01:00.0: WB enabled [ 1.969003] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000200000c00 and cpu addr 0xffff8808126b5c00 [ 1.969005] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000200000c04 and cpu addr 0xffff8808126b5c04 [ 1.969007] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000200000c08 and cpu addr 0xffff8808126b5c08 [ 1.969009] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000200000c0c and cpu addr 0xffff8808126b5c0c [ 1.969011] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000200000c10 and cpu addr 0xffff8808126b5c10 [ 1.969410] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000076c98 and cpu addr 0xffffc90004036c98 [ 1.969558] radeon 0000:01:00.0: fence driver on ring 6 use gpu addr 0x0000000200000c18 and cpu addr 0xffff8808126b5c18 [ 1.969560] radeon 0000:01:00.0: fence driver on ring 7 use gpu addr 0x0000000200000c1c and cpu addr 0xffff8808126b5c1c [ 1.969631] radeon 0000:01:00.0: radeon: using MSI. [ 1.969660] [drm] radeon: irq initialized. [ 3.762178] fbcon: radeondrmfb (fb0) is primary device [ 3.780407] radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device [ 3.791974] [drm] Initialized radeon 2.43.0 20080528 for 0000:01:00.0 on minor 0