[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64N.0707311343410.16158@blysk.ds.pg.gda.pl>
Date: Tue, 31 Jul 2007 13:55:51 +0100 (BST)
From: "Maciej W. Rozycki" <macro@...ux-mips.org>
To: John Sigler <linux.kernel@...e.fr>
cc: linux-kernel@...r.kernel.org,
linux-rt-users <linux-rt-users@...r.kernel.org>
Subject: Re: BIOS implementors disabling the LAPIC
On Tue, 31 Jul 2007, John Sigler wrote:
> The motherboard manufacturer (well, their level 1 support, anyway) told me I
> could "safely enable the LAPIC". If it is safe to enable the LAPIC, then why
> are they disabling it in the BIOS? (They weren't able to tell me whether
> their BIOS triggers SMIs or not...)
Ask them.
> Is this a "either works or doesn't" situation where hell should break loose if
> I try to enable the LAPIC and it's not supported by the motherboard, or is
> this a "you will silently lose data at the worst possible time" situation?
It could be either. For example some IBM hardware used to be known to
have problems, like the 8254 timer freezing occasionally, when the APIC
was used and the NMI watchdog enabled. On some laptops you would get an
instant hard lockup if you enabled the APIC and used one of the special
key combinations (whether on purpose or by chance) used to adjust display
brightness, etc..
> If that were the case, then I could not enable the LAPIC and have NMIs work,
> right?
It depends on what you want to use NMIs for. For their PC/AT compatible
purpose, that is reporting of memory parity/ECC and bus errors, it works
in either mode. For any other purpose you need an APIC.
Maciej
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists