All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miroslav Lichvar <mlichvar@redhat.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] Periodic jumps of PHC on I350
Date: Fri, 5 Oct 2018 17:35:29 +0200	[thread overview]
Message-ID: <20181005153529.GK19804@localhost> (raw)

I'm observing a weird issue with the PTP clock on the I350. Every ~9.2
minutes (which coincides with a half of the 40-bit SYSTIM overflow) it
jumps about 1100 seconds back and then 8 seconds later it jumps ahead
to where it was supposed to be.

From ptp4l output:

ptp4l[1700.796]: master offset        126 s2 freq  -14982 path delay     45720
ptp4l[1701.796]: clockcheck: clock jumped backward or running slower than expected!
ptp4l[1701.796]: master offset -1099511626698 s0 freq  -14982 path delay     45720
ptp4l[1701.796]: port 1: SLAVE to UNCALIBRATED on SYNCHRONIZATION_FAULT
ptp4l[1702.796]: master offset -1099511626796 s0 freq  -14982 path delay     45720
ptp4l[1703.796]: master offset -1099511621597 s0 freq  -14982 path delay     45664
ptp4l[1704.796]: master offset -1099511625711 s2 freq -62499999 path delay     45720
ptp4l[1704.796]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
ptp4l[1705.796]: master offset -1099449150078 s2 freq -62499999 path delay     45902
ptp4l[1706.796]: master offset -1099386663207 s2 freq -62499999 path delay     45561
ptp4l[1707.796]: master offset -1099324177805 s2 freq -62499999 path delay     45561
ptp4l[1708.796]: master offset -1099261696997 s2 freq -62499999 path delay     45256
ptp4l[1709.796]: clockcheck: clock jumped forward or running faster than expected!
ptp4l[1709.796]: master offset  312422909 s0 freq -62499999 path delay     45256

I see it on four different machines (three have I350, one I354). I've
tried 4.19-rc6 and few different versions down to 4.13. All show this
behavior.

Any ideas what could be wrong?

-- 
Miroslav Lichvar

                 reply	other threads:[~2018-10-05 15:35 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=20181005153529.GK19804@localhost \
    --to=mlichvar@redhat.com \
    --cc=intel-wired-lan@osuosl.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.