Bug 25266

Summary: Xorg crashes on specific action in an application - confirmed link to driver
Product: xorg Reporter: Andrey <trueurssian>
Component: Driver/RadeonAssignee: xf86-video-ati maintainers <xorg-driver-ati>
Status: RESOLVED DUPLICATE QA Contact: Xorg Project Team <xorg-team>
Severity: major    
Priority: medium    
Version: git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Xorg log from segfault crash
none
Relevant information from the crash that isnt reported in the log none

Description Andrey 2009-11-24 15:04:55 UTC
Xorg segfaults and quits when zooming in - in PCBNew, the Pcb routing suite that is part of the kicad electronics CAD suite. Only happens when using the radeon driver, no problems with nvidia cards or the generic VESA driver on the ATI card. on the same version of the X server. 

Relevant information:

Radeon mobile x300 video card
Kernel 2.6.31
Xorg 1.7.1.902 (confirmed with other 1.7.1.x xorgs as well)
xf86-video-ati 6.12.99.git20091014-1
Kicad 20090216-final (also confirmed with latest svn build)

Description:
In PCBNEW, upon zooming in to zoom 50 or higher. Xorg crashes reporting a
segmentation fault.

This only happens when there is a graphical Arc on the drawing layer OR
edges layer of the pcboard. Otherwise everything works as usual.

This only started happening on update from Xorg 1.6.9 (and its related drivers)

The actual complaint is "segfault at address(nil)"

There is more specific information dumped onto the console if I start X manually but for some reason it doesnt get saved to the log (but the backtrace does so... strange)


Relevent section of xorg.conf

Section "Device"
        Identifier  "RV370"
        Driver      "radeon"
        Card        "x300"

        Option "AccelMethod" "EXA"
        Option "EnablePageFlip" "on"
        Option "DynamicClocks" "off"
        Option "BusType" "PCIE"
        Option "ColorTiling" "on"
        Option "EXAVsync" "yes"

        Option  "MergedFB" "on"
        Option  "MonitorLayout" "LVDS, CRT"
        Option  "CRT2Hsync" "50-75"
        Option  "CRT2VRefresh" "50-82"
EndSection

Section "Module"
        Load  "ddc"  # ddc probing of monitor
        Load  "dbe"
        Load  "dri"
        Load  "extmod"
        Load  "glx"
        Load  "drm"
        Load  "bitmap" # bitmap-fonts
        Load  "type1"
        Load  "freetype"
        Load  "record"
EndSection
Comment 1 Alex Deucher 2009-11-24 15:10:38 UTC
please attach your xorg log and, if possible, a backtrace from the crash.
Comment 2 Andrey 2009-11-24 15:26:29 UTC
Created attachment 31451 [details]
Xorg log from segfault crash
Comment 3 Andrey 2009-11-24 15:27:04 UTC
Created attachment 31452 [details]
Relevant information from the crash that isnt reported in the log
Comment 4 Andrey 2009-11-24 15:28:59 UTC
Backtrace:
0: /usr/bin/X (xorg_backtrace+0x3b) [0x809ccab]
1: /usr/bin/X (0x8048000+0x52ff5) [0x809aff5]
2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb783140c]
3: /usr/lib/xorg/modules/libfb.so (fbPushFill+0xf9) [0xb7207149]
4: /usr/lib/xorg/modules/libfb.so (fbPushImage+0xd7) [0xb72072f7]
5: /usr/lib/xorg/modules/libfb.so (fbPushPixels+0x78) [0xb7207388]
6: /usr/bin/X (miPolyArc+0x153a) [0x818e16a]
7: /usr/lib/xorg/modules/libfb.so (fbPolyArc+0x8a) [0xb71f4d5a]
8: /usr/lib/xorg/modules/libexa.so (0xb71de000+0xf09d) [0xb71ed09d]
9: /usr/bin/X (0x8048000+0xd1245) [0x8119245]
10: /usr/bin/X (0x8048000+0x24dc9) [0x806cdc9]
11: /usr/bin/X (0x8048000+0x27a27) [0x806fa27]
12: /usr/bin/X (0x8048000+0x1ab45) [0x8062b45]
13: /lib/libc.so.6 (__libc_start_main+0xe6) [0xb7458b86]
14: /usr/bin/X (0x8048000+0x1a731) [0x8062731]
Segmentation fault at address (nil)

Fatal server error:
Caught signal 11 (Segmentation fault). Server aborting


The backtrace is from the log, just so you dont have to go looking for it. 
Comment 5 Michel Dänzer 2009-11-26 02:04:54 UTC

*** This bug has been marked as a duplicate of bug 25078 ***

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.