From: Disconnect <lkml@sigkill.net>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Fix NMI watchdog documentation
Date: 25 May 2003 01:52:16 -0400 [thread overview]
Message-ID: <1053841936.1177.5.camel@slappy> (raw)
In-Reply-To: <Pine.LNX.4.50.0305250102130.17353-100000@montezuma.mastecende.com>
On Sun, 2003-05-25 at 01:03, Zwane Mwaikambo wrote:
> On Sun, 25 May 2003 Valdis.Kletnieks@vt.edu wrote:
>
> > On Sat, 24 May 2003 23:36:26 EDT, Zwane Mwaikambo said:
> >
> > > > Dell Latitude with broken BIOS detected. Refusing to enable the local APIC.
> >
> > > It's known broken with that configuration and hence blacklisted.
> >
> > Yes, I know it's blacklisted. The question I intended to ask was "Is the
> > entire concept of IOAPIC irretrievably scrozzled on this machine, or is there
> > sufficient minimum functionality to get nmi_watchdog working?"
>
> You don't have an IOAPIC at all, but the Local APIC has been known to
> cause problems. So forget about nmi_watchdog.
>
> Zwane
I was reading that code the other day (just out of curiosity, believe it
or not) and I'm wondering how recently that has been tested - most of
the blacklist/oddness workarounds listed in dmi_scan.c are
model-specific, but the APIC entry is any Dell Inspiron or Latitude.
I'm going to remove the test tomorrow sometime and see what happens -
lots has changed since the Inspiron 8000, including a migration to
p4-mobile, so its worth seeing if the newer Dells are fixed. If so,
I'll submit a patch to make that more model-specific (probably I'll just
add a whitelist function - no_local_apic_kills_bios or some such; seems
better than listing every dell inspiron individually..)
I'm encouraged by the complete lack of APM or any of the 'enter bios
while running' options present on the older laptops; according to the
comments, even if the APIC kills the bios on entry/exit, it won't matter
since you can't trigger it to begin with..
--
Disconnect <lkml@sigkill.net>
next prev parent reply other threads:[~2003-05-25 5:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-24 19:07 [RFC] Fix NMI watchdog documentation Carl-Daniel Hailfinger
2003-05-24 19:08 ` Zwane Mwaikambo
2003-05-24 19:11 ` Zwane Mwaikambo
2003-05-24 19:43 ` Carl-Daniel Hailfinger
2003-05-25 3:29 ` Valdis.Kletnieks
2003-05-25 3:36 ` Zwane Mwaikambo
2003-05-25 4:48 ` Valdis.Kletnieks
2003-05-25 5:03 ` Zwane Mwaikambo
2003-05-25 5:52 ` Disconnect [this message]
2003-05-24 19:12 ` Marc-Christian Petersen
2003-05-25 10:49 mikpe
2003-05-25 10:50 mikpe
2003-05-26 2:36 ` Valdis.Kletnieks
2003-05-26 5:31 ` Disconnect
2003-05-26 9:21 mikpe
2003-05-27 3:19 ` Valdis.Kletnieks
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=1053841936.1177.5.camel@slappy \
--to=lkml@sigkill.net \
--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;
as well as URLs for NNTP newsgroup(s).