|Summary:||X.org 6.8.2 server dies on startup with signal 11 (ATI Radeon Mobility M6 LY)|
|Product:||xorg||Reporter:||Daniel Stone <daniel>|
|Component:||Driver/Radeon||Assignee:||Xorg Project Team <xorg-team>|
|Status:||RESOLVED DUPLICATE||QA Contact:|
|i915 platform:||i915 features:|
Description FreeDesktop Bugzilla Database Corruption Fix User 2005-06-25 07:36:17 UTC
Summary ======= OpenBSD 3.7, X.org 6.8.2, Fujitsu/Siemens E6646 i686 laptop, ATI Radeon Mobility M6 LY video chipset. The problem is that the X server crashes on startup with a signal 11. XFree86 184.108.40.2062 works fine on the same system. Details ======= I am using a Fujitsu/Siemens E6646 Lifebook i686 laptop. The video chipset is an ATI Radeon Mobility M6 LY. I have just (re)installed OpenBSD 3.7 (which includes X.org 6.8.2) on this system. The problem is that the X server crashes on startup with a signal 11. I have tried a number of different ways of generating /etc/X11/xorg.conf but all give the same behavior (signal 11 crash on startup): * xorgcfg * X -configure * xorgcfg -textmode * copy working XFree86 XF86Config for this same system (see below) Attached are an OpenBSD 'dmesg' (showing the video & other hardware as detected by the kernel), an /etc/X11/xorg.conf, and the /var/log/Xorg.0.log from 'startx' with that xorg.conf. The same system (booting from a different disk partition) runs OpenBSD 3.5-stable's XFree86 220.127.116.112 fine (attached are the 3.5-stable dmesg, /usr/X11R6/lib/X11/XF86Config, and /var/log/XFree86.0.log).
Comment 1 FreeDesktop Bugzilla Database Corruption Fix User 2005-06-25 07:37:52 UTC
Created attachment 2957 [details] GPG pubkey
Comment 2 FreeDesktop Bugzilla Database Corruption Fix User 2005-06-25 07:47:54 UTC
Created attachment 2958 [details] [review] Simplify Imakefiles and fix build (bad)
Comment 3 FreeDesktop Bugzilla Database Corruption Fix User 2005-06-25 07:49:15 UTC
Created attachment 2959 [details] [review] Proposed patch
Comment 4 FreeDesktop Bugzilla Database Corruption Fix User 2005-06-25 07:50:20 UTC
Created attachment 2960 [details] [review] fix version check
Comment 5 FreeDesktop Bugzilla Database Corruption Fix User 2005-06-25 07:55:03 UTC
Created attachment 2961 [details] Xorg log file As noted in the bug text, OpenBSD 3.5's XFree86 18.104.22.1682 works fine on the same system. This attachment shows the OpenBSD 3.5 kernel's detection of hardware (including the video chipset).
Comment 6 FreeDesktop Bugzilla Database Corruption Fix User 2005-06-25 07:56:36 UTC
Created attachment 2962 [details] [review] Patch I'm applying This is the /usr/X11R6/lib/X11/XF86Config file I use for OpenBSD 3.5's XFree86 22.214.171.1242 on this same system (which works fine).
Comment 7 FreeDesktop Bugzilla Database Corruption Fix User 2005-06-25 07:58:01 UTC
Created attachment 2963 [details] [review] Proposed patch
Comment 8 Adam Jackson 2005-07-03 14:46:00 UTC
starting with the 126.96.36.199 snapshot, on linux systems, the X server can print its own backtrace when it crashes. please confirm that these bugs are still valid with 188.8.131.52 or later, and if they are please attach a the server log from the crash.
Comment 9 Karl Sjödahl 2005-07-19 02:43:36 UTC
I have the same problem with a ATI Radeon IGP 340M card and OpenBSD. Today I tryed to compile a snapshot on OpenBSD 3.7-current (from 22 june). 184.108.40.206 and 220.127.116.11 won't compile on OpenBSD but 18.104.22.168 compiled. It has the same problems and the only warning I get is: (WW) RADEON(0): LCD DDC Info Table found! and then the same: Fatal server error: Caught signal 11. Server aborting.
Comment 10 Jonathan Thornburg 2005-09-11 07:12:55 UTC
Created attachment 3228 [details] copy of my /etc/X11/xorg.conf file
Comment 11 Jonathan Thornburg 2005-09-11 07:13:35 UTC
Created attachment 3229 [details] copy of /var/log/Xorg.0.log when running X server under gdb
Comment 12 Jonathan Thornburg 2005-09-11 07:15:13 UTC
Created attachment 3230 [details] gdb log (including traceback) from running X server This is the gdb log when following the instructions on http://wiki.x.org/wiki/DebuggingTheXserver in the section "Debugging with one machine", subsection "Version 1". Unfortunately, it seems my X server was built with only limited debugging symbols, so many addresses aren't resolved. :( :(
Comment 13 Jonathan Thornburg 2005-09-11 07:21:08 UTC
I realise that the gdb traceback I've just submitted isn't very useful (not enough debugging symbols in the X server binary). I will try to compile a new X server from source with full -g debugging support, and if successful, I'll submit a new (& hopefully more informative) gdb traceback.