Re: [2.6.25-rc6] possible regression: X server dying

[Dave Airlie]

On Tue, Apr 1, 2008 at 7:02 PM, Tilman Schmidt <tilman@xxxxxxx> wrote:
> On Mon, 31 Mar 2008 14:53:29 +1000, Dave Airlie wrote:
>
> > On Tue, Mar 25, 2008 at 10:53 AM, Dave Airlie <airlied@xxxxxxxxx> wrote:
> >
> > >
> > > On Tue, Mar 25, 2008 at 9:45 AM, Tilman Schmidt <tilman@xxxxxxx> wrote:
> > >
> >
>  [...]
>
>
> >
> > >  >  | Backtrace:
> > >  >  | 0: /usr/bin/X(xf86SigHandler+0x81) [0x80e6d81]
> > >  >  | 1: [0xb7fc9400]
> > >  >  | 2:
> /usr/lib/xorg/modules//extensions/libGLcore.so(_swrast_Triangle+0x2d)
> [0xb51ea5dd]
> > >  >  | 3: /usr/lib/xorg/modules//extensions/libGLcore.so [0xb51f1075]
> > >  >  | 4: /usr/lib/xorg/modules//extensions/libGLcore.so [0xb5206f2e]
> > >  >  | 5: /usr/lib/xorg/modules//extensions/libGLcore.so [0xb52080b8]
> > >  >  | 6:
> /usr/lib/xorg/modules//extensions/libGLcore.so(_tnl_run_pipeline+0x153)
> [0xb520cb83]
> > >  >  | 7:
> /usr/lib/xorg/modules//extensions/libGLcore.so(_tnl_draw_prims+0x3f0)
> [0xb51f8340]
> > >  >  | 8:
> /usr/lib/xorg/modules//extensions/libGLcore.so(vbo_exec_vtx_flush+0x1fb)
> [0xb52471eb]
> > >  >  | 9:
> /usr/lib/xorg/modules//extensions/libGLcore.so(vbo_exec_FlushVertices+0x78)
> [0xb52488e8]
> > >  >  | 10:
> /usr/lib/xorg/modules//extensions/libGLcore.so(_mesa_Flush+0x83)
> [0xb5112663]
> > >  >  | 11: /usr/lib/xorg/modules//extensions/libglx.so [0xb7c6a107]
> > >  >  | 12: /usr/lib/xorg/modules//extensions/libglx.so [0xb7c4aa6d]
> > >  >  | 13: /usr/bin/X [0x815809e]
> > >  >  | 14: /usr/bin/X(Dispatch+0x1af) [0x808f68f]
> > >  >  | 15: /usr/bin/X(main+0x47e) [0x807717e]
> > >  >  | 16: /lib/libc.so.6(__libc_start_main+0xe0) [0xb7d5dfe0]
> > >  >  | 17: /usr/bin/X(FontFileCompleteXLFD+0x1e5) [0x8076501]
> > >  >  |
> > >  >  | Fatal server error:
> > >  >  | Caught signal 11.  Server aborting
> > >
> >
> > any look finding what might have caused this?
> >
>
>  Not really. It's obviously triggered by the screensaver. The machine
>  runs SuSE's default: gnome-screensaver with mode = random and a list
>  of 189 candidate screensavers, so I can't tell which one(s) of those
>  actually triggers the problem.
>
>  But perhaps that doesn't matter anyway. I recently collected another
>  X backtrace with kernel 2.6.25-rc7 which looks quite different in
>  the libglx section:
>
>
>  0: /usr/bin/X(xf86SigHandler+0x81) [0x80e6d81]
>  1: [0xb7ef7400]
>  2: /usr/lib/xorg/modules//extensions/libglx.so [0xb7b7d8e8]
>  3: /usr/lib/xorg/modules//extensions/libglx.so(DoRender+0xdd) [0xb7b7645d]
>  4: /usr/lib/xorg/modules//extensions/libglx.so [0xb7b7657c]
>  5: /usr/lib/xorg/modules//extensions/libglx.so [0xb7b7aa6d]
>  6: /usr/bin/X [0x815809e]
>
>  7: /usr/bin/X(Dispatch+0x1af) [0x808f68f]
>  8: /usr/bin/X(main+0x47e) [0x807717e]
>  9: /lib/libc.so.6(__libc_start_main+0xe0) [0xb7c8bfe0]
>  10: /usr/bin/X(FontFileCompleteXLFD+0x1e5) [0x8076501]
>
>  But I know next to nothing about GL, so I'm out of my depth there.
>  I'd welcome any suggestions on how to provoke the crash more
>  regularly so that I could attempt to bisect.

Its one of the GL screensavers, not sure how to narrow it down, use
ldd to figure out which ones are using GL.

I've no idea how the kernel is influencing this.

Dave.
--
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/