mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tilman Schmidt <tilman@imap.cc>
To: Dave Airlie <airlied@gmail.com>
Cc: linux-kernel@vger.kernel.org, pavel@ucw.cz
Subject: Re: [2.6.25-rc6] possible regression: X server dying
Date: Tue, 08 Apr 2008 00:22:58 +0200	[thread overview]
Message-ID: <47FA9EC2.6030801@imap.cc> (raw)
In-Reply-To: <47F1FA3F.3010206@imap.cc>

[-- Attachment #1: Type: text/plain, Size: 1414 bytes --]

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. :-)

Hope this helps (slim chance, I know)
T.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]

  parent reply	other threads:[~2008-04-07 22:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-24 22:38 Tilman Schmidt
2008-03-24 23:22 ` Dave Airlie
2008-03-24 23:45   ` Tilman Schmidt
2008-03-25  0:53     ` Dave Airlie
2008-03-26 18:52       ` Pavel Machek
2008-03-31  4:53       ` Dave Airlie
2008-03-31 17:45         ` Mark Lord
2008-04-01  9:02         ` Tilman Schmidt
2008-04-06  7:44           ` Dave Airlie
2008-04-06 14:34             ` Gerhard Pircher
2008-04-07 22:27               ` Dave Airlie
2008-04-08 21:01                 ` Guennadi Liakhovetski
2008-04-09  8:54                   ` Gerhard Pircher
2008-04-24 16:40                     ` Oliver Pinter
2008-04-24 20:37                       ` Gerhard Pircher
2008-04-24 16:03                   ` Guennadi Liakhovetski
2008-04-19 11:30             ` [2.6.25] X server dying due to lock not being held Gerhard Pircher
2008-04-07 22:22           ` Tilman Schmidt [this message]
2008-04-07 22:55             ` [2.6.25-rc6] possible regression: X server dying Ray Lee
2008-04-09 11:57               ` Tilman Schmidt
2008-04-14  1:02               ` Tilman Schmidt
2008-04-03 22:49 2.6.25-rc8-git2: Reported regressions from 2.6.24 Rafael J. Wysocki
2008-04-03 23:22 ` [2.6.25-rc6] possible regression: X server dying Rafael J. Wysocki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47FA9EC2.6030801@imap.cc \
    --to=tilman@imap.cc \
    --cc=airlied@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome