Re: 3.5 regression on i915

[Willy Tarreau]

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/