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 10:42:58 +0200 [thread overview]
Message-ID: <20121006084258.GB22618@1wt.eu> (raw)
In-Reply-To: <051c15$4i14fm@AZSMGA002.ch.intel.com>
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.
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/eeepc:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6
X.Org X Server 1.4.2
Release Date: 11 June 2008
X Protocol Version 11, Revision 0
Build Operating System: Slackware 12.1 Slackware Linux Project
Current Operating System: Linux eeepc 3.5.6-rc1+ #4 SMP Sat Oct 6 10:13:58 CEST 2012 i686
Build Date: 30 June 2008 11:35:29PM
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sat Oct 6 10:42:43 2012
(==) Using config file: "/etc/X11/xorg.conf"
(II) Module "ramdac" already built-in
(II) Module "ddc" already built-in
(II) Module "i2c" already built-in
(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]
3: /usr/lib/xorg/modules/drivers//intel_drv.so [0xb736de51]
4: X(AddScreen+0x1fc) [0x806d42c]
5: X(InitOutput+0x21e) [0x80a1b7e]
6: X(main+0x296) [0x806dbb6]
7: /lib/libc.so.6(__libc_start_main+0xe0) [0xb7581390]
8: X(FontFileCompleteXLFD+0x20d) [0x806d121]
Fatal server error:
Caught signal 11. Server aborting
giving up.
xinit: Connection reset by peer (errno 104): unable to connect to X server
xinit: No such process (errno 3): Server error.
Willy
next prev parent reply other threads:[~2012-10-06 8:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 23:42 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 [this message]
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=20121006084258.GB22618@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®