From: Feng Tang <feng.tang@intel.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
<linux-kernel@vger.kernel.org>, <sboyd@kernel.org>,
<corbet@lwn.net>, <Mark.Rutland@arm.com>, <maz@kernel.org>,
<kernel-team@meta.com>, <ak@linux.intel.com>,
<zhengjun.xing@intel.com>, Chris Mason <clm@meta.com>,
John Stultz <jstultz@google.com>,
Waiman Long <longman@redhat.com>
Subject: Re: [PATCH clocksource 1/3] clocksource: Reject bogus watchdog clocksource measurements
Date: Wed, 30 Nov 2022 14:00:04 +0800 [thread overview]
Message-ID: <Y4bxZCEAmPnALsRV@feng-clx> (raw)
In-Reply-To: <20221130055024.GM4001@paulmck-ThinkPad-P17-Gen-1>
On Tue, Nov 29, 2022 at 09:50:24PM -0800, Paul E. McKenney wrote:
[...]
> >
> > Great! As both HPET and PM_TIMER get the same calibration 1975.000 MHz,
> > and it matches the 40ms drift per second you mentioned earlier, this
> > seems like the CPUID(0x15) gave the wrong frequence number.
> >
> > Or unlikely, HPET and PM_TIMER are driven by the same circuit source,
> > which has deviation.
> >
> > Either way, I think the HW/FW could have some problem.
>
> And this time with your printk()s:
>
> [ 0.000000] tsc: using CPUID[0x15] crystal_khz= 24000 kHz ebx=158 eax=2
> [ 0.000000] tsc: Detected 1900.000 MHz processor
> [ 0.000000] tsc: Detected 1896.000 MHz TSC
> [ 5.268858] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1910969940391419 ns
> [ 25.706231] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x36a8d32ce31, max_idle_ns: 881590731004 ns
> [ 32.223011] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275000 ns
> [ 57.823933] clocksource: Switched to clocksource tsc-early
> [ 58.144840] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
> [ 63.613713] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x36a8d32ce31, max_idle_ns: 881590731004 ns
> [ 63.637323] clocksource: Switched to clocksource tsc
> [ 64.673579] tsc: Warning: TSC freq calibrated by CPUID/MSR differs from what is calibrated by HW timer, please check with vendor!!
> [ 64.703719] tsc: Previous calibrated TSC freq: 1896.000 MHz
> [ 64.716816] tsc: TSC freq recalibrated by [PM_TIMER]: 1974.999 MHz
This confirms the tsc frequency is calculated from CPUID(0x15).
> What would be good next steps to check up on the hardware and firmware?
Maybe raise it to vendor? I have no idea how to check thos black boxes :)
> (My next step involves a pillow, but will follow up tomorrow morning
> Pacific Time.)
Really thanks for checking this through late night!
Thanks,
Feng
> Thanx, Paul
next prev parent reply other threads:[~2022-11-30 6:03 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 23:28 [PATCH clocksource 0/3] Reject bogus watchdog clocksource measurements Paul E. McKenney
2022-11-14 23:28 ` [PATCH clocksource 1/3] clocksource: " Paul E. McKenney
2022-11-17 21:57 ` Thomas Gleixner
2022-11-17 23:09 ` Paul E. McKenney
2022-11-21 0:55 ` Feng Tang
2022-11-21 15:21 ` Paul E. McKenney
2022-11-21 18:14 ` Paul E. McKenney
2022-11-22 15:55 ` Feng Tang
2022-11-22 22:07 ` Paul E. McKenney
2022-11-23 2:36 ` Feng Tang
2022-11-23 21:23 ` Paul E. McKenney
2022-11-28 2:15 ` Feng Tang
2022-11-29 19:29 ` Paul E. McKenney
2022-11-30 1:38 ` Feng Tang
2022-11-30 4:12 ` Paul E. McKenney
2022-11-30 4:49 ` Feng Tang
2022-11-30 5:16 ` Paul E. McKenney
2022-11-30 5:35 ` Feng Tang
2022-11-30 5:50 ` Paul E. McKenney
2022-11-30 6:00 ` Feng Tang [this message]
2022-12-01 17:24 ` Paul E. McKenney
2022-12-02 1:10 ` Feng Tang
2022-12-02 1:44 ` Paul E. McKenney
2022-12-02 2:02 ` Feng Tang
2022-12-02 22:24 ` Paul E. McKenney
2022-12-03 2:51 ` Feng Tang
2022-11-14 23:28 ` [PATCH clocksource 2/3] clocksource: Add comments to classify bogus measurements Paul E. McKenney
2022-11-14 23:28 ` [PATCH clocksource 3/3] clocksource: Exponential backoff for load-induced bogus watchdog reads Paul E. McKenney
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=Y4bxZCEAmPnALsRV@feng-clx \
--to=feng.tang@intel.com \
--cc=Mark.Rutland@arm.com \
--cc=ak@linux.intel.com \
--cc=clm@meta.com \
--cc=corbet@lwn.net \
--cc=jstultz@google.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=maz@kernel.org \
--cc=paulmck@kernel.org \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
--cc=zhengjun.xing@intel.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