phc2sys service start failed with error "autoconfiguration cannot be mixed with manual config options"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Andre Mauricio Zelak |
Bug Description
Brief Description
-----------------
Using same phc2sys instance/interface configuration from previus STX versions the phc2sys service fails to start. The error message is: "autoconfiguration cannot be mixed with manual config options."
Severity
--------
Major
Steps to Reproduce
------------------
Configure the phc2sys instance as:
system ptp-instance-add phc0 phc2sys
system host-ptp-
system ptp-interface-add phc0if1 phc0
system host-if-ptp-assign controller-0 enp81s0f1 phc0if1
system ptp-instance-
system ptp-instance-apply
The configuration must have an PTP interface and the '-a' option in the command line.
Expected Behavior
------------------
The phc2sys starts ignoring the PTP interface given.
Actual Behavior
----------------
The phc2sys service fails to start.
Reproducibility
---------------
Always
System Configuration
-------
All
Branch/Pull Time/Commit
-------
stx master since commit 2a6ddfe1b9700ce
Last Pass
---------
stx 8.0
Timestamp/Logs
--------------
$ systemctl status phc2sys@*
* <email address hidden> - Synchronize system clock or PTP hardware clock (PHC)
Loaded: loaded (/etc/systemd/
Active: failed (Result: exit-code) since Thu 2023-11-30 19:11:10 UTC; 4h 14min ago
Process: 875095 ExecStart=
Process: 875096 ExecStartPost=
Process: 875097 ExecStopPost=
Main PID: 875095 (code=exited, status=
CPU: 3ms
$ cat /etc/default/
OPTIONS="-a -r -R 2 -u 600 "
$ cat /etc/linuxptp/
[global]
##
## Default Data Set
##
domainNumber 24
logging_level 7
message_tag phc0
uds_address /var/run/
[enp81s0f1]
##
## Associated interface: enp81s0f1
##
./phc2sys -a -r -R 2 -u 600 -f phc2sys-
autoconfiguration cannot be mixed with manual config options.
usage: phc2sys [options]
automatic configuration:
-a turn on autoconfiguration
-r synchronize system (realtime) clock
manual configuration:
-c [dev|name] slave clock (CLOCK_REALTIME)
-d [dev] master PPS device
-s [dev|name] master clock
-O [offset] slave-master time offset (0)
-w wait for ptp4l
common options:
-f [file] configuration file
-E [pi|linreg] clock servo (pi)
-P [kp] proportional constant (0.7)
-I [ki] integration constant (0.3)
-S [step] step threshold (disabled)
-F [step] step threshold only on start (0.00002)
-R [rate] slave clock update rate in HZ (1.0)
-N [num] number of master clock readings per update (5)
-L [limit] sanity frequency limit in ppb (200000000)
-M [num] NTP SHM segment number (0)
-D [num] fall back to default clock in automatic mode (1)
-u [num] number of clock updates in summary stats (0)
-n [num] domain number (0)
-x apply leap seconds by servo instead of kernel
-z [path] server address for UDS (/var/run/ptp4l)
-l [num] set the logging level to 'num' (6)
-t [tag] add tag to log messages
-m print messages to stdout
-q do not print messages to the syslog
-v prints the software version and exits
-h prints this message and exits
Test Activity
-------------
Developer Testing
Workaround
----------
Don't configure or remote the PTP interface configuration.
Changed in starlingx: | |
assignee: | nobody → Andre Mauricio Zelak (azelak) |
Changed in starlingx: | |
importance: | Undecided → Medium |
tags: | added: stx.9.0 stx.networking |
Fix proposed to branch: master /review. opendev. org/c/starlingx /integ/ +/904782
Review: https:/