From: linux@horizon.com
To: mikpe@user.it.uu.se
Cc: linux-kernel@vger.kernel.org
Subject: Re: Playing with 2.5.63: APM blanking and "bio too big"
Date: 1 Mar 2003 17:25:39 -0000 [thread overview]
Message-ID: <20030301172539.15346.qmail@science.horizon.com> (raw)
In-Reply-To: <200303011658.h21GwTwu027100@harpo.it.uu.se>
>>* I had real problems with APM screen blanking enabled. It reliably
>> and repeatedly locked the machine HARD (no keyboard, no SysRq, no ping)
>> when the scren blanker kicked in or trying to switch from X. This is
>> an Athlon on a KT133 Motherboard. No problems in 2.4. APM can corectly
>> power the machine off, however.
> Do you have CONFIG_X86_UP_APIC=y?
Right in one!
> To verify, hack apic.c and ensure that "dont_enable_local_apic_timer"
> is initialised to 1. Also don't enable the NMI watchdog.
I'll try that. Thanks!
> Another option, which is what I use now on all my local-APIC capable
> machines, is to disable APM_DISPLAY_BLANK.
What I'm running now, and now that I understand, probably preferable.
Maybe a warning in Configure.help?
--- arch/i386/Kconfig 2003-02-24 14:05:10.000000000 -0500
+++ arch/i386/Kconfig.new 2003-03-01 12:23:59.000000000 -0500
@@ -922,6 +922,10 @@
backlight at all, or it might print a lot of errors to the console,
especially if you are using gpm.
+ This also tends to interact badly with use of the local APIC.
+ You probably don't want this option unless you are building
+ for a laptop that you intend to use in text mode.
+
config APM_RTC_IS_GMT
bool "RTC stores time in GMT"
depends on APM
Or should Linux mask the APIC timer before making the APM call?
> I really despise BIOS writers.
The BIOS interface is... non-obvious.
next prev parent reply other threads:[~2003-03-01 17:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-01 16:58 Mikael Pettersson
2003-03-01 17:25 ` linux [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-01 14:14 linux
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=20030301172539.15346.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@user.it.uu.se \
/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
all inboxes | Powered by JetHome®