From: "Dr. David Alan Gilbert" <dave@treblig.org>
To: tglx@kernel.org, jstultz@google.com, sboyd@kernel.org
Cc: linux-kernel@vger.kernel.org, regressions@lists.linux.dev
Subject: [REGRESSION] Random 'clocksource: Watchdog remote CPU ?? read timed out'
Date: Mon, 3 Aug 2026 16:45:58 +0000 [thread overview]
Message-ID: <anDFxqll6Pb05RmC@gallifrey> (raw)
Hi all,
I've noticed in my logs on every boot since 7.1.x a:
[ 6.749566] clocksource: Watchdog remote CPU 11 read timed out
with the CPU being different each time. There's no apparent bad
side effects or anything, but it seemed worth reporting and I noticed
It's only one each boot as far as I can tell.
I checked back through journalctl -b -... and the first time I got
it was the first 7.1.x boot, and I remember seeing this during rc's
as well but that was on a bit of a random build.
The current ones are happening on Fedora's 7.1.5-201.fc44.x86_64
dg@dalek:~$ sudo dmesg|grep -i watchdog
[ 0.381705] NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.
[ 2.244379] sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver
[ 2.253962] sp5100-tco sp5100-tco: Using 0xfeb00000 for watchdog MMIO address
[ 6.749566] clocksource: Watchdog remote CPU 11 read timed out
dg@dalek:~$ sudo journalctl -b -1 |grep -i Watchdog
Aug 02 11:52:48 dalek kernel: NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.
Aug 02 11:52:49 dalek kernel: sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver
Aug 02 11:52:49 dalek kernel: sp5100-tco sp5100-tco: Using 0xfeb00000 for watchdog MMIO address
Aug 02 11:53:00 dalek rtkit-daemon[1703]: Watchdog thread running.
Aug 02 11:53:17 dalek kernel: clocksource: Watchdog remote CPU 26 read timed out
dg@dalek:~$ sudo journalctl -b -2 |grep -i Watchdog
Aug 01 12:14:48 dalek kernel: NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.
Aug 01 12:14:49 dalek kernel: sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver
Aug 01 12:14:49 dalek kernel: sp5100-tco sp5100-tco: Using 0xfeb00000 for watchdog MMIO address
Aug 01 12:15:00 dalek rtkit-daemon[1697]: Watchdog thread running.
Aug 01 12:15:16 dalek kernel: clocksource: Watchdog remote CPU 24 read timed out
dg@dalek:~$ sudo journalctl -b -3 |grep -i Watchdog
Jul 31 12:16:33 dalek kernel: NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.
Jul 31 12:16:34 dalek kernel: sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver
Jul 31 12:16:34 dalek kernel: sp5100-tco sp5100-tco: Using 0xfeb00000 for watchdog MMIO address
Jul 31 12:16:44 dalek rtkit-daemon[1696]: Watchdog thread running.
Jul 31 12:16:48 dalek kernel: clocksource: Watchdog remote CPU 31 read timed out
dg@dalek:~$ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 43 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 32
On-line CPU(s) list: 0-31
Vendor ID: AuthenticAMD
Model name: AMD Ryzen 9 3950X 16-Core Processor
CPU family: 23
Model: 113
Thread(s) per core: 2
Core(s) per socket: 16
Socket(s): 1
Stepping: 0
Frequency boost: enabled
CPU(s) scaling MHz: 50%
CPU max MHz: 4761.2300
CPU min MHz: 2200.0000
BogoMIPS: 6986.90
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr
sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl xto
pology nonstop_tsc cpuid extd_apicid aperfmperf rapl pni pclmulqdq monitor ssse3 fma cx1
6 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr
8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_cor
e perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw_pstate ssbd mba ibpb stibp vm
mcall fsgsbase bmi1 avx2 smep bmi2 cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsav
eopt xsavec xgetbv1 cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsav
eerptr rdpru wbnoinvd arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid
decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif v_spec_ctrl umip rdpid o
verflow_recov succor smca sev sev_es
Thanks,
Dave
--
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux | Happy \
\ dave @ treblig.org | | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
reply other threads:[~2026-08-03 16:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=anDFxqll6Pb05RmC@gallifrey \
--to=dave@treblig.org \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=sboyd@kernel.org \
--cc=tglx@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.