From: Chris Wilson <chris@chris-wilson.co.uk>
To: Willy Tarreau <w@1wt.eu>
Cc: Dave Airlie <airlied@gmail.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
linux-kernel@vger.kernel.org
Subject: Re: 3.5 regression on i915
Date: Sat, 06 Oct 2012 10:04:00 +0100 [thread overview]
Message-ID: <275ffc$6skdfn@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <20121006084258.GB22618@1wt.eu>
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.vetter@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
next prev parent reply other threads:[~2012-10-06 9:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 23:42 3.5 regression on i915 Willy Tarreau
2012-10-05 23:48 ` Dave Airlie
2012-10-05 23:58 ` Willy Tarreau
2012-10-06 7:27 ` Willy Tarreau
2012-10-06 7:43 ` Dave Airlie
2012-10-06 7:59 ` Willy Tarreau
2012-10-06 8:24 ` Chris Wilson
2012-10-06 8:42 ` Willy Tarreau
2012-10-06 9:04 ` Chris Wilson [this message]
2012-10-06 9:17 ` Willy Tarreau
2012-10-06 16:10 ` Chris Wilson
2012-10-06 20:43 ` Willy Tarreau
2012-10-06 8:04 ` Chris Wilson
2012-10-06 8:20 ` Willy Tarreau
2012-10-06 8:43 ` Chris Wilson
2012-10-07 21:00 ` Daniel Vetter
2012-10-07 21:07 ` Willy Tarreau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='275ffc$6skdfn@fmsmga002.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=w@1wt.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox