linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tilman Schmidt <tilman@imap.cc>
To: Ray Lee <ray-lk@madrabbit.org>
Cc: Dave Airlie <airlied@gmail.com>,
	linux-kernel@vger.kernel.org, pavel@ucw.cz
Subject: Re: [2.6.25-rc6] possible regression: X server dying
Date: Wed, 09 Apr 2008 13:57:41 +0200	[thread overview]
Message-ID: <47FCAF35.4000500@imap.cc> (raw)
In-Reply-To: <2c0942db0804071555w2dc2e43fw7cce64d4a5ba004@mail.gmail.com>

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

Ray Lee schrieb:
> 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.

Good idea. I did one pass through the screensavers that way, letting
each one run a couple of seconds until it seemed to become repetitive.
None of this crashed my X server, which at least seems to tell me that
it is not one particular screensaver always triggering the problem.

But: twice during that test I was called away, left the thing running,
and came back to find the X server had exited again, apparently after
the "real" screensaver had kicked in. Twice in a day, that's much more
than ever before. So you may have found me a way to trigger the crash
with greater probability.

Thanks,
T.

-- 
Tilman Schmidt                    E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)


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

  reply	other threads:[~2008-04-09 11:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-24 22:38 [2.6.25-rc6] possible regression: X server dying 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           ` [2.6.25-rc6] possible regression: X server dying Tilman Schmidt
2008-04-07 22:55             ` Ray Lee
2008-04-09 11:57               ` Tilman Schmidt [this message]
2008-04-14  1:02               ` Tilman Schmidt
  -- strict thread matches above, loose matches on Subject: below --
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=47FCAF35.4000500@imap.cc \
    --to=tilman@imap.cc \
    --cc=airlied@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=ray-lk@madrabbit.org \
    /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;
as well as URLs for NNTP newsgroup(s).