From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: linux-parisc <linux-parisc@vger.kernel.org>
Subject: Re: Cycle offset is larger than allowed by the 'jiffies' clock's max_cycles value
Date: Sun, 14 Mar 2021 13:08:54 +0100 [thread overview]
Message-ID: <2191464.ElGaqSPkdT@daneel.sf-tec.de> (raw)
In-Reply-To: <dc93df38-d2c4-362e-0e22-b8885509c2ea@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1514 bytes --]
Am Sonntag, 14. März 2021, 12:16:11 CET schrieben Sie:
> On 3/14/21 10:47 AM, Rolf Eike Beer wrote:
> > Am Mittwoch, 3. März 2021, 15:29:42 CET schrieb Helge Deller:
> >> On 3/1/21 7:44 PM, Rolf Eike Beer wrote:
> >>> Am Montag, 1. März 2021, 17:49:42 CET schrieb Rolf Eike Beer:
> >>>> Am Montag, 1. März 2021, 17:25:18 CET 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
> >>
> >> I know I have seen this at least once with a 32-bit kernel in qemu as
> >> well....
> >>
> >>>> Not 5.11, but 5.10.11. 5.10.4 is fine. It could be a bad upgrade
> >>>> attempt,
> >>>> I'll retry once I have built a proper 5.11 kernel.
> >>>
> >>> Ok, it's there also in 5.11.2:
> >> You don't see it in 5.11, but in 5.11.2.
> >> Sadly none of the changes between those versions seem related
> >> to this problem.
> >>
> >> Do you still see this?
> >> I'd like to get it anaylzed/fixed.
> >
> > Me too. What do you need?
>
> I actually don't know.
> First of all it would be great if we could reproduce it.
> Right now I don't see this issue any longer, so I have nowhere to start
> from.
I get it every time if I boot that kernel.
Eike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2021-03-14 12:10 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 [this message]
2021-08-26 14:30 ` Rolf Eike Beer
2021-08-28 16:51 ` John David Anglin
2021-09-16 21:38 ` Rolf Eike Beer
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=2191464.ElGaqSPkdT@daneel.sf-tec.de \
--to=eike-kernel@sf-tec.de \
--cc=linux-parisc@vger.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