All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Chris Wilson <chris@chris-wilson.co.uk>
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, 6 Oct 2012 11:17:08 +0200	[thread overview]
Message-ID: <20121006091708.GC22618@1wt.eu> (raw)
In-Reply-To: <275ffc$6skdfn@fmsmga002.fm.intel.com>

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]
> 
> 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.

Good catch, but now it dies later after screen goes black :

Backtrace:
0: X(xf86SigHandler+0x7e) [0x80d8b5e]
1: [0xffffe400]
2: /usr/lib/xorg/modules/drivers//intel_drv.so(I830Sync+0x4e) [0xb732eefe]
3: /usr/lib/xorg/modules/drivers//intel_drv.so [0xb733d916]
4: X(AbortDDX+0x8d) [0x80a146d]
5: X(AbortServer+0x28) [0x81b3ae8]
6: X(FatalError+0x66) [0x81b4066]
7: /usr/lib/xorg/modules/drivers//intel_drv.so [0xb733e626]
8: /usr/lib/xorg/modules/drivers//intel_drv.so [0xb733f962]
9: X(AddScreen+0x1fc) [0x806d42c]
10: X(InitOutput+0x21e) [0x80a1b7e]
11: X(main+0x296) [0x806dbb6]
12: /lib/libc.so.6(__libc_start_main+0xe0) [0xb7552390]
13: X(FontFileCompleteXLFD+0x20d) [0x806d121]

FatalError re-entered, aborting
Caught signal 11.  Server aborting

I suspect the error handling in this version of intel_drv is incomplete,
resulting in segfaults instead of plain error reporting.

Willy


  reply	other threads:[~2012-10-06  9:17 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
2012-10-06  9:17                 ` Willy Tarreau [this message]
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=20121006091708.GC22618@1wt.eu \
    --to=w@1wt.eu \
    --cc=airlied@gmail.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.