From: Roland Scheidegger <rscheidegger_lists@hispeed.ch>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/tsc: RFC: re-synchronize TSCs to boot cpu TSC
Date: Fri, 9 Dec 2016 17:46:26 +0100 [thread overview]
Message-ID: <38f3ca77-ce32-d180-106a-e7242c635394@hispeed.ch> (raw)
In-Reply-To: <alpine.DEB.2.20.1612090953570.3794@nanos>
Am 09.12.2016 um 10:59 schrieb Thomas Gleixner:
> On Fri, 9 Dec 2016, Roland Scheidegger wrote:
>>
>> I saw some system lockups though:
>> When doing a cold boot, this kernel never managed to boot up. The last
>> message seen is:
>> x86: Booting SMP configuration:
>> .... node #0, CPUs: #1
>
> Weird. That really would be interesting to figure out what goes wrong
> there. What bothers me is that we don't see something like this:
>
>> [ 0.172334] TSC ADJUST differs: Reference CPU0: -577421768610 CPU1:
>> -577423766270
>
> Can you please apply the debug patch below and provide the output ?
Ok, this is the output (minus some typos maybe...):
x86: Booting SMP configuration:
.... node #0, CPUs: #1
TSC ADJUST: CPU1: -2806491604
TSC source sync 0 -> 1 runs 3
TSC ADJUST differs: Reference CPU0: -2805503200 CPU1: -2806491604
TSC ADJUST synchronize: Reference CPU0: -2805503200 CPU1: -2806491604
TSC target sync skip
TSC source sync skipped
And that's it.
>
>
>> [ 0.094492] x86: Booting SMP configuration:
>> [ 0.094534] .... node #0, CPUs: #1
>> [ 0.172334] TSC ADJUST differs: Reference CPU0: -577421768610 CPU1:
>> -577423766270
>
> What on earth is this BIOS doing? That's a couple of minutes back in time.
Looks like that's only after a reset, after a cold boot the numbers are
significantly smaller (1 sec or so?). Though the difference between
these two is nearly a million cycles too, so might be similar between
min and max for all.
>
> And the difference between the max and min adjust value is 2050932 cycles.
>
>> Without the patches on cold boot it just was as expected:
>> [ 0.093700] x86: Booting SMP configuration:
>> [ 0.093737] .... node #0, CPUs: #1
>> [ 0.174304] TSC synchronization [CPU#0 -> CPU#1]:
>> [ 0.174375] Measured 1837188 cycles TSC warp between CPUs, turning
>> off TSC clock.
>
> Not surprising given the above numbers.
>
Hope that helps,
Roland
next prev parent reply other threads:[~2016-12-09 16:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1481179042-968-1-git-send-email-sroland@vmware.com>
2016-12-08 7:56 ` Thomas Gleixner
[not found] ` <6194ea73-99dd-ceca-6f8d-e945ca717c75@hispeed.ch>
2016-12-09 9:59 ` Thomas Gleixner
2016-12-09 16:46 ` Roland Scheidegger [this message]
2016-12-09 17:33 ` Thomas Gleixner
2016-12-09 20:50 ` Roland Scheidegger
2016-12-09 22:59 ` Thomas Gleixner
2016-12-10 1:55 ` Roland Scheidegger
2016-12-10 5:20 ` Roland Scheidegger
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=38f3ca77-ce32-d180-106a-e7242c635394@hispeed.ch \
--to=rscheidegger_lists@hispeed.ch \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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®