Created attachment 19526 [details] command lspci -vnn I have collect all the information for this. I have found the stack trace in xorg.0.log and startx.log.
Created attachment 19527 [details] startx output
Created attachment 19528 [details] xorg.0.log
Created attachment 19529 [details] dmesg
Backtrace: 0: /usr/X11R6/bin/X(xf86SigHandler+0x79) [0x80c3069] 1: [0xb7f5c400] 2: /usr/X11R6/bin/X(xf86DoEDID_DDC2+0xd9) [0x80f89b9] 3: /usr/X11R6/bin/X(xf86OutputGetEDID+0x23) [0x80e95f3] 4: /usr/lib/xorg/modules/drivers//intel_drv.so [0xb79db5b2] 5: /usr/lib/xorg/modules/drivers//intel_drv.so [0xb79db64f] 6: /usr/X11R6/bin/X(xf86ProbeOutputModes+0x2ae) [0x80ebaee] 7: /usr/X11R6/bin/X [0x80f28d0] 8: /usr/X11R6/bin/X(RRGetInfo+0x99) [0x816e249] 9: /usr/X11R6/bin/X(ProcRRGetScreenResources+0x8c) [0x81726ec] 10: /usr/X11R6/bin/X [0x816b4f5] 11: /usr/X11R6/bin/X(Dispatch+0x34f) [0x808c91f] 12: /usr/X11R6/bin/X(main+0x47d) [0x8071d8d] 13: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7b7f685] 14: /usr/X11R6/bin/X [0x8071171] Saw signal 11. Server aborting.
Quanxian, could you describe the connection type: which port (DVI?) used on the board? You told me the same package works fine on SuSE 11.0. Is it with the same connection cable and monitor?
Looks like #17892 is dup with this, and my patch is on that one too.
*** This bug has been marked as a duplicate of bug 17892 ***
I do the testing on RC4 packages. Still not works. Also I have tested RC3 with Zhenyu's patch, it also doesn't works. Seems this problem is not same as bug 17892. Also I got some information from dmesg. [ 179.709708] [drm:i915_getparam] *ERROR* Unknown parameter 5 [ 180.380260] set status page addr 0x02aa0000 [ 180.460556] [drm:i915_getparam] *ERROR* Unknown parameter 5 Any suggestion for this?
By the way, This time stack trace(comment #4) disappears. The port is VGA not DVI.
Quanxian, have you changed to from Ubuntu's kernel to GEM kernel? The dmesg in comment#8 does not exist in your first dmesg (in comment#3).
We have already fixed a crash relate to display output probe in 2.5.0, this should be fixed, close this, reopen if you still see this.
Sorry to response later. Zhenyu, Would you like to push the fix commit to this bug for us to tracking? Thanks Quanixna Wang
We have two commits might be relate to this one. commit 986c8df79e83c369655ad786a6bf6342b53c535d Author: Adam Jackson <ajax@nwnk.net> Date: Thu Oct 16 10:24:04 2008 +0800 Fix Mac mini crash in DDC mode probe SDVO on Mac mini trys to get EDID from CRT port, which failed with recent DVI-I change. Author: Zhenyu Wang <zhenyu.z.wang@intel.com> Date: Sun Oct 12 08:07:44 2008 +0800 Bug #17892: Fix possible crash in CRT probe Introduced in patch for DVI-I CRT probe, if no EDID CRT monitor is connected, origin code destroys default DDC bus which causes crash in later get_modes call. Change it to setup and destroy DDC bus as needed in get_modes, so we always reprobe and get current state.
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.