mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@kernel.org>
To: David Kostial <mail@david-kostial.de>, "x86@kernel.org" <x86@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] x86/tsc: ~1 second TSC skew when bringing a secondary CPU online on Ryzen 7 8840HS
Date: Mon, 17 Aug 2026 12:00:49 +0200	[thread overview]
Message-ID: <87mrulkqwe.ffs@fw13> (raw)
In-Reply-To: <2058267156.513331.1786817844981@mailbusiness.ionos.de>

On Sat, Aug 15 2026 at 20:17, David Kostial wrote:
>   smpboot: Booting Node 0 Processor 1 APIC 0x1
>   TSC synchronization [CPU#0 -> CPU#1]:
>   Measured 3360957369 cycles TSC warp between CPUs, turning off TSC clock.
>   tsc: Marking TSC unstable due to check_tsc_sync_source failed
>   TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'.
>   clocksource: Switched to clocksource hpet
....
> I'm not sure whether the root cause is firmware/AGESA or whether there
> is anything x86/tsc should handle differently here.

That's a firmware problem. The firmware messes up the TSC synchronization.

The kernel can't do anything about this as the CPU does not have the
TSC_ADJUST MSR.

We tried to write to the TSC MSR directly, but that turned out to be
fragile and unreliable so we restricted the fixup attempts to CPUs which
have the TSC_ADJUST MSR.

Thanks,

        tglx



      reply	other threads:[~2026-08-17 10:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-15 18:17 David Kostial
2026-08-17 10:00 ` Thomas Gleixner [this message]

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=87mrulkqwe.ffs@fw13 \
    --to=tglx@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mail@david-kostial.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®