On Sat, 6 Oct 2012 11:17:08 +0200, Willy Tarreau <w...@1wt.eu> wrote: > On Sat, Oct 06, 2012 at 10:04:00AM +0100, Chris Wilson wrote: > > On Sat, 6 Oct 2012 10:42:58 +0200, Willy Tarreau <w...@1wt.eu> wrote: > > > On Sat, Oct 06, 2012 at 09:24:35AM +0100, Chris Wilson wrote: > > > > More likely X is segfaulting for another reason altogether. Can you > > > > please attach the stacktrace (with symbols!) and see if another > > > > bisection is required? > > > > > > Yes, here it is. > > > > > > (EE) intel(0): Failed to initialize kernel memory manager > > > > > > Backtrace: > > > 0: X(xf86SigHandler+0x7e) [0x80d8b5e] > > > 1: [0xffffe400] > > > 2: /usr/lib/xorg/modules/drivers//intel_drv.so(i830_allocator_init+0x332) > > > [0xb73756e2]
So far I have tested -intel-2.6.3 and -intel-2.7.1 with xorg-1.5.3 and kernel-3.7 on a 965gm both using the EXA AccelMethod, and both are still operational. Can you send the complete Xorg.log for the current failure? Thanks, -Chris -- Chris Wilson, Intel Open Source Technology Centre -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
