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]

Date:	Mon, 7 Apr 2008 15:55:27 -0700
From:	"Ray Lee" <ray-lk@...rabbit.org>
To:	"Tilman Schmidt" <tilman@...p.cc>
Cc:	"Dave Airlie" <airlied@...il.com>, linux-kernel@...r.kernel.org,
	pavel@....cz
Subject: Re: [2.6.25-rc6] possible regression: X server dying

On Mon, Apr 7, 2008 at 3:22 PM, Tilman Schmidt <tilman@...p.cc> wrote:
> This is still quite elusive. It only happens once every couple of days,
>  and the only thing that seems to be clear is that it's triggered by a GL
>  screensaver. So if it's ok I'll continue sharing X crash backtraces
>  while I go on groping for a lead. Here's my next one, this time with
>  kernel 2.6.25-rc8:
>
>
>  0: /usr/bin/X(xf86SigHandler+0x81) [0x80e6d81]
>  1: [0xb7f22400]
>  2:
>  /usr/lib/xorg/modules//extensions/libGLcore.so(_mesa_set_enable+0x1343)
>  [0xb50aa673]
>  3: /usr/lib/xorg/modules//extensions/libGLcore.so(_mesa_Disable+0x5a)
>  [0xb50abc1a]
>  4: /usr/lib/xorg/modules//extensions/libglx.so [0xb7ba8b98]
>  5: /usr/lib/xorg/modules//extensions/libglx.so(DoRender+0xdd) [0xb7ba145d]
>  6: /usr/lib/xorg/modules//extensions/libglx.so [0xb7ba157c]
>  7: /usr/lib/xorg/modules//extensions/libglx.so [0xb7ba5a6d]
>  8: /usr/bin/X [0x815809e]
>
> 9: /usr/bin/X(Dispatch+0x1af) [0x808f68f]
>  10: /usr/bin/X(main+0x47e) [0x807717e]
>  11: /lib/libc.so.6(__libc_start_main+0xe0) [0xb7cb6fe0]
>  12: /usr/bin/X(FontFileCompleteXLFD+0x1e5) [0x8076501]
>
>  As for Pavel's suggestion of disabling heap randomization, given the
>  current crash rate I'd have to try that for several weeks before I could
>  be reasonably sure that it helped. I think it'll be more useful if I go
>  on looking for a way to reproduce the crash more reliably. Perhaps I
>  should start playing some GL based games. :-)

If you think it's one of the screensavers but don't know which one,
then open up a bash shell and do a

for i in /usr/lib/xscreensaver/*; do echo $i; $i ; done

hitting control-c to break out of the screensaver when you think it's
been cleared of any wrongdoing. They'll default to rendering in a
window rather than the root window, but perhaps that'll be good enough
to hit the bug (it also lets you see the name of the screensaver it
just ran).
--
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/