Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2178233

Summary: ptp4l couldn't calibrate the frequency when using software timestamping
Product: Red Hat Enterprise Linux 9 Reporter: Yalin.Li <yalli>
Component: linuxptpAssignee: Miroslav Lichvar <mlichvar>
Status: CLOSED ERRATA QA Contact: Yalin.Li <yalli>
Severity: high Docs Contact:
Priority: high    
Version: 9.2CC: kzhang, mlichvar, pvlasin
Target Milestone: rcKeywords: Regression, Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: linuxptp-3.1.1-6.el9_2.1 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 2179041 (view as bug list) Environment:
Last Closed: 2023-05-09 07:48:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2144442, 2179041    
Deadline: 2023-03-27   

Description Yalin.Li 2023-03-14 15:41:50 UTC 
Description of problem:
Problem only be found in 3.1.1-6, 3.1.1-5 is fine.

# ptp4l -ES2mi ens1f0
ptp4l[27265.140]: port 1: INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l[27265.140]: port 0: INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l[27265.140]: port 0: INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l[27265.140]: Switched to /dev/ptp2 as PTP clock
ptp4l[27270.529]: port 1: new foreign master 40a6b7.fffe.352190-1
ptp4l[27272.385]: port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES
ptp4l[27272.385]: selected local clock 40a6b7.fffe.393530 as best master
ptp4l[27272.385]: port 1: assuming the grand master role
ptp4l[27274.529]: selected best master clock 40a6b7.fffe.352190
ptp4l[27274.529]: foreign master not using PTP timescale
ptp4l[27274.529]: port 1: MASTER to UNCALIBRATED on RS_SLAVE
ptp4l[27276.528]: master offset      58898 s0 freq -900000000 path delay     14238
ptp4l[27277.528]: master offset      59125 s1 freq -899999569 path delay     14238
ptp4l[27278.528]: master offset      47005 s2 freq -899952564 path delay     14238
ptp4l[27278.529]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
ptp4l[27279.529]: master offset      46417 s2 freq -899939050 path delay     14238
ptp4l[27280.529]: clockcheck: clock jumped backward or running slower than expected!
ptp4l[27280.529]: master offset      48786 s0 freq -899939050 path delay     14492
ptp4l[27280.529]: port 1: SLAVE to UNCALIBRATED on SYNCHRONIZATION_FAULT
ptp4l[27281.529]: master offset      45834 s2 freq -899977151 path delay     15464
ptp4l[27281.529]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
ptp4l[27282.529]: clockcheck: clock jumped backward or running slower than expected!
ptp4l[27282.529]: master offset      46952 s0 freq -899977151 path delay     15815
ptp4l[27282.529]: port 1: SLAVE to UNCALIBRATED on SYNCHRONIZATION_FAULT
ptp4l[27283.529]: master offset      45373 s2 freq -899980151 path delay     16136
ptp4l[27283.529]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
ptp4l[27284.529]: clockcheck: clock jumped backward or running slower than expected!
ptp4l[27284.529]: master offset      47911 s0 freq -899980151 path delay     15815
ptp4l[27284.529]: port 1: SLAVE to UNCALIBRATED on SYNCHRONIZATION_FAULT
ptp4l[27285.529]: master offset      48483 s2 freq -899979064 path delay     15815
ptp4l[27285.529]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
ptp4l[27286.529]: clockcheck: clock jumped backward or running slower than expected!
ptp4l[27286.529]: master offset      50667 s0 freq -899979064 path delay     15975
ptp4l[27286.529]: port 1: SLAVE to UNCALIBRATED on SYNCHRONIZATION_FAULT
ptp4l[27287.529]: master offset      46197 s2 freq -899987557 path delay     16158
ptp4l[27287.529]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
ptp4l[27288.529]: clockcheck: clock jumped backward or running slower than expected!
ptp4l[27288.529]: master offset      48197 s0 freq -899987557 path delay     15975
ptp4l[27288.529]: port 1: SLAVE to UNCALIBRATED on SYNCHRONIZATION_FAULT
ptp4l[27289.529]: master offset      47004 s2 freq -899989824 path delay     15975
ptp4l[27289.529]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
ptp4l[27290.529]: clockcheck: clock jumped backward or running slower than expected!
ptp4l[27290.529]: master offset      47606 s0 freq -899989824 path delay     16030
ptp4l[27290.529]: port 1: SLAVE to UNCALIBRATED on SYNCHRONIZATION_FAULT
ptp4l[27291.529]: master offset      46023 s2 freq -899992831 path delay     16030
ptp4l[27291.529]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
ptp4l[27292.529]: clockcheck: clock jumped backward or running slower than expected!
ptp4l[27292.529]: master offset      48725 s0 freq -899992831 path delay     16030
ptp4l[27292.529]: port 1: SLAVE to UNCALIBRATED on SYNCHRONIZATION_FAULT
ptp4l[27293.529]: master offset      47038 s2 freq -899996036 path delay     16030
ptp4l[27293.529]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
ptp4l[27294.529]: clockcheck: clock jumped backward or running slower than expected!
ptp4l[27294.529]: master offset      48099 s0 freq -899996036 path delay     16030
ptp4l[27294.529]: port 1: SLAVE to UNCALIBRATED on SYNCHRONIZATION_FAULT
ptp4l[27295.529]: master offset      48267 s2 freq -899995717 path delay     16030
ptp4l[27295.529]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
ptp4l[27296.529]: clockcheck: clock jumped backward or running slower than expected!
ptp4l[27296.529]: master offset      46255 s0 freq -899995717 path delay     16030
ptp4l[27296.529]: port 1: SLAVE to UNCALIBRATED on SYNCHRONIZATION_FAULT
ptp4l[27297.529]: master offset      48781 s2 freq -899990918 path delay     15782
ptp4l[27297.529]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
ptp4l[27298.529]: clockcheck: clock jumped backward or running slower than expected!
ptp4l[27298.529]: master offset      49278 s0 freq -899990918 path delay     16098
ptp4l[27298.529]: port 1: SLAVE to UNCALIBRATED on SYNCHRONIZATION_FAULT
ptp4l[27299.529]: master offset      47326 s2 freq -899994627 path delay     16191
ptp4l[27299.529]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
ptp4l[27300.529]: clockcheck: clock jumped backward or running slower than expected!
ptp4l[27300.529]: master offset      50189 s0 freq -899994627 path delay     15925
ptp4l[27300.529]: port 1: SLAVE to UNCALIBRATED on SYNCHRONIZATION_FAULT


Version-Release number of selected component (if applicable):
linuxptp-3.1.1-6.el9.x86_64

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:
slave clock fail to sync to the master clock

Expected results:
slave clock should successfully sync to the master clock

Additional info:
Comment 1 Miroslav Lichvar 2023-03-15 09:40:56 UTC 
This was broken by the VLAN over bond patches.
Comment 2 Miroslav Lichvar 2023-03-15 10:52:19 UTC 
This completely breaks synchronization of the system clock with SW timestamping on interfaces that also support HW timestamping.

Fix submitted upstream: https://www.mail-archive.com/linuxptp-devel@lists.sourceforge.net/msg06420.html
Comment 9 Yalin.Li 2023-03-27 10:04:12 UTC 
PTP regression test passed(including reproducer):
https://beaker.engineering.redhat.com/jobs/7657668
https://beaker.engineering.redhat.com/jobs/7653882
Comment 14 errata-xmlrpc 2023-05-09 07:48:10 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (linuxptp bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:2349