Created attachment 22211 [details] Xorg.0.log hello, Attempting to start X results in a crash. Backtrace: 0: X(xorg_backtrace+0x3b) [0x812072b] 1: X(xf86SigHandler+0x4d) [0x80c727d] 2: [0xffffe400] 3: X(xf86CrtcSetMode+0x36) [0x80e1445] 4: /usr/X11R6/lib/xorg/modules/drivers//intel_drv.so(i830GetLoadDetectPipe+0x147) [0xb7b65d01] 5: /usr/X11R6/lib/xorg/modules/drivers//intel_drv.so [0xb7b60188] 6: X(xf86ProbeOutputModes+0x19f) [0x80de0fd] 7: X(xf86InitialConfiguration+0xda) [0x80deba6] 8: /usr/X11R6/lib/xorg/modules/drivers//intel_drv.so [0xb7b6b0fc] 9: /usr/X11R6/lib/xorg/modules/drivers//intel_drv.so [0xb7b6dcdf] 10: X(InitOutput+0xdf3) [0x80a4e9b] 11: X(main+0x1e7) [0x806be39] 12: /lib/libc.so.6(__libc_start_main+0xe5) [0xb7cfe59d] 13: X [0x806b4c1]
Created attachment 22212 [details] xorg.conf
The machine is a desktop running linux, kernel 2.6.28.1. Intel(R) Celeron(R) CPU 2.53GHz (II) intel(0): Integrated Graphics Chipset: Intel(R) 865G (--) intel(0): Chipset: "865G" (--) intel(0): Linear framebuffer at 0xE8000000 (--) intel(0): IO registers at addr 0xFEB80000 (WW) intel(0): libpciaccess reported 0 rom size, guessing 64kB
on further testing, xorg-server 1.6.99 and intel driver current git (as of 1/25/09) both work just fine under kernel 2.6.27.10. They cause lockups under 2.6.28.1. I believe its the new GEM that isn't working properly. I get kernel messages, like: [drm:i915_gem_idle] *ERROR* hardware wedged freezing the OS for about 5 min. at a time in cases.
Adjusting severity: crashes & hangs should be marked critical.
So, wait, is this bug about the segfault at startup, or about hangs after startup while apps are running? If it's about later hangs, the following kernel commit for review may help: commit cfa16a0de5392c54db553ec2233a7110e4b4da7a Author: Eric Anholt <eric@anholt.net> Date: Tue May 26 18:46:16 2009 -0700 drm/i915: Apply a big hammer to 865 GEM object CPU cache flushing.
Feedback timeout -- I think this has been fixed by the commit mentioned, which landed in 2.6.30.
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.