Uninitialized ts2phc variable causes "ignoring invalid master time stamp" error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Cole Walker |
Bug Description
Brief Description
-----------------
After configuring and starting the ts2phc application via "system ptp-instance-
This appears to be the result of an unitialized variable in ts2phc and is corrected by this upstream fix in linuxptp: https:/
Severity
--------
Provide the severity of the defect.
<Major: System/Feature is usable but degraded>
Steps to Reproduce
------------------
Configure ts2phc
system ptp-instance-add ts1 ts2phc
system ptp-interface-add tsint1 ts1
system host-if-ptp-assign controller-0 oam0 tsint1
system host-if-ptp-assign controller-0 data0 tsint1
system ptp-instance-
system host-ptp-
system host-update controller-0 clock_synchroni
system ptp-instance-apply
Check ts2phc logs at /var/log/user.log for repeated instances of "ignoring invalid master time stamp"
Expected Behavior
------------------
The ts2phc service should not reject valid timestamps and should sync the configured clocks.
Actual Behavior
----------------
Ts2phc rejects valid timestamps and does not sync configured clocks
Reproducibility
---------------
Intermittent, but can be seen with repeated restarts of ts2phc.
System Configuration
-------
Any
Branch/Pull Time/Commit
-------
Stx master as of 2024-02-09
Last Pass
---------
Unknown
Timestamp/Logs
--------------
N/A
Test Activity
-------------
Developer testing
Workaround
----------
Restart the ts2phc application with "sudo systemctl restart ts2phc@*" and verify operation in /var/log/user.log
Changed in starlingx: | |
assignee: | nobody → Cole Walker (cwalops) |
tags: | added: stx.9.0 stx.networking |
Changed in starlingx: | |
importance: | Undecided → Medium |
Fixed by: https:/ /review. opendev. org/c/starlingx /integ/ +/910822
Merged on March 4
Note: The LP was not updated automatically because the Closes-Bug syntax was incorrect