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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <21d7e9970803302153s314d48d3o7120a56092eeaede@mail.gmail.com>
Date:	Mon, 31 Mar 2008 14:53:29 +1000
From:	"Dave Airlie" <airlied@...il.com>
To:	"Tilman Schmidt" <tilman@...p.cc>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [2.6.25-rc6] possible regression: X server dying

On Tue, Mar 25, 2008 at 10:53 AM, Dave Airlie <airlied@...il.com> wrote:
>
> On Tue, Mar 25, 2008 at 9:45 AM, Tilman Schmidt <tilman@...p.cc> wrote:
>  > On Tue, 25 Mar 2008 09:22:32 +1000, Dave Airlie wrote:
>  >  > On Tue, Mar 25, 2008 at 8:38 AM, Tilman Schmidt <tilman@...p.cc> wrote:
>  >  >> In the five days since I booted a 2.6.25-rc6 kernel on my development
>  >  >>  machine, it has happened three times already that I came back to the
>  >  >>  machine to find that the X server had exited, killing all applications
>  >  >>  that still had a window open. [...]
>  >
>  > >
>  >  > anything in the X.org logfiles?
>  >
>  >  Ah, of course. Sorry I forgot. Xorg.0.log.old ends with this:
>  >
>  >  | 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?

it certainly looks like some heap or address space change affects Mesa.

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