Bug 21333 - Spontaneous Xorg crash [EXA, radeon]
Summary: Spontaneous Xorg crash [EXA, radeon]
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: 7.4 (2008.09)
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-22 04:53 UTC by Øyvind Stegard
Modified: 2009-05-13 00:57 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Øyvind Stegard 2009-04-22 04:53:17 UTC
This bug was originally reported downstream here:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/365074

I just experienced a completely spontaneous Xorg crash using radeon driver. Seems EXA-related according to the stack trace. I wasn't doing anything other than typing an email in Evolution (no videos, no OpenGL-apps other than Compiz itself).

- Ubuntu Jaunty RC (tracking/current)
- Running Compiz
- Using radeon Xorg driver (xserver-xorg-video-radeon 6.12.1-0ubuntu2)
- Kernel linux-image-2.6.28-11-generic 2.6.28-11.41 (Ubuntu)
- Mesa 7.4-0ubuntu1
- Xorg 7.4~5ubuntu18

Hardware:
- ATI X1400 Radeon Mobility, 128MB RAM
- Intel Core Duo 2GHz, 2GB RAM

Here is the backtrace:
0: /usr/X11R6/bin/X(xorg_backtrace+0x3b) [0x813518b]
1: /usr/X11R6/bin/X(xf86SigHandler+0x55) [0x80c7be5]
2: [0xb7f07400]
3: /usr/X11R6/bin/X(dixFreePrivates+0x8c) [0x8072bdc]
4: /usr/lib/xorg/modules//libfb.so(fbDestroyPixmap+0x32) [0xb75dc282]
5: /usr/lib/xorg/modules//libexa.so [0xb75b7c60]
6: /usr/X11R6/bin/X [0x817f5e2]
7: /usr/lib/xorg/modules/extensions//libextmod.so [0xb78a3018]
8: /usr/X11R6/bin/X(dixDestroyPixmap+0x15) [0x8086d35]
9: /usr/X11R6/bin/X(FreeResource+0x10c) [0x8074c3c]
10: /usr/X11R6/bin/X(ProcFreePixmap+0x93) [0x8088663]
11: /usr/X11R6/bin/X(Dispatch+0x33f) [0x808d57f]
12: /usr/X11R6/bin/X(main+0x3bd) [0x80722ed]
13: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7ada775]
14: /usr/X11R6/bin/X [0x80717a1]
Saw signal 11. Server aborting.
Output LCD1 disable success
Blank CRTC 0 success
Disable CRTC 0 success
Blank CRTC 1 success
Disable CRTC 1 success
Enable CRTC 0 success
Unblank CRTC 0 success
 ddxSigGiveUp: Closing log
 ddxSigGiveUp: re-raising 11



Xorg.0.log from crash:
http://launchpadlibrarian.net/25849192/Xorg.0.log

Kernel log:
http://launchpadlibrarian.net/25849163/dmesg.txt

lspci:
http://launchpadlibrarian.net/25849181/lspci.txt
Comment 1 Michel Dänzer 2009-04-27 08:59:07 UTC
Could be related to bug 21132 et al. Apparently that only happens with OpenGL compositing, if that's true for you as well then it seems most likely memory corruption caused by the Mesa driver.
Comment 2 Øyvind Stegard 2009-04-27 18:26:32 UTC
I did run Compiz at the time. However, bug 21132 indicates that crashes occur rather frequently, but this has only happened once to me after upgrading to Ubuntu Jaunty (I upgraded when it was late in beta phase). So I reported it, but unfortunately I have no idea how to reproduce it.

The only "hint" I got is that I remember changing font rendering options back and forth some time before the crash (from sub-pixel to gray-scale and back a few times). Also, sub-pixel font rendering tends to result in corruption for some glyphs, which indicates a problem (might just be related to other small pixmap corruptions that happens with the radeon driver and my graphics card, like bug 18397). I'll try and see if I can provoke crash by jiggling with font settings.
Comment 3 Michel Dänzer 2009-04-30 07:29:34 UTC
A fix for a memory use-after-free in the r300 driver just went into Mesa Git master and mesa_7_4_branch. Would be great if you could try if it helps for this problem as well.
Comment 4 Øyvind Stegard 2009-04-30 07:57:15 UTC
(In reply to comment #3)
> A fix for a memory use-after-free in the r300 driver just went into Mesa Git
> master and mesa_7_4_branch. Would be great if you could try if it helps for
> this problem as well.
> 

Will do, I'm going to test for bug 21223, and I'll take this bug at the same time. Not sure I'll be able to reproduce this one, though (hasn't happened since I reported it).
Comment 5 Øyvind Stegard 2009-05-12 06:12:26 UTC
I've not been able to reproduce this yet (haven't tried that hard either), but at the same time another Ubuntu user with an ATI X1400 got the exact same crash/backtrace: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/375414

Comment 6 Michel Dänzer 2009-05-12 07:11:20 UTC
(In reply to comment #5)
> at the same time another Ubuntu user with an ATI X1400 got the exact same
> crash/backtrace:
> https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/375414

He's using libgl1-mesa-dri 7.4-0ubuntu3, which AFAICT doesn't have my fix (only -0ubuntu3.1 or -0ubuntu4 does).
Comment 7 Øyvind Stegard 2009-05-12 09:47:46 UTC
(In reply to comment #6)
> (In reply to comment #5)
> > at the same time another Ubuntu user with an ATI X1400 got the exact same
> > crash/backtrace:
> > https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/375414
> 
> He's using libgl1-mesa-dri 7.4-0ubuntu3, which AFAICT doesn't have my fix (only
> -0ubuntu3.1 or -0ubuntu4 does).
> 

Ok, I have libgl1-mesa-dri 7.4-0ubuntu3.1 (from Jaunty proposed updates).

Changelog says this:
 * debian/patches/106_compiz_ring_switcher_xorg_segv_on_radeon.diff:
    fix xserver segv triggered by compiz ring switcher plugin for users
    with r300/r400 radeon chipsets and -ati driver. Patch previously
    commited to mesa master as c28707b50701b1cf8727be29d61e2d939c6ee58f
    and also to mesa_7_4_branch as a1ce4efefbb7f796a0a24544a1e893a56848f0c1.
    Note: it was commited to the 7.4 branch after mesa 7.4.0 release.
    (LP: #368049)

Does this mean it has been fixed for those of us running with the updated Mesa package ? I won't spend any time trying to reproduce it, if that's the case ;).
Comment 8 Michel Dänzer 2009-05-13 00:57:31 UTC
Let's assume that fix took care of it.


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.