Bug 77835

Summary:

X crash when using xrandr with R9 290X and 7870 for triple head

Product:

DRI

Reporter:

Maik Broemme <mbroemme>

Component:

DRM/Radeon

Assignee:

Default DRI bug account <dri-devel>

Status:

RESOLVED WONTFIX

QA Contact:

Severity:

critical

Priority:

medium

Version:

unspecified

Hardware:

x86-64 (AMD64)

OS:

Linux (All)

Whiteboard:

i915 platform:

i915 features:

Attachments:

Description	Flags
Xorg log of crash	none
boot log with drm:radeon_atom_get_leakage_vddc_based_on_leakage_params error	none

Description Maik Broemme 2014-04-23 20:32:30 UTC

Created attachment 97831 [details]
Xorg log of crash

I'm trying to get a system with a R9 290X and a HD 7870 GHz Edition working. If I use the cards independently everything works fine under X (the 7870 works with glamor acceleration and the R9 290X without acceleration) but the problem is to get them working together with single X. Attached is my Xorg.0.log and the dmesg output. I'm using the following cards:

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii XT [Radeon HD 8970]
04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn XT [Radeon HD 7870 GHz Edition]

Steps to reproduce this issue:

#1 startx
#2 xrandr --output DVI-0 --primary
#3 xrandr --output HDMI-1 --right-of DVI-0
#4 xrandr --setprovideroutputsource 1 0
#5 xrandr --output HDMI-1-0 --mode 1920x1080 --right-of HDMI-1

Right now X is crashed with the following:

(EE) 
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x48) [0x584b08]
(EE) 1: /usr/bin/X (0x400000+0x1887f9) [0x5887f9]
(EE) 2: /usr/lib/libpthread.so.0 (0x7f2a182c8000+0xf880) [0x7f2a182d7880]
(EE) 
(EE) Segmentation fault at address 0x0
(EE) 
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE) 
(EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE) 
(II) AIGLX: Suspending AIGLX clients for VT switch
(EE) Server terminated with error (1). Closing log file.
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
      after 4790 requests (4790 known processed) with 9 events remaining.
xinit: connection to X server lost

The system is running Arch Linux with the following configuration:

ati-dri 10.1.1
glamor-egl 0.6.0
libdrm 2.4.53
linux 3.14.1
linux-firmware 20140316.dec41bc
mesa 10.1.1
mesa-libgl 10.1.1
xf86-video-ati 7.3.0
xorg-server 1.15.1

Does anybody has a hint what I could try next? Also what is needed to get acceleration working. I tried it with "NoAccel" "False" and "AccelMethod" "glamor" but it just freezes my X on startup. :)

--Maik

Comment 1 Maik Broemme 2014-04-23 20:33:40 UTC

Created attachment 97832 [details]
boot log with drm:radeon_atom_get_leakage_vddc_based_on_leakage_params error

Comment 2 Alex Deucher 2014-04-23 20:41:06 UTC

Acceleration is not currently stable on Hawaii cards (R9 290) so it is disabled by default.

Comment 3 Maik Broemme 2014-04-23 20:51:00 UTC

This was my experience too but even without acceleration of the R9 290X the X server crashes when using both cards.

Comment 4 Maik Broemme 2014-04-23 21:05:17 UTC

Alex, I've tried 3.15-rc2 and your new ucode files from http://people.freedesktop.org/~agd5f/radeon_ucode/ for both cards now, but still no luck with xrandr and both cards. Firmware is correctly loaded. Same crash.

[   21.174824] [drm] initializing kernel modesetting (HAWAII 0x1002:0x67B0 0x174B:0xE285).
[   21.436057] [drm] Loading HAWAII Microcode
[   21.442757] [drm] radeon/HAWAII_mc2.bin: 32364 bytes
[   21.698816] [drm] initializing kernel modesetting (PITCAIRN 0x1002:0x6818 0x1682:0x3251).
[   21.699439] [drm] Loading PITCAIRN Microcode
[   21.701027] [drm] radeon/PITCAIRN_mc2.bin: 31100 bytes

Comment 5 Michel Dänzer 2015-10-19 06:01:05 UTC

Does this still happen with current versions of xf86-video-ati and xserver? If so, can you get a gdb backtrace of the crash? See http://wiki.x.org/wiki/Development/Documentation/ServerDebugging/ .

Comment 6 Greg Turner 2016-01-15 08:28:06 UTC

This looks like bug 79531.  Mr. Broemme, if, by any chance, you are still able to repro this problem, check out the patches in that bug, and let us know if they fix the problem for you.

And, no need to repeat yourself Michel, I know I still owe the mailing list a respin of that patch -- I didn't give up, just procrastinated.

Comment 7 Maik Broemme 2016-01-15 12:58:36 UTC

I can't reproduce it anymore as I don't have the cards anymore.

Comment 8 Michel Dänzer 2016-01-18 07:05:32 UTC

Resolving per comment 7.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.