From: Chris Wilson <chris@chris-wilson.co.uk>
To: Willy Tarreau <w@1wt.eu>, Dave Airlie <airlied@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>, linux-kernel@vger.kernel.org
Subject: Re: 3.5 regression on i915
Date: Sat, 06 Oct 2012 09:24:35 +0100 [thread overview]
Message-ID: <051c15$4i14fm@AZSMGA002.ch.intel.com> (raw)
In-Reply-To: <20121006075956.GF21163@1wt.eu>
On Sat, 6 Oct 2012 09:59:56 +0200, Willy Tarreau <w@1wt.eu> wrote:
> On Sat, Oct 06, 2012 at 03:43:56AM -0400, Dave Airlie wrote:
> > On Sat, Oct 6, 2012 at 3:27 AM, Willy Tarreau <w@1wt.eu> wrote:
> > > On Sat, Oct 06, 2012 at 01:58:45AM +0200, Willy Tarreau wrote:
> > >> On Sat, Oct 06, 2012 at 09:48:57AM +1000, Dave Airlie wrote:
> > >> > Any reason you don't have KMS, you'll keep hitting these non-kms bugs
> > >> > since it has no users anymore really.
> > >> >
> > >> > Granted they'll get fixed, but I suspect its a losing battle over time.
> > >>
> > >> Well, back in old times every time I tried to enable it, I only ran into
> > >> problems so I got used to disable it, which made sense since it didn't
> > >> bring me any benefit.
> > >
> > > OK I found why in the end. When I enable KMS, my X server fails to start
> > > and segfaults in intel_drv.so. So I think that the comment in Kconfig
> > > below is quite appropriate :
> >
> > Okay are you running a really old userspace? just wondering what could
> > cause this.
>
> yes, my Xorg is 1.4.2 and xf86-video-intel is 2.7.1.
>
> I have additional information, I retested with 3.4.12 with and without KMS :
>
> 3.4.12, no KMS : X works fine
> 3.4.12, KMS : X works fine but some garbage follows the mouse pointer
> on the external display
> 3.5.x no KMS : kernel BUG
> 3.5.x KMS : X server segfaults in intel driver
>
> So in fact, both the KMS/non-KMS confs have regressed in 3.5 on this setup.
>
> It is possible that the commit which removed the list of pinned inactive
> objects (1b50247a) has uncovered another long-time bug.
More likely X is segfaulting for another reason altogether. Can you
please attach the stacktrace (with symbols!) and see if another
bisection is required?
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-10-06 8:24 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 [this message]
2012-10-06 8:42 ` Willy Tarreau
2012-10-06 9:04 ` Chris Wilson
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='051c15$4i14fm@AZSMGA002.ch.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