From: Thomas Gleixner <tglx@linutronix.de>
To: Fab Stz <fabstz-it@yahoo.fr>, John Stultz <jstultz@google.com>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
Anna-Maria Behnsen <anna-maria@linutronix.de>,
Frederic Weisbecker <frederic@kernel.org>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
Jacob Pan <jacob.jun.pan@linux.intel.com>,
Len Brown <lenb@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>
Subject: Re: [REGRESSION] ? system is stuck in clocksource, >60s delay at boot time without tsc=unstable
Date: Tue, 25 Feb 2025 20:35:43 +0100 [thread overview]
Message-ID: <87eczlg6ls.ffs@tglx> (raw)
In-Reply-To: <5114de6a-e6ef-4459-9570-6dd2245fabd5@yahoo.fr>
On Tue, Feb 25 2025 at 09:11, Fab Stz wrote:
> Thank you for the patch! I built the 6.1 kernel with it applied and it
> apparently works as expected (no delay). Please find logs below &
> attached dmesg log. Maybe the interesting line is:
>
> Feb 25 08:53:51 debian kernel: tsc: Marking TSC unstable due to TSC
> halts in idle
Correct. That's the missing piece.
> Will the patch also enter the longterm releases like 6.1?
Let me write a proper change log with a Fixes tag and cc stable, so it
will be automatically picked up.
Thanks,
tglx
next prev parent reply other threads:[~2025-02-25 19:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <10cf96aa-1276-4bd4-8966-c890377030c3.ref@yahoo.fr>
2024-11-27 7:18 ` [REGRESSION] ? system is stuck in clocksource, >60s delay at boot time without tsc=unstable Fab Stz
2024-12-27 12:39 ` Fab Stz
2025-01-02 21:49 ` John Stultz
2025-01-02 21:56 ` John Stultz
2025-01-03 15:38 ` Fab Stz
2025-01-03 19:02 ` John Stultz
2025-01-04 22:02 ` Fab Stz
2025-01-15 16:59 ` Thomas Gleixner
2025-02-23 17:01 ` Fab Stz
2025-02-24 8:13 ` Thomas Gleixner
2025-02-25 8:11 ` Fab Stz
2025-02-25 19:35 ` Thomas Gleixner [this message]
2025-02-25 22:37 ` [PATCH] intel_idle: Handle older CPUs, which stop the TSC in deeper C states, correctly Thomas Gleixner
2025-02-26 10:24 ` Rafael J. Wysocki
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=87eczlg6ls.ffs@tglx \
--to=tglx@linutronix.de \
--cc=anna-maria@linutronix.de \
--cc=daniel.lezcano@linaro.org \
--cc=fabstz-it@yahoo.fr \
--cc=frederic@kernel.org \
--cc=jacob.jun.pan@linux.intel.com \
--cc=jstultz@google.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@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