public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Steinmetz <ast@domdv.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
	<jdamery@chiark.greenend.org.uk (Jonathan D. Amery)>
Subject: Re: VT82C686 && APM deadlock bug?
Date: Wed, 12 Dec 2001 18:11:45 +0100 (CET)	[thread overview]
Message-ID: <XFMail.20011212181145.ast@domdv.de> (raw)
In-Reply-To: <E16ECul-0001kf-00@the-village.bc.nu>


On 12-Dec-2001 Alan Cox wrote:
>> going wrong during (apm?) screen blanking when there is interrupt activity.
>> Unfortunately the system is frozen solid so there's no chance for any debug
>> trace. It would be nice if someone with detail knowledge of the blanking
>> code
>> could have a look.
> 
> APM power management code is buried in the BIOS. We ask the APM bios nicely
> to blank the display and power manage it. If the APM bios does something
> daft we can't do much about it.
> 
> You can turn apm support off in your XFree86 config and see if that helps
> 
At least in my case this wasn't exactly apm related. It happened too with apm
blanking disabled and only screen blanking without apm blanking occuring.
Preventing screen blanking completely by issuing echo -e "\033[9;0]" prevented
the freeze from happening so I do believe it's not the apm blanking code but
the general console blanking code where the problem occurs (no X, no fb, plain
80x25).


Andreas Steinmetz
D.O.M. Datenverarbeitung GmbH

  reply	other threads:[~2001-12-12 17:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-12 16:37 VT82C686 && APM deadlock bug? Jonathan D. Amery
2001-12-12 16:50 ` Andreas Steinmetz
2001-12-12 17:11   ` Alan Cox
2001-12-12 17:11     ` Andreas Steinmetz [this message]
2001-12-13 11:32 ` Markus Hetzmannseder
2001-12-13 23:26   ` Jonathan D. Amery
2001-12-14  0:02 ` brian

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=XFMail.20011212181145.ast@domdv.de \
    --to=ast@domdv.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.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