Bug 515842 - Segmention fault when starting X
Summary: Segmention fault when starting X
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-08-05 22:56 UTC by Sebastian Vahl
Modified: 2018-04-11 18:03 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-08-18 11:40:34 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Xorg.0.log after crash (19.34 KB, text/plain)
2009-08-05 22:56 UTC, Sebastian Vahl
no flags Details
Xorg.0.log with -27 (9.30 KB, text/plain)
2009-08-06 15:34 UTC, Sebastian Vahl
no flags Details
Xorg.0.log after crash with -27 (9.40 KB, text/plain)
2009-08-06 15:59 UTC, Thomas Janssen
no flags Details
Xorg.0.log with -28 (9.29 KB, application/octet-stream)
2009-08-07 23:03 UTC, Sebastian Vahl
no flags Details

Description Sebastian Vahl 2009-08-05 22:56:45 UTC
Created attachment 356438 [details]
Xorg.0.log after crash

Description of problem:
On my current live image spin based on today's rawhide X is crashing with a segmention fault.

Backtrace:
0: /usr/bin/X(xorg_backtrace+0x3c) [0x80a44ac]
1: /usr/bin/X [0x80a7ca6]                     
2: [0xe6c40c]                                 
3: /lib/libc.so.6(__rawmemchr+0x40) [0x346ac0]
4: /lib/libc.so.6 [0x338677]                  
5: /lib/libc.so.6(__isoc99_vsscanf+0x73) [0x3273d3]
6: /lib/libc.so.6(__isoc99_sscanf+0x1f) [0x32734f] 
7: /usr/bin/X [0x80bb492]                          
8: /usr/bin/X(InitOutput+0x5a0) [0x80b78d0]        
9: /usr/bin/X [0x8062fdb]                          
10: /lib/libc.so.6(__libc_start_main+0xe6) [0x2dfb36]
11: /usr/bin/X [0x8062d81]                           

Link map:
0xe6e000: (vdso)
0x4e5000: /usr/lib/libxf86config.so.0
0xf3f000: /usr/lib/libpciaccess.so.0
0xe13000: /usr/lib/libXfont.so.1
0x810000: /usr/lib/libXau.so.6
0x110000: /usr/lib/libfontenc.so.1
0xb5c000: /usr/lib/libpixman-1.so.0
0xf68000: /usr/lib/libhal.so.1
0xa2c000: /lib/libdbus-1.so.3
0xf85000: /lib/libpthread.so.0
0x53e000: /usr/lib/libXdmcp.so.6
0xeea000: /usr/lib/libssl.so.8
0x116000: /usr/lib/libcrypto.so.8
0xae3000: /lib/libdl.so.2
0x8ad000: /lib/libz.so.1
0x28f000: /lib/libaudit.so.0
0x2aa000: /lib/libselinux.so.1
0x79f000: /lib/libm.so.6
0xaa8000: /lib/librt.so.1
0x2c9000: /lib/libc.so.6
0x444000: /usr/lib/libfreetype.so.6
0x971000: /lib/libcap.so.2
0x8fb000: /lib/ld-linux.so.2
0x748000: /lib/libgssapi_krb5.so.2
0x562000: /lib/libkrb5.so.3
0x6e4000: /lib/libcom_err.so.2
0xd8c000: /lib/libk5crypto.so.3
0x4f6000: /lib/libresolv.so.2
0x85b000: /lib/libattr.so.1
0x4db000: /lib/libkrb5support.so.0
0x84a000: /lib/libkeyutils.so.1
0x93f000: /usr/lib/xorg/modules/extensions/libextmod.so
0xc7d000: /usr/lib/xorg/modules/extensions/libdbe.so
0x61b000: /usr/lib/xorg/modules/extensions/libglx.so
0x50f000: /usr/lib/xorg/modules/extensions/librecord.so
0x512000: /usr/lib/xorg/modules/extensions/libdri.so
0xce0000: /usr/lib/libdrm.so.2
0x51c000: /usr/lib/xorg/modules/extensions/libdri2.so
0x520000: /usr/lib/xorg/modules/drivers/ati_drv.so
0xfa0000: /usr/lib/xorg/modules/drivers/radeon_drv.so
0x522000: /usr/lib/libdrm_radeon.so.1
0x527000: /usr/lib/xorg/modules/drivers/vesa_drv.so
0x8d2000: /usr/lib/xorg/modules/drivers/fbdev_drv.so
0x8c0000: /usr/lib/xorg/modules/linux/libfbdevhw.so
0xe92000: /lib/libgcc_s.so.1
Segmentation fault at address (nil)

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



Version-Release number of selected component (if applicable):
xorg-x11-server-Xorg-1.6.99-25.20090804.fc12.i686

How reproducible:
ever

Steps to Reproduce:
1. update to recent X
2. startx
  
Actual results:
crash

Expected results:
X

Additional info:
I've filed this bug against xorg-x11-server-Xorg because /usr/bin/X is mostly mentioned in the backtrace in Xorg.0.log. If I was wrong please move it to the proper component.

Comment 1 Warren Togami 2009-08-06 01:39:14 UTC
Upgrade your xorg-x11-server to -27 or later.  This is already fixed.

Comment 2 Sebastian Vahl 2009-08-06 15:34:58 UTC
Created attachment 356538 [details]
Xorg.0.log with -27

It's still crashing here with xorg-x11-server-Xorg-1.6.99-27.20090804.fc12.i686:

Backtrace:
0: /usr/bin/X(xorg_backtrace+0x3c) [0x80a442c]
1: /usr/bin/X [0x80a7c26]
2: [0xfcb40c]
3: /usr/lib/xorg/modules/drivers/nouveau_drv.so [0x5cdb64]
4: /usr/bin/X(xf86DeleteScreen+0x6c) [0x80bf5dc]
5: /usr/bin/X(InitOutput+0x637) [0x80b78e7]
6: /usr/bin/X [0x8062f5b]
7: /lib/libc.so.6(__libc_start_main+0xe6) [0xb7ab36]
8: /usr/bin/X [0x8062d01]

Link map:
0xfcd000: (vdso)
0xa35000: /usr/lib/libxf86config.so.0
0xb5c000: /usr/lib/libpciaccess.so.0
0xe2a000: /usr/lib/libXfont.so.1
0xd95000: /usr/lib/libXau.so.6
0x929000: /usr/lib/libfontenc.so.1
0x6e2000: /usr/lib/libpixman-1.so.0
0xd59000: /usr/lib/libhal.so.1
0x110000: /lib/libdbus-1.so.3
0x47a000: /lib/libpthread.so.0
0xb38000: /usr/lib/libXdmcp.so.6
0x60e000: /usr/lib/libssl.so.8
0x2dd000: /usr/lib/libcrypto.so.8
0x94e000: /lib/libdl.so.2
0x4dc000: /lib/libz.so.1
0x157000: /lib/libaudit.so.0
0x663000: /lib/libselinux.so.1
0xefb000: /lib/libm.so.6
0x860000: /lib/librt.so.1
0xb64000: /lib/libc.so.6
0x172000: /usr/lib/libfreetype.so.6
0x884000: /lib/libcap.so.2
0x592000: /lib/ld-linux.so.2
0x209000: /lib/libgssapi_krb5.so.2
0x744000: /lib/libkrb5.so.3
0xf46000: /lib/libcom_err.so.2
0x237000: /lib/libk5crypto.so.3
0x8d4000: /lib/libresolv.so.2
0x4b1000: /lib/libattr.so.1
0x262000: /lib/libkrb5support.so.0
0xa59000: /lib/libkeyutils.so.1
0x26b000: /usr/lib/xorg/modules/extensions/libextmod.so
0x28c000: /usr/lib/xorg/modules/extensions/libdbe.so
0x4ef000: /usr/lib/xorg/modules/extensions/libglx.so
0x291000: /usr/lib/xorg/modules/extensions/librecord.so
0x294000: /usr/lib/xorg/modules/extensions/libdri.so
0x29e000: /usr/lib/libdrm.so.2
0x2a9000: /usr/lib/xorg/modules/extensions/libdri2.so
0x5b4000: /usr/lib/xorg/modules/drivers/nouveau_drv.so
0x2ad000: /usr/lib/libdrm_nouveau.so.1
0x2b2000: /usr/lib/xorg/modules/drivers/vesa_drv.so
0x2b8000: /usr/lib/xorg/modules/drivers/fbdev_drv.so
0xec3000: /usr/lib/xorg/modules/linux/libfbdevhw.so
0x559000: /lib/libgcc_s.so.1
Segmentation fault at address 0xe0

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

Comment 3 Thomas Janssen 2009-08-06 15:59:35 UTC
Created attachment 356540 [details]
Xorg.0.log after crash with -27

Not fixed with -27 installed in VM.

Comment 4 Thomas Janssen 2009-08-06 17:36:52 UTC
I reopened the bug since it's not fixed. Crash confirmed with -27

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 5 Matěj Cepl 2009-08-07 13:48:04 UTC
Give a try to -28, please.

Comment 6 Thomas Janssen 2009-08-07 14:12:02 UTC
Yes, -28 fixed it here. Thanks, that was fast.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 7 Adam Williamson 2009-08-07 22:26:48 UTC
(-28 has been tagged through the freeze so it will show up in the next rawhide compose)

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 8 Sebastian Vahl 2009-08-07 23:03:02 UTC
Created attachment 356732 [details]
Xorg.0.log with -28

-28 doesn't fix it for me. I should say, that I only update the related xorg-x11-server packages from koji (-common, -xorg, libxf86config). The rest is normal rawhide from today: 

Backtrace:
0: /usr/bin/X(xorg_backtrace+0x3c) [0x80a442c]
1: /usr/bin/X [0x80a7c26]
2: [0x9cb40c]
3: /usr/lib/xorg/modules/drivers/nouveau_drv.so [0x87eb64]
4: /usr/bin/X(xf86DeleteScreen+0x6c) [0x80bf5dc]
5: /usr/bin/X(InitOutput+0x637) [0x80b78e7]
6: /usr/bin/X [0x8062f5b]
7: /lib/libc.so.6(__libc_start_main+0xe6) [0x4a8b36]
8: /usr/bin/X [0x8062d01]

Link map:
0x9cd000: (vdso)
0x481000: /usr/lib/libxf86config.so.0
0xb82000: /usr/lib/libpciaccess.so.0
0x673000: /usr/lib/libXfont.so.1
0x1da000: /usr/lib/libXau.so.6
0x272000: /usr/lib/libfontenc.so.1
0x110000: /usr/lib/libpixman-1.so.0
0xa77000: /usr/lib/libhal.so.1
0x8ff000: /lib/libdbus-1.so.3
0x412000: /lib/libpthread.so.0
0x172000: /usr/lib/libXdmcp.so.6
0xd1d000: /usr/lib/libssl.so.8
0x278000: /usr/lib/libcrypto.so.8
0x227000: /lib/libdl.so.2
0xef7000: /lib/libz.so.1
0x178000: /lib/libaudit.so.0
0xc0d000: /lib/libselinux.so.1
0x9ea000: /lib/libm.so.6
0x955000: /lib/librt.so.1
0x492000: /lib/libc.so.6
0x6ab000: /usr/lib/libfreetype.so.6
0xfe1000: /lib/libcap.so.2
0x621000: /lib/ld-linux.so.2
0x193000: /lib/libgssapi_krb5.so.2
0x742000: /lib/libkrb5.so.3
0x1c1000: /lib/libcom_err.so.2
0xea2000: /lib/libk5crypto.so.3
0x43d000: /lib/libresolv.so.2
0x1c4000: /lib/libattr.so.1
0x1c9000: /lib/libkrb5support.so.0
0xe91000: /lib/libkeyutils.so.1
0xbab000: /usr/lib/xorg/modules/extensions/libextmod.so
0x1d2000: /usr/lib/xorg/modules/extensions/libdbe.so
0x7fb000: /usr/lib/xorg/modules/extensions/libglx.so
0xf65000: /usr/lib/xorg/modules/extensions/librecord.so
0x1dd000: /usr/lib/xorg/modules/extensions/libdri.so
0x1e7000: /usr/lib/libdrm.so.2
0x1f2000: /usr/lib/xorg/modules/extensions/libdri2.so
0x865000: /usr/lib/xorg/modules/drivers/nouveau_drv.so
0x1f6000: /usr/lib/libdrm_nouveau.so.1
0x1fb000: /usr/lib/xorg/modules/drivers/vesa_drv.so
0x201000: /usr/lib/xorg/modules/drivers/fbdev_drv.so
0xc91000: /usr/lib/xorg/modules/linux/libfbdevhw.so
0x22c000: /lib/libgcc_s.so.1
Segmentation fault at address 0xe0

Comment 9 Adam Williamson 2009-08-08 00:50:19 UTC
there's a -30 now, and there is also an updated -nouveau driver that you may have missed.

can you try with the new nouveau driver package first, then with both the new nouveau and -30?

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 10 Sebastian Vahl 2009-08-08 07:14:33 UTC
confirmed to work with -28 and -30 and xorg-x11-drv-nouveau-0.0.15-2.20090805git712064e.fc12.

I've tried the -29 and -30 packages also yesterday (without newer nouveau), but they were failing, too. But there were no libxf86config available for koji in this build, so I've thought this was a temporary failure.


Note You need to log in before you can comment on or make changes to this bug.