From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: linux-parisc <linux-parisc@vger.kernel.org>
Cc: John Stultz <john.stultz@linaro.org>, Ingo Molnar <mingo@kernel.org>
Subject: Re: Cycle offset is larger than allowed by the 'jiffies' clock's max_cycles value
Date: Thu, 16 Sep 2021 23:38:54 +0200 [thread overview]
Message-ID: <1795824.tdWV9SEqCh@daneel.sf-tec.de> (raw)
In-Reply-To: <11708426.O9o76ZdvQC@eto.sf-tec.de>
[-- Attachment #1: Type: text/plain, Size: 836 bytes --]
Am Montag, 1. März 2021, 17:25:18 CEST schrieb Rolf Eike Beer:
> After upgrade to 5.11 get this multiple times per second on my C8000:
>
> [ 36.998702] WARNING: timekeeping: Cycle offset (29) is larger than
> allowed by the 'jiffies' clock's max_cycles value (10): time overflow
> danger [ 36.998705] timekeeping: Your kernel is sick, but tries
> to cope by capping time updates
This has nothing to do with the kernel version. For whatever reason
CONFIG_DEBUG_TIMEKEEPING was flipped on in the newer versions, no idea why and
how I did that.
However, that "may have a (very small) performance impact" in the Kconfig
isn't exactly true. When output through my 9600 serial line it slows the
kernel down to a crawl, so much that it doesn't even boot.
So, everything is fine for now.
Regards,
Eike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2021-09-16 21:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 16:25 Cycle offset is larger than allowed by the 'jiffies' clock's max_cycles value Rolf Eike Beer
2021-03-01 16:49 ` Rolf Eike Beer
2021-03-01 18:44 ` Rolf Eike Beer
2021-03-03 14:29 ` Helge Deller
2021-03-03 14:43 ` Rolf Eike Beer
2021-03-04 1:19 ` John David Anglin
2021-03-14 9:47 ` Rolf Eike Beer
2021-03-14 11:16 ` Helge Deller
2021-03-14 12:08 ` Rolf Eike Beer
2021-08-26 14:30 ` Rolf Eike Beer
2021-08-28 16:51 ` John David Anglin
2021-09-16 21:38 ` Rolf Eike Beer [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=1795824.tdWV9SEqCh@daneel.sf-tec.de \
--to=eike-kernel@sf-tec.de \
--cc=john.stultz@linaro.org \
--cc=linux-parisc@vger.kernel.org \
--cc=mingo@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;
as well as URLs for NNTP newsgroup(s).