X server crash triggered by logstalgia

[Matt Zimmerman]

Binary package hint: xserver-xorg-video-intel

This is reproducible every time by running logstalgia, which is an OpenGL application. Running glxgears doesn't crash though.

Backtrace:
0: /usr/X11R6/bin/X(xf86SigHandler+0x65) [0x481005]
1: /lib/libc.so.6 [0x7f629e12d060]
2: /usr/lib/xorg/modules/extensions//libglx.so(__glXDeassociateContext+0x35) [0x7f629d6075e5]
3: /usr/lib/xorg/modules/extensions//libglx.so(__glXContextDestroy+0xf) [0x7f629d60395f]
4: /usr/lib/xorg/modules/extensions//libglx.so [0x7f629d60fb72]
5: /usr/lib/xorg/modules/extensions//libglx.so(__glXFreeContext+0x6c) [0x7f629d605b1c]
6: /usr/lib/xorg/modules/extensions//libglx.so [0x7f629d605b63]
7: /usr/X11R6/bin/X(FreeResourceByType+0x105) [0x435595]
8: /usr/lib/xorg/modules/extensions//libglx.so [0x7f629d60246e]
9: /usr/lib/xorg/modules/extensions//libglx.so [0x7f629d605e42]
10: /usr/X11R6/bin/X(Dispatch+0x364) [0x44d7a4]
11: /usr/X11R6/bin/X(main+0x45d) [0x43378d]
12: /lib/libc.so.6(__libc_start_main+0xe6) [0x7f629e118466]
13: /usr/X11R6/bin/X [0x432b69]

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 8.10
Package: xserver-xorg-video-intel 2:2.4.1-1ubuntu6
ProcEnviron:
 LC_COLLATE=C
 PATH=/home/username/bin:/usr/lib/ccache:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/sbin:/usr/sbin:/usr/games:/usr/lib/surfraw
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
ProcVersion: Linux version 2.6.27-5-generic (buildd@yellow) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu8) ) #1 SMP Fri Oct 3 00:36:38 UTC 2008

SourcePackage: xserver-xorg-video-intel
Uname: Linux 2.6.27-5-generic x86_64
xkbcomp:

[Bryce Harrington (bryce)]

I'll try reproducing this when I get a chance and see if we can get a more detailed backtrace.

(--) PCI:*(0@0:2:0) Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller rev 12, Mem @ 0xf8100000/1048576, 0xe0000000/268435456, I/O @ 0x00001800/8
(--) PCI: (0@0:2:1) Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller rev 12, Mem @ 0xf8200000/1048576

[Bryce Harrington (bryce)]

[This is an automatic notice.]

We'd like to forward your bug upstream, however upstream requires
that you first test it against their newer driver code.

To save you the effort of building the driver from source, we've built
packages for the driver and its new dependencies.

So you have a couple options:

 1. Download and test .debs for intrepid, from:
     https://edge.launchpad.net/~intel-gfx-testing/+archive

 -or-

 2. Download and test the Jaunty alpha-2 (or newer) Live CD,
     (which includes a beta of the new xserver 1.6 as well).
     See http://cdimage.ubuntu.com/releases/9.04/ for ISOs

Thanks ahead of time! You can simply reply to this email to report your
findings.

P.S., if you wish to forward your bug upstream yourself, please follow
these directions to do so:
  http://intellinuxgraphics.org/how_to_report_bug.html

[Matt Zimmerman (mdz)]

On Sat, Dec 20, 2008 at 02:26:51AM -0000, Bryce Harrington wrote:
>
> [This is an automatic notice.]
>
> We'd like to forward your bug upstream, however upstream requires
> that you first test it against their newer driver code.
>
> To save you the effort of building the driver from source, we've built
> packages for the driver and its new dependencies.
>
> So you have a couple options:
>
> 1. Download and test .debs for intrepid, from:
> https://edge.launchpad.net/~intel-gfx-testing/+archive
>
> -or-
>
> 2. Download and test the Jaunty alpha-2 (or newer) Live CD,
> (which includes a beta of the new xserver 1.6 as well).
> See http://cdimage.ubuntu.com/releases/9.04/ for ISOs
>
>
> Thanks ahead of time! You can simply reply to this email to report your
> findings.

I upgraded to Jaunty and retested with 2:2.5.1-1ubuntu7, and I'm unable to
reproduce the problem with that setup.

--
 - mdz

[Bryce Harrington (bryce)]

Excellent, thanks for testing and confirming the issue is no longer present in Jaunty. I'll close the issue as fixed. Since this is an issue with glx, it's likely the issue was fixed with the new mesa and/or xserver in Jaunty. If you have an idea which patch solved the issue and would like to have that investigated for Intrepid, please feel free to open a bug-task against Intrepid.