From: mikpe@csd.uu.se
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.2[01] i386 does not reenable local apic
Date: Wed, 4 Jun 2003 12:53:59 +0200 [thread overview]
Message-ID: <16093.53191.406196.811094@gargle.gargle.HOWL> (raw)
In-Reply-To: <1648.1054702960@kao2.melbourne.sgi.com>
Keith Owens writes:
> arc/i386/kernel/apic.c::detect_init_APIC()
>
> switch (boot_cpu_data.x86_vendor) {
> case X86_VENDOR_AMD:
> if (boot_cpu_data.x86 == 6 && boot_cpu_data.x86_model > 1)
> break;
> if (boot_cpu_data.x86 == 15 && cpu_has_apic)
> break;
> goto no_apic;
> case X86_VENDOR_INTEL:
> if (boot_cpu_data.x86 == 6 ||
> (boot_cpu_data.x86 == 15 && cpu_has_apic) ||
> (boot_cpu_data.x86 == 5 && cpu_has_apic))
> break;
> goto no_apic;
> default:
> goto no_apic;
> }
>
> if (!cpu_has_apic) {
> /*
> * Some BIOSes disable the local APIC in the
> * APIC_BASE MSR. This can only be done in
> * software for Intel P6 and AMD K7 (Model > 1).
> */
> rdmsr(MSR_IA32_APICBASE, l, h);
> if (!(l & MSR_IA32_APICBASE_ENABLE)) {
> printk("Local APIC disabled by BIOS -- reenabling.\n");
> l &= ~MSR_IA32_APICBASE_BASE;
> l |= MSR_IA32_APICBASE_ENABLE | APIC_DEFAULT_PHYS_BASE;
> wrmsr(MSR_IA32_APICBASE, l, h);
> }
> }
>
> Because boot_cpu_data.x86 == 15 and the local APIC is disabled in BIOS,
> detect_init_APIC() skips the code that reenables the local APIC. This
> test is back to front. Change the code to force X86_VENDOR_INTEL to
> drop through and it successfully reenables the local apic, I even get
> NMI events.
The correct fix is to delete the "&& cpu_has_apic" test for family 15
CPUs. Simply falling through for VENDOR_INTEL will oops UP P5s.
I've seen a few P4 owners being caught by this. OTOH, several of those
had crap BIOSen that caused hangs with local APIC enabled.
I'll do a patch for 2.4.22-pre, if we ever actually get a 2.4.21 final...
/Mikael
prev parent reply other threads:[~2003-06-04 10:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-04 5:02 Keith Owens
2003-06-04 10:53 ` mikpe [this message]
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=16093.53191.406196.811094@gargle.gargle.HOWL \
--to=mikpe@csd.uu.se \
--cc=kaos@ocs.com.au \
--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
all inboxes | Powered by JetHome®