All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: adam@os.inf.tu-dresden.de, fernando@quatro.com.br,
	linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: 2.4.18-rcx: Dual P3 + VIA + APIC
Date: Sat, 23 Feb 2002 23:18:50 +0100	[thread overview]
Message-ID: <20020223231850.4ea9d3ca.skraw@ithnet.com> (raw)
In-Reply-To: <E16efs1-0005cE-00@the-village.bc.nu>
In-Reply-To: <20020223173857.3db89749.skraw@ithnet.com> <E16efs1-0005cE-00@the-village.bc.nu>

On Sat, 23 Feb 2002 17:22:01 +0000 (GMT)
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

> > <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?

Regards,
Stephan


  reply	other threads:[~2002-02-23 22:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-20 10:41 2.4.18-rcx: Dual P3 + VIA + APIC 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 [this message]
2002-02-24 16:42                     ` Martin J. Bligh
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=20020223231850.4ea9d3ca.skraw@ithnet.com \
    --to=skraw@ithnet.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 \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.