From: Manfred Spraul <manfred@colorfullife.com>
To: Tommy Faasen <faasen@xs4all.nl>, linux-kernel@vger.kernel.org
Subject: Re: SMP debugging
Date: Thu, 11 Oct 2001 21:18:42 +0200 [thread overview]
Message-ID: <3BC5F092.6492A8B3@colorfullife.com> (raw)
> The way I look at the output is that the kernel only looks
> what the specs ofthe first cpu are and asumes that the second
> is the same.
Correct, that part of the Intel MP specification: if 2 different cpus
are
used, then the capabilities of the second cpu must be a subset of the
capabilities of the first cpu. (IIRC)
Probably you must edit smpboot.c or init.c and clear the capabilities of
cpu0 that cpu1 doesn't have.
> Invalid operand: 0000
> CPU: 0
> EIP: 0010:[<c010c784>] Not tainted
> EFLAGS: 00010206
Could you run the oops through ksymoops?
> processor 0:
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
> pse36 mmx fxsr
> processor 1:
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov mmx
Ok, cpu0 support fxsr, cpu1 doesn't.
fxsr is used for the thread switching.
It seems that this causes an oops during the first thread switch.
Could you try what happens if you replace
linux/include/asm-i386/processor.h:
- #define cpu_has_fxsr (test_bit(X86_FEATURE_FXSR,
boot_cpu_data.x86_capability))
+ #define cpu_has_fxsr (0)
If that doesn't work, then check where X86_FEATURE_FXSR is used.
--
Manfred
next reply other threads:[~2001-10-11 19:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-11 19:18 Manfred Spraul [this message]
2001-10-11 22:07 ` SMP debugging Tommy Faasen
-- strict thread matches above, loose matches on Subject: below --
2001-10-11 18:58 Tommy Faasen
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=3BC5F092.6492A8B3@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=faasen@xs4all.nl \
--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