From: William Lee Irwin III <wli@holomorphy.com>
To: linux-kernel@vger.kernel.org
Cc: mochel@osdl.org, hpa@zytor.com
Subject: NUMA-Q breakage 4/7 cpu_init() heisenbug
Date: Fri, 12 Jul 2002 15:39:56 -0700 [thread overview]
Message-ID: <20020712223956.GB25360@holomorphy.com> (raw)
cpu_init() (or something nearby) is broken and there is no clear way to
tell why. Adding printk's seems to make it go away. hpa seemed to have
a notion of what was going on around here.
Workaround below.
Cheers,
Bill
===== arch/i386/kernel/cpu/common.c 1.1 vs edited =====
--- 1.1/arch/i386/kernel/cpu/common.c Fri May 10 09:06:30 2002
+++ edited/arch/i386/kernel/cpu/common.c Thu Jul 11 22:09:41 2002
@@ -446,6 +446,8 @@
__asm__ __volatile__("lgdt %0": "=m" (gdt_descr));
__asm__ __volatile__("lidt %0": "=m" (idt_descr));
+ printk(KERN_INFO "Loading GDT/IDT for CPU#%d\n", nr);
+
/*
* Delete NT
*/
@@ -466,6 +468,8 @@
load_TR(nr);
load_LDT(&init_mm.context);
+ printk(KERN_INFO "Loaded per-cpu LDT/TSS for CPU#%d\n", nr);
+
/* Clear %fs and %gs. */
asm volatile ("xorl %eax, %eax; movl %eax, %fs; movl %eax, %gs");
@@ -483,4 +487,6 @@
clear_thread_flag(TIF_USEDFPU);
current->used_math = 0;
stts();
+
+ printk(KERN_INFO "Cleaned up FPU and debug regs for CPU#%d\n", nr);
}
reply other threads:[~2002-07-12 22:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020712223956.GB25360@holomorphy.com \
--to=wli@holomorphy.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.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®