linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maciej Zenczykowski <maze@cela.pl>
To: Julien Oster <lkml-20031111@mc.frodoid.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: A7N8X (Deluxe) Madness
Date: Tue, 11 Nov 2003 21:25:55 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.44.0311112120450.30654-100000@gaia.cela.pl> (raw)
In-Reply-To: <frodoid.frodo.87n0b2zmk1.fsf@usenet.frodoid.org>

> > I'd guess one is locking up due to hard disk load,
> > and the other is locking up due to automatic suspend/standby issues.
> > Can you verify that the ac kernel isn't locking up due to a 'screensaver' 
> > type problem?
> 
> Interesting question. I also thought about that one. However,
> regarding X, the machine sometimes crashes before the X Server
> screensaver (nothing special there, just the built in one that turns
> the screen black) is clearing the screen and sometimes afterwards. If
> it crashes afterwards, I can of course not see when it crashed, since
> I don't see the clock on the screen anymore.
> 
> And there's nothing else which I could think of. I have resetted the
> spinout time for the harddisks to "never" (for different reasons) and
> I don't think that there's any power saving stuff enabled in BIOS
> setup. I'll check that. However, I'm afraid there really isn't any
> screensaver or powersaving thing within my system, of course for the
> standard X screensaver, which doesn't seem related to it.

Indeed however I didn't mean the X server xscreensaver and family - I 
meant the BIOS DPMS, kernel console saver, etc functionality.  I had this 
kind of problem with my stationary computer (it locked solid when the 
screen was blanked) with some older kernel version (around 2.4.9).  I 
think kernel screen saveing can be turned off with some sort of escape 
code...

indeed:
$ man console_codes
  /timeout
gives:
  ESC [ 9 ; n ] where n is screen blank timeout in minutes
  ESC [ 13 ] to unblank
  ESC [ 14 ; n ] to set the VESA powerdown interval in minutes
so try something like
  echo -e "\e[13]\e[9;10080]\e[14;10080]"
to make it blank after a week and see if it still locks.
You can also try turning of VESA/DPMS blanking in the Bios.

Cheers,
MaZe.



  reply	other threads:[~2003-11-11 20:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-11 19:47 A7N8X (Deluxe) Madness Julien Oster
2003-11-11 19:55 ` Maciej Zenczykowski
2003-11-11 20:18   ` Julien Oster
2003-11-11 20:25     ` Maciej Zenczykowski [this message]
2003-11-11 20:09 ` Erik Andersen
2003-11-11 20:24   ` Julien Oster
2003-11-11 21:09     ` Erik Andersen
2003-11-11 21:31       ` Julien Oster
2003-11-12  2:55 ` Josh McKinney

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=Pine.LNX.4.44.0311112120450.30654-100000@gaia.cela.pl \
    --to=maze@cela.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml-20031111@mc.frodoid.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).