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
Date: Mon, 26 May 2003 20:38:04 +0200 [thread overview]
Message-ID: <16082.24332.881881.965677@gargle.gargle.HOWL> (raw)
In-Reply-To: <1053967225.5948.12.camel@slappy>
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.
next prev parent reply other threads:[~2003-05-26 18:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-26 9:21 mikpe
2003-05-26 16:40 ` APIC on Dell Laptops - WAS: " Disconnect
2003-05-26 18:38 ` mikpe [this message]
2003-05-26 19:44 ` Disconnect
2003-05-27 20:25 ` Disconnect
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=16082.24332.881881.965677@gargle.gargle.HOWL \
--to=mikpe@csd.uu.se \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@sigkill.net \
/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®