From: Disconnect <lkml@sigkill.net>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Fix NMI watchdog documentation
Date: 26 May 2003 01:31:41 -0400 [thread overview]
Message-ID: <1053927100.1291.7.camel@slappy> (raw)
In-Reply-To: <200305260236.h4Q2ala7003115@turing-police.cc.vt.edu>
On Sun, 2003-05-25 at 22:36, Valdis.Kletnieks@vt.edu wrote:
> On Sun, 25 May 2003 12:50:28 +0200, mikpe@csd.uu.se said:
>
> > The blacklist rule is a catch-all since we don't have detailed DMI
> > data on all Inspiron/Latitude models, and at the time, _all_ of them
> > were broken. Looking through my records, Inspiron 8000 and 8100, and
> > Latitude C600, C610, C640, C800, and C810 are known to be broken. Note
> > that this includes at least one P4-based machine (C640), so it's not
> > restricted to "old" mobile P3s.
>
> OK, I put together a kernel that had the Latitude blacklist commented out,
> and it comes up with:
>
> No local APIC present or hardware disabled
> Initializing CPU#0
>
> So add the Latitude C840 to the "known b0rken" list.
Ditto the Inspiron 8500 - no apic at all (which is different from
known-broken, since nothing bad happened.)
For cleanliness sake it would be nice to have specific model info in the
blacklist ("your hardware doesn't have a frobber" is nicer than "the
frobber on your hardware causes your pets to catch fire"), but since the
hardware doesn't exist anyway the end result is the same. (And the code
is a lot more readable.)
Perhaps just a comment above those entries:
/* Latitude C840 and Inspiron 8500 have no APIC support in hardware */
Eventually it might even turn into a proper whitelist/blacklist
collection.
--
Disconnect <lkml@sigkill.net>
next prev parent reply other threads:[~2003-05-26 5:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-25 10:50 [RFC] Fix NMI watchdog documentation mikpe
2003-05-26 2:36 ` Valdis.Kletnieks
2003-05-26 5:31 ` Disconnect [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-26 9:21 mikpe
2003-05-27 3:19 ` Valdis.Kletnieks
2003-05-25 10:49 mikpe
2003-05-24 19:07 Carl-Daniel Hailfinger
2003-05-24 19:08 ` Zwane Mwaikambo
2003-05-24 19:08 ` Zwane Mwaikambo
2003-05-24 19:11 ` 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
2003-05-24 19:12 ` Marc-Christian Petersen
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=1053927100.1291.7.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.