All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Pecio <michal.pecio@gmail.com>
To: Thomas Gleixner <tglx@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Watchdog remote CPU read timed out
Date: Sun, 30 Aug 2026 14:16:16 +0200	[thread overview]
Message-ID: <20260830141503.42994806.michal.pecio@gmail.com> (raw)

Hi Thomas,

This is another warning I'm getting on recent 7.x kernels, apparently
from new code you wrote a few months ago.

Increasing WATCHDOG_DEFAULT_TIMEOUT_NS to 100us makes it go away, at
least for a few minutes (I will try longer uptime later).

With a few debug prints, I found that watchdog_wait_seq() fails every
few seconds, usually on CPU 0 but sporadically on others too.

Example output below. Is this something to worry about / fix?

Thanks,
Michal

[ 4307.502933] clocksource: watchdog_wait_seq done on cpu 0
[ 4307.502946] clocksource: watchdog_wait_seq done on cpu 1
[ 4307.502950] clocksource: watchdog_wait_seq done on cpu 0
[ 4307.502952] clocksource: watchdog_wait_seq done on cpu 1
[ 4307.502954] clocksource: watchdog_wait_seq done on cpu 0
[ 4307.502956] clocksource: watchdog_wait_seq done on cpu 1
[ 4307.502958] clocksource: watchdog_wait_seq done on cpu 0
[ 4307.502960] clocksource: watchdog_wait_seq done on cpu 1
[ 4308.006997] clocksource: watchdog_wait_seq done on cpu 0
[ 4308.007028] clocksource: watchdog_wait_seq done on cpu 0
[ 4308.007031] clocksource: watchdog_wait_seq done on cpu 0
[ 4308.007028] clocksource: WD_CPU_TIMEOUT in watchdog_wait_seq cpu 2
[ 4308.007034] clocksource: watchdog_wait_seq done on cpu 0
[ 4308.502975] clocksource: watchdog_wait_seq done on cpu 0
[ 4308.502991] clocksource: watchdog_wait_seq done on cpu 3
[ 4308.503021] clocksource: WD_CPU_TIMEOUT in watchdog_wait_seq cpu 0
[ 4308.503048] clocksource: watchdog_wait_seq done on cpu 3
[ 4308.503050] clocksource: watchdog_wait_seq done on cpu 3
[ 4308.503051] clocksource: watchdog_wait_seq done on cpu 3


             reply	other threads:[~2026-08-30 12:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-30 12:16 Michal Pecio [this message]
2026-10-25 21:54 ` Watchdog remote CPU read timed out Thomas Gleixner

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=20260830141503.42994806.michal.pecio@gmail.com \
    --to=michal.pecio@gmail.com \
    --cc=linux-kernel@vger.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.