MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16082.24332.881881.965677@gargle.gargle.HOWL>
Date: Mon, 26 May 2003 20:38:04 +0200
From: mikpe@csd.uu.se
To: Disconnect <lkml@sigkill.net>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: APIC on Dell Laptops - WAS: Re: [RFC] Fix NMI watchdog
	documentation
In-Reply-To: <1053967225.5948.12.camel@slappy>
References: <200305260921.h4Q9LcNr022536@harpo.it.uu.se>
	<1053967225.5948.12.camel@slappy>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1423
Lines: 34

Disconnect writes:
 > Local APIC disabled by BIOS -- reenabling.
 > Found and enabled local APIC!
 > 
 > And now /proc/cpuinfo and cpuid both show APIC support.
 > 
 > Removed/replaced power, triggered lid-switch/battery-status/etc with no
 > issues.  (The only thing that caused trouble was Fn-F10, the "eject cd"
 > button.  Never tried it under Linux before, and the cd isn't in it at
 > the moment anyway, so I'm betting thats unrelated. But it did cause a
 > lockup that even sysrq couldn't recover.)

Nice.

 > Not 100% clear on what the APIC does, but I'm not sure its doing it ;) 
 > 
 > PCI: Using ACPI for IRQ routing <-- shouldn't this be missing if the
 > APIC is in use?

Nope. local APIC != I/O APIC. Disable ACPI, or enable IO_APIC (and hope it's there).

 > (Full dmesg attached, for those who are curious - the unknown-scancode
 > is for the various laptop buttons - bright/dim, vol, media, battery,
 > etc.  Except for the volume buttons the only ones that work are the ones
 > that directly hit the hardware, ala bright/dim.)
 > 
 > Also, for others with an I8500 who might read the dmesg log, don't get

dmidecode data would be nice, for the whitelist rules.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/