From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: Stephan von Krawczynski <skraw@ithnet.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: adam@os.inf.tu-dresden.de, fernando@quatro.com.br,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.18-rcx: Dual P3 + VIA + APIC
Date: Sun, 24 Feb 2002 08:42:52 -0800 [thread overview]
Message-ID: <58726664.1014540170@[10.10.2.3]> (raw)
In-Reply-To: <20020223231850.4ea9d3ca.skraw@ithnet.com>
In-Reply-To: <20020223231850.4ea9d3ca.skraw@ithnet.com>
>> > <4>CPU1<T0:1339376,T1:446448,D:8,S:446460,C:1339380>
>> > <4>checking TSC synchronization across CPUs: passed.
>> > <4>Waiting on wait_init_idle (map = 0x2)
>> > <4>All processors have done init_idle
>> >
>> > I would say this means the TSC skew fix is broken and shooting down
>> > your box. What do you think, Alan?
>>
>> Seems a reasonable guess. However that TSC skew itself may point to other
>> problems. It means one processor started running successfully a little
>> after the other. That might be normal behaviour for that board or might
>> point to something else
>
> It seems no normal behaviour, I checked several other boards of this type
> and none had a TSC skew (and all work). Purely guessing I would suggest
> two try some other 2 processors to verify the behaviour is really
> processor-independent. Another guess would of course be the MB itself
> being broken to some extent.
>
> Has anybody ever seen a _working_ skew correction? Is this known-to-work
> code?
Yes. Works every time for me (on NUMA-Q), with huge corrections:
checking TSC synchronization across CPUs:
BIOS BUG: CPU#0 improperly initialized, has 6571 usecs TSC skew! FIXED.
BIOS BUG: CPU#1 improperly initialized, has 6571 usecs TSC skew! FIXED.
BIOS BUG: CPU#2 improperly initialized, has 6571 usecs TSC skew! FIXED.
BIOS BUG: CPU#3 improperly initialized, has 6571 usecs TSC skew! FIXED.
BIOS BUG: CPU#4 improperly initialized, has 20664 usecs TSC skew! FIXED.
BIOS BUG: CPU#5 improperly initialized, has 20664 usecs TSC skew! FIXED.
BIOS BUG: CPU#6 improperly initialized, has 20665 usecs TSC skew! FIXED.
BIOS BUG: CPU#7 improperly initialized, has 20664 usecs TSC skew! FIXED.
BIOS BUG: CPU#8 improperly initialized, has -4424 usecs TSC skew! FIXED.
BIOS BUG: CPU#9 improperly initialized, has -4424 usecs TSC skew! FIXED.
BIOS BUG: CPU#10 improperly initialized, has -4424 usecs TSC skew! FIXED.
BIOS BUG: CPU#11 improperly initialized, has -4424 usecs TSC skew! FIXED.
BIOS BUG: CPU#12 improperly initialized, has -22812 usecs TSC skew! FIXED.
BIOS BUG: CPU#13 improperly initialized, has -22812 usecs TSC skew! FIXED.
BIOS BUG: CPU#14 improperly initialized, has -22812 usecs TSC skew! FIXED.
BIOS BUG: CPU#15 improperly initialized, has -22811 usecs TSC skew! FIXED.
I did try disabling it once, which stopped the system booting.
I never looked at it any further.
If you are crashing near the wait_init_idle fix, you might
try Ingo's scheduler patch - it has a different way of
fixing this race condition.
M.
next prev parent reply other threads:[~2002-02-24 17:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-20 10:41 Adam Lackorzynski
2002-02-20 15:24 ` Alan Cox
2002-02-20 15:40 ` Adam Lackorzynski
2002-02-21 17:58 ` Fernando Korndorfer
2002-02-21 20:11 ` Stephan von Krawczynski
2002-02-22 13:02 ` Adam Lackorzynski
2002-02-22 13:11 ` Stephan von Krawczynski
2002-02-22 13:54 ` Fernando Korndorfer
2002-02-22 16:45 ` Adam Lackorzynski
2002-02-22 17:04 ` Stephan von Krawczynski
2002-02-22 18:20 ` Adam Lackorzynski
2002-02-23 16:38 ` Stephan von Krawczynski
2002-02-23 17:22 ` Alan Cox
2002-02-23 22:18 ` Stephan von Krawczynski
2002-02-24 16:42 ` Martin J. Bligh [this message]
2002-02-25 13:19 ` Adam Lackorzynski
2002-02-25 15:32 ` Martin J. Bligh
2002-02-25 16:17 ` Adam Lackorzynski
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='58726664.1014540170@[10.10.2.3]' \
--to=martin.bligh@us.ibm.com \
--cc=adam@os.inf.tu-dresden.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=fernando@quatro.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=skraw@ithnet.com \
/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®