From: Mikael Pettersson <mikpe@csd.uu.se>
To: chris@jakdaw.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: P4/i845 Strange clock drifting
Date: Fri, 5 Apr 2002 19:52:00 +0200 (MET DST) [thread overview]
Message-ID: <200204051752.TAA02715@harpo.it.uu.se> (raw)
On Fri, 5 Apr 2002 13:28:10 +0100, Chris Wilson wrote:
>I've now tried a couple more kernels to no avail - nothing can find APICs.
>Is it even possible for a P4 to not have a local APIC? System is a
>supermicro 5012B*.
>
>/proc/cpuinfo shows:
>
>flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm
>
>(notice no "apic"). Is this normal/correct? If just just removed the check
>from apic.c and tried to enable the apic anyway then are bad things going
>to happen?
Your P4 does contain a local APIC, but your BIOS chose to disable it.
The following patch should (re)enable it:
--- linux-2.5.7/arch/i386/kernel/apic.c.~1~ Sat Mar 9 12:53:12 2002
+++ linux-2.5.7/arch/i386/kernel/apic.c Fri Apr 5 19:35:14 2002
@@ -603,7 +603,7 @@
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 == 15 ||
(boot_cpu_data.x86 == 5 && cpu_has_apic))
break;
goto no_apic;
@@ -615,7 +615,7 @@
/*
* 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).
+ * software for Intel P6/P4 and AMD K7 (Model > 1).
*/
rdmsr(MSR_IA32_APICBASE, l, h);
if (!(l & MSR_IA32_APICBASE_ENABLE)) {
This should work (and is known to work on many P6 and K7 boards),
but your BIOS may have problems with the local APIC.
- does apm --suspend work? does the resume afterwards work?
- if you run something compute-intensive for a while, does it
continue working ok or does it hang suddenly?
If your box remained stable, great!
If it experienced problems like unexpected hangs, then we'll need to
prevent the local APIC from being enabled on this mainboard.
In this case, please apply the patch below, reconfigure without
local APIC support, rebuild and send me (not the list) the DMI strings
printed during boot -- or the entire boot log if you're not certain
which parts are the DMI strings.
/Mikael
--- linux-2.5.7/arch/i386/kernel/dmi_scan.c.~1~ Tue Mar 19 01:10:03 2002
+++ linux-2.5.7/arch/i386/kernel/dmi_scan.c Fri Apr 5 19:35:33 2002
@@ -21,8 +21,8 @@
u16 handle;
};
-#define dmi_printk(x)
-//#define dmi_printk(x) printk x
+//#define dmi_printk(x)
+#define dmi_printk(x) printk x
static char * __init dmi_string(struct dmi_header *dm, u8 s)
{
next reply other threads:[~2002-04-05 17:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-05 17:52 Mikael Pettersson [this message]
2002-04-08 13:49 ` Chris Wilson
2002-04-09 9:33 ` Chris Wilson
-- strict thread matches above, loose matches on Subject: below --
2002-04-03 14:52 "Fernández-Victorio Arévalo, Gonzalo"
2002-04-03 14:10 Chris Wilson
2002-04-03 14:17 ` Zwane Mwaikambo
2002-04-05 12:28 ` Chris Wilson
2002-04-05 14:31 ` Zwane Mwaikambo
2002-04-05 15:01 ` Chris Wilson
2002-04-05 16:40 ` Maciej W. Rozycki
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=200204051752.TAA02715@harpo.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=chris@jakdaw.org \
--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®