Xorg crashes when using two monitors set up by aticonfig (BigDesktop mode) [AMD Feature#7647] [EPR#260264]

[Michael Glukhovsky]

Reported on: Ubuntu 8.04 (Hardy Heron)
Video card: ATI Mobility Radeon x1400 (128MB) on a Lenovo Thinkpad T60.
Monitors being used: Built-in T60 LCD with a resolution of 1400x1050, and a 24" Westinghouse LCD externally attached via analog (VGA) connector with a resolution of 1900x1200.

After many hours of effort, I finally managed to get my second monitor working using the fglrx driver and ATI's command-line utility aticonfig using BigDesktop mode. The total resolution of the desktop, as reported by xrandr, is 3840x1200. The orientation is horizontal,reverse so that my larger screen is to the left of the laptop. Compiz effects, etc. work perfectly. There are issues with 3D and video tearing, which may be related to the overlay being used (currently set to Xv). However, there is a massive showstopping bug.

If I click on the desktop on the right-hand monitor, it will very often crash Xorg entirely. I can fairly reliably replicate the bug by either simply clicking or drawing a selection area on the right-hand desktop. The left-hand desktop works perfectly; the icons for nautilus appear on the left-hand monitor. Gnome-panels are currently on the right-hand (laptop) monitor. Windows and compiz effects are drawn fine on both windows, with no problems. When using VLC, fullscreen video plays on the right-hand monitor.

Attached are my xorg.confs and the logfile post-crash, but here is the relevant error:

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x7e) [0x80c780e]
1: [0xb7fb9420]
2: /usr/lib/dri/fglrx_dri.so [0xb51b9903]
3: /usr/lib/dri/fglrx_dri.so [0xb51bba62]
4: /usr/lib/dri/fglrx_dri.so [0xb51cae6f]
5: /usr/lib/dri/fglrx_dri.so [0xb51cb03d]
6: /usr/lib/dri/fglrx_dri.so [0xb4d09f88]
7: /usr/lib/dri/fglrx_dri.so [0xb4f85145]
8: /usr/lib/xorg/modules/extensions//libglx.so [0xb7c226e5]
9: /usr/lib/xorg/modules/extensions//libglx.so [0xb7be799c]
10: /usr/lib/xorg/modules/extensions//libglx.so [0xb7be7077]
11: /usr/lib/xorg/modules/extensions//libglx.so [0xb7beb996]
12: /usr/bin/X [0x81506de]
13: /usr/bin/X(Dispatch+0x2cf) [0x808d8df]
14: /usr/bin/X(main+0x48b) [0x807471b]
15: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7d50450]
16: /usr/bin/X(FontFileCompleteXLFD+0x201) [0x8073a91]

Fatal server error:
Caught signal 8. Server aborting

(II) AIGLX: Suspending AIGLX clients for VT switch

[Michael Glukhovsky (mglukhovsky)]

Attached is my xorg.conf as generated by aticonfig (with the exception of 'Option "XAANoOffscreenPixmaps" "true"', which was a solution to slight corruption on the screen as reported in bug #17743).

[Michael Glukhovsky (mglukhovsky)]

Clarification: this bug appears to only occur when using Compiz as the window manager.

Using metacity --replace to switch from Compiz to Metacity stopped the crashes. Is there any way to get Compiz to work as smoothly?

[linkx (link-mustbuilddigital)]

I am experiencing the EXACT same bug. Here are my stats:

MacBookPro 17" 1680x1050
Acer Widescreen 1680x1050
BigDesktop configured using the fglrx GUI "ATI Catalyst Control Center"

X crashes when a click happens on the external monitor's desktop when compiz is enabled.

I was delighted to see that after installing fglrx and the control panel I did not need to mess with xorg.conf at ALL to get compiz and bigdesktop working. It works flawlessly, except for this bug.

I have not touched xorg.conf yet. Any suggested settings would be appreciated. Thanks!

[trollord (trollenlord)]

xorg-driver-fglrx

[patko (hrvoje-zlatar)]

I have the exact same problem. I use:

Compaq nw8440 with ATI FireGL v5200
Laptop's LCD 1920x1200
Dell 2407 1920x1200
Compiz

I had a lot of problems configuring BigDesktop, but now it works fine except the problem mentioned.

[icold (andrewcaveman)]

I have the same problem and it can be reproduced every time. Every time I double click on the backgound on the 2nd monitor it crashes X windows.

ASUS FS3 Laptop
ATI Mobility Radeon X1700
SAMSUNG 940Be
Compiz

Works fine as long as I don't use big desktop or compiz effects.

[Kyzyl (kyzylh)]

And another one joins the ranks...
Exact same problem:
ATI Mobility x1600
17" Mac Book Pro (integrated 1440x900 display)
Ubuntu 8.04.1 x64
fglrx 8.7 (the one that came out on july 21st)
BenQ FP202W 1680x1050

Everything works fine... until I click.

I really hope a patch comes out for this, because as mentioned it's s huge show stopper if you want to have a nice looking desktop :-/

[Michael Baudino (gornack)]

Hello,

I'm having quite the same bug : i configured my bigdesktop using the Catalyst Control Center, never touched aticonfig nor xorg.conf.
Everything is going well on the second desktop except that if i click (mousedown, not even doubleclick) on the desktop, X crashes.

Here's my config :
ATI Mobility Radeon X1600 (in HP Compaq nw8440)
Xorg 7.3
fglrx 8.51.3
Catalyst Control Center 1.10

Hope this helps

[linkx (link-mustbuilddigital)]

I still have this same issue, precisely as you described.

[ComBatXL (florian-eberle)]

I've the same problem, 2nd Screen a simply mousedown crashes the whole X-Server. I could not find a soultion untill now.

My configuration:
Ubuntu 8.04 w/ Compiz fusion

# lspci | grep VGA
01:00.0 VGA compatible controller: ATI Technologies Inc RV516 [Radeon X1300/X1550 Series]

# cat /proc/cpuinfo | grep model
model : 15
model name : Intel(R) Core(TM)2 Duo CPU E4400 @ 2.00GHz

[Michael Baudino (gornack)]

I'd just want to add that I can right-click on the second (extended) desktop, no problem happens, the menu is normally raised.
When the menu is raised, I can even left-click on the second desktop once (to make the menu disappear) without a problem.
Now that the menu has disappeared, I try to left-click on that bloody second desktop again (saying to myself "C'mon !")...... *crack*..... X crashes :/

Hope this might help.

[Blair Bethwaite (blair-bethwaite)]

Confirmed here also (X1600 Mobility). I have had this problem with Compiz and fglrx since starting to use them, can also confirm that it persists with the last few driver releases from AMD (Catalyst 8.7,8.8,8.9) and Compiz 0.7.6.

Happy to provide more info if somebody is actually going to look into this - why no response since April!?

[linkx (link-mustbuilddigital)]

Can anyone suggest where to post this bug so that it gets the attention of the appropriate people?

I have asked the Compiz-Fusion folk, since it is directly related to Desktop Effects. You can view the thread here:

http://forum.compiz-fusion.org/showthread.php?p=66888#post66888

Let's get this fixed in a future release!

[Blair Bethwaite (blair-bethwaite)]

I see you've posted this to ATI forums too, here's hoping we get an
answer. I've taken to running a maximised window in the background on
the second head just to avoid accidentally crashing the xserver.

On Wed, Oct 15, 2008 at 12:23 AM, linkx <email address hidden> wrote:
> Can anyone suggest where to post this bug so that it gets the attention
> of the appropriate people?
>
> I have asked the Compiz-Fusion folk, since it is directly related to
> Desktop Effects. You can view the thread here:
>
> http://forum.compiz-fusion.org/showthread.php?p=66888#post66888
>
> Let's get this fixed in a future release!
>
> --
> Xorg crashes when using two monitors set up by aticonfig (BigDesktop mode)
> https://bugs.launchpad.net/bugs/222163
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
In science one tries to tell people, in such a way
as to be understood by everyone, something that
no one ever knew before. But in poetry, it's the
exact opposite.
 - Paul Dirac

[Bryce Harrington (bryce)]

[This is an automated message]

As of Intrepid (8.10), we have a dedicated package 'fglrx-installer' for fglrx bugs, which now includes a process for upstreaming bugs to AMD.

  http://bugs.launchpad.net/ubuntu/+source/fglrx-installer

To transition your bug into the new fglrx-package, we need your help. Please do the following:

 a. Verify the bug occurs in Intrepid.
     (Intrepid ISOs: http://cdimage.ubuntu.com)
 b. If you haven't already, please include in the bug:
     * Your /var/log/Xorg.0.log
     * The output of `lspci -vvnn`
     * Steps to reproduce the issue
 c. Click 'Also affects distribution'
 d. Set 'Source Package Name' to 'fglrx-installer'
 e. Click Continue

Thank you. This will assist us in reviewing and upstreaming your fglrx bug, as appropriate.

[We'll expire the fglrx bugs in l-r-m-* in a month or so.]

[PiOuP (pbgerber)]

I have the same problem since 2 years with my laptop and my second monitor with fglrx and compiz.
My config : Thinkpad T60 - ATX1300 - Samsung SyncMaster 206BW - 1400x1050+1680x1050 (virtual screen) 3080x1050)

[Blair Bethwaite (blair-bethwaite)]

Confirming, as requested, that this bug is still present in Intrepid using xorg-driver-fglrx(2:8.543-0ubuntu4). No surprises there. Also attached

[Blair Bethwaite (blair-bethwaite)]

Attached Xorg.0.log.old has traceback from a crash caused by this bug. Steps to reproduce:
1. Install any fglrx driver
2. Attach secondary monitor and setup a big desktop using either aticonfig or amdcccle
3. Enable desktop effects
4. Left click anywhere on the secondary display (if another window already had focus a second click may be required)
CRASH

[Bryce Harrington (bryce)]

[Reported to AMD]

[PiOuP (pbgerber)]

Same problem with the latest driver 8.12 ...

[Mike (linux-attobyte)]

Tested against Intrepid 8.10 and the latest Ubuntu drivers.

Not sure if this is a different bug but mine is not a laptop. It also takes more then a single click on the desktop to get X to crash. I have to click from the desktop to a window and after 2 or 3 times X will crash. I have switch to /usr/bin/metacity and the crashes have went away.

Please let me know if you need anymore testing or system information.

$ lspci -vvnn (Display Controller only)

01:00.1 Display controller [0380]: ATI Technologies Inc RV530 [Radeon X1600] (Secondary) [1002:71e2]
 Subsystem: ATI Technologies Inc Device [1002:030a]
 Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Region 0: Memory at d1000000 (64-bit, non-prefetchable) [disabled] [size=64K]
 Capabilities: [50] Power Management version 2
  Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME

$ dpkg-query -l | grep -i fglrx
ii fglrx-amdcccle 2:8.543-0ubuntu4 Catalyst Control Center for the ATI graphics
ii fglrx-kernel-source 2:8.543-0ubuntu4 Kernel module source for the ATI graphics ac
ii fglrx-modaliases 2:8.543-0ubuntu4 Identifiers supported by the ATI graphics dr
ii xorg-driver-fglrx 2:8.543-0ubuntu4 Video driver for the ATI graphics accelera

[Ancoron Luziferis (ancoron)]

Same issue here:

- Kubuntu 8.10 Intrepid Ibex
- AMD64 X2 4400+ Dual-Core
- ATI/AMD Radeon HD2400 PRO
- fglrx driver version 8.543 from Ubuntu repos

The difference to others here to my case is that it can't be reproduced exactly. Sometimes it just happens when I log into KDE4 and the first window from the last session is about to be displayed. Then it crashes X with a stacktrace similar to the reporter of this bug and I get a blinking cursor in text mode on the black screen but cannot type anything, no prompt, nothing.

My case is somewhat different as I can still change between TTYs so I went into TTY1 and issued a ps to see that X is a zombie running at 100% CPU on one of my cores. I can issue all commands just normally (maybe because the other core is free for use). But when I try to do something like "/etc/init.d/kdm restart" the system crashes hard when it tries to terminate the defunct X.

I didn't have that problem before using Ubuntu 8.04 Hardy Heron neither with KDE3 nor XFCE.

I'll still have to try out if the problem persists when I try to disable all effects under KDE4.

Regards,

Ancoron

[Ancoron Luziferis (ancoron)]

^^ Addition:

I just took my old configuration from 8.04 to the clean install of 8.10 to get things working.

May this be an issue with the internal configuration database that the fglrx driver uses?

[Bryce Harrington (bryce)]

I was told this bug has been resolved.
If it's still an issue with 8.600 just now uploaded to -fglrx, feel free to reopen.

[Michael Baudino (gornack)]

I just upgraded to 9.04, the bug has disappeared.
I can click on my secondary desktop as much as I wish ;)
Maybe it's because it does not seem to be the fglrx driver anymore.
"lsmod | grep fglrx" gives nothing, anyway.

Hope this helps.

[linkx (link-mustbuilddigital)]

Yes! Look at me: click click click on my secondary desktop with compiz and
ATI . . .

On Thu, Apr 30, 2009 at 11:21 AM, Gornack <email address hidden> wrote:

> I just upgraded to 9.04, the bug has disappeared.
> I can click on my secondary desktop as much as I wish ;)
> Maybe it's because it does not seem to be the fglrx driver anymore.
> "lsmod | grep fglrx" gives nothing, anyway.
>
> Hope this helps.
>
> --
> Xorg crashes when using two monitors set up by aticonfig (BigDesktop mode)
> [AMD Feature#7647] [EPR#260264]
> https://bugs.launchpad.net/bugs/222163
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Ancoron Luziferis (ancoron)]

Well, I think you two are some lucky folks using the open-source radeon driver after the upgrade. Issue a "lsmod | grep radeon" to check if you're using it.

The radeon driver brings full 3D acceleration up to R5xx chips (so including the X1600) but it is very experimental when used with R6xx+ chips (all that Radeon HDxxxx cards). At work I'm using the free radeon driver successfully since Hardy on an X1300 with KDE4, most effects anabled and in dual-head mode.

I will upgrade this weekend and we will see if there is anything "fixed" in Jaunty for HD cards.

[Michael Baudino (gornack)]

On Thu, Apr 30, 2009 at 10:45 PM, Ancoron <email address hidden> wrote:

> Well, I think you two are some lucky folks using the open-source radeon
> driver after the upgrade. Issue a "lsmod | grep radeon" to check if
> you're using it.
>
>
You're right, I'm using the "radeon " module.
And I'm using a X1600 card.

--
Mike
KameHouse Prod.

[bugbot (bugbot)]

Thank you for reporting this issue about a driver from the
linux-restricted-modules package. lrm-2.4.24 was shipped with Ubuntu
8.04 which reached end-of-life for desktop support on May 12th, 2011.

For that reason, this bug report is being closed at this time. I'm
marking it wontfix because what you describe is probably a valid issue,
but there are no plans to work on lrm 2.4.24 bugs further.

The issue may be resolved in a newer version. If not, aside from filing
a new bug report, another angle may be to file it directly with the
driver vendor.