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]
Drat, that is:
commit 7bb6fb8dd958ae773ac205282e3c0b56c22e01ed
Author: Daniel Vetter <daniel.vet...@ffwll.ch>
Date: Tue Apr 24 08:22:52 2012 +0200
drm/i915: disallow gem ums init ioctl for kms
This ioctl used in a kms driver is only useful to create massive
havoc.
Can't see just why -intel crashes, but I presume it is during the
i830_free_memory along that path.
Anyway, looks like that patch needs to be reverted.
-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/
