Bug 23410

Summary: git commit breaks xorg
Product: xorg Reporter: Paulo Dias <paulo.miguel.dias>
Component: Driver/RadeonAssignee: xf86-video-ati maintainers <xorg-driver-ati>
Status: RESOLVED NOTABUG QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium    
Version: git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Paulo Dias 2009-08-19 07:51:56 UTC 
latest git commit 72e0d1b2cb11a67b8e4be4c74913ee44dc051c5b breaks xorg, making him segfault. reverting it fixes the problem. 

i didnt activated colortiling btw.

rs485 hw (aka the evil one)
xorg-server 1.6.99.1+git20090705.fd4eed69

best regards
Comment 1 Paulo Dias 2009-08-19 07:53:38 UTC 
forgot to mention, using mesa/drm from master, today pull.
using linus kernel 2.6.31 rc6 (with suport for opengl 1.5), dri2/kms for radeon.

best regards
Comment 2 Paulo Dias 2009-08-19 14:10:24 UTC 
bakctrace of the segfault

Backtrace:
0: /usr/bin/X(xorg_backtrace+0x3b) [0x80b543b]
1: /usr/bin/X [0x80a9785]
2: [0xffffe40c]
3: /usr/lib/xorg/modules/libexa.so [0xb79844a3]
4: /usr/lib/xorg/modules/libexa.so [0xb7984853]
5: /usr/lib/xorg/modules/libexa.so [0xb798038b]
6: /usr/lib/xorg/modules/libexa.so [0xb798517c]
7: /usr/bin/X [0x811180d]
8: /usr/bin/X [0x809805e]
9: /usr/bin/X [0x809a7cf]
10: /usr/bin/X [0x8067665]
11: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7d4d775]
12: /usr/bin/X [0x8067221]
Segmentation fault at address 0x5

Fatal server error:
Caught signal 11 (Segmentation fault). Server aborting
Comment 3 Dave Airlie 2009-08-19 15:59:03 UTC 
you could read the commit message.
Comment 4 Paulo Dias 2009-08-20 06:21:03 UTC 
if you mean the warning about using latest git, i did read it, but acording to the commiter, it should be able to work with older gits/1.6 IF colortiling is not enabled (which is the case), so i believe its still a bug, or am i wrong?

best regards

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.