[Bug 81476] three monitors on two radeon cards works with some layouts not others

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Jul 18 10:11:51 PDT 2014


Ian! D. Allen <idallen at idallen.ca> changed:

           What    |Removed                     |Added
             Status|RESOLVED                    |REOPENED
         Resolution|NOTOURBUG                   |---

--- Comment #4 from Ian! D. Allen <idallen at idallen.ca> ---
(In reply to comment #3)
> They way the core provider stuff in the xserver works the rendering
> is done on one GPU and the respective updated regions are sent to the
> other displays.

If the above limits are true, why do I get a working 4800x1200 desktop when I
invert two of the three screens?  Why can it show my 4800x1200 desktop if two
screens are upside-down but not if they are right-side-up?  How is this
possible if 4800x1200 can't be done? [*]

> If you disable the OpenGL compositor, your desktop should work fine.

I don't know enough about the graphics chain to know how to "disable the OpenGL
compositor".  All I do is start Xorg, a window manager, and some clients. 
There is nothing mentioned about "composit" actually being used anywhere in the
Xorg.0.log.  The net searches I do all find stuff that's years old.  Please
point me at some current documentation on how to disable this?

> The OpenGL compositing manager you are running should check for the max
> limits of the GL driver before using it for surfaces which may exceed that. 

Yes, it should check instead of quietly screwing up.  Can it not query the GPU
for the max limit?  (The max limit you say of 4096 is not obvious in the
Xorg.0.log output anywhere.  Why does xrandr tell me "maximum 8192 x 8192"?) 
To whom should I submit this "failure to check limit" bug report?

[*] The working 4800x1200 desktop with two screens inverted is unstable, since
if I CTRL-ALT-F1 to a console, it dies with:
reporting 4 6 22 172
reporting 4 6 22 172
reporting 4 6 22 172
reporting 4 6 22 172
reporting 4 6 22 172
reporting 4 6 22 172
reporting 4 6 22 172
(II) AIGLX: Suspending AIGLX clients for VT switch
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x55) [0x7f6e13e71b05]
(EE) 1: /usr/bin/X (0x7f6e13cba000+0x1bb9c9) [0x7f6e13e759c9]
(EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f6e12fe0000+0xfcb0)
(EE) 3: /usr/bin/X (CreatePicture+0x3e) [0x7f6e13de897e]
(EE) 4: /usr/bin/X (0x7f6e13cba000+0xdc15e) [0x7f6e13d9615e]
(EE) 5: /usr/bin/X (0x7f6e13cba000+0x1a8758) [0x7f6e13e62758]
(EE) 6: /usr/bin/X (0x7f6e13cba000+0xea898) [0x7f6e13da4898]
(EE) 7: /usr/bin/X (BlockHandler+0x44) [0x7f6e13d144f4]
(EE) 8: /usr/bin/X (WaitForSomething+0x11d) [0x7f6e13e6ee4d]
(EE) 9: /usr/bin/X (0x7f6e13cba000+0x55954) [0x7f6e13d0f954]
(EE) 10: /usr/bin/X (0x7f6e13cba000+0x59b8a) [0x7f6e13d13b8a]
(EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xed)
(EE) 12: /usr/bin/X (0x7f6e13cba000+0x44101) [0x7f6e13cfe101]
(EE) Segmentation fault at address 0x10
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
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
(EE) Server terminated with error (1). Closing log file.
xinit: connection to X server lost

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.x.org/archives/xorg-driver-ati/attachments/20140718/5d984f35/attachment.html>

More information about the xorg-driver-ati mailing list