[Linuxptp-users] pmc not getting any output
ptp OC started with slave clock as follows [root@centos7 linuxptp]# ./ptp4l -f /etc/ptp4l_slave.conf -i eth1 -s -m ptp4l[531140.983]: config item (null).assume_two_step is 1 ptp4l[531140.983]: config item (null).check_fup_sync is 0 ptp4l[531140.983]: config item (null).tx_timestamp_timeout is 10 ptp4l[531140.983]: config item (null).hwts_filter is 0 ptp4l[531140.983]: config item (null).clock_servo is 0 ptp4l[531140.983]: config item (null).clock_type is 32768 ptp4l[531140.983]: config item (null).clock_servo is 0 ptp4l[531140.983]: config item (null).clockClass is 248 ptp4l[531140.983]: config item (null).clockAccuracy is 254 ptp4l[531140.983]: config item (null).offsetScaledLogVariance is 65535 ptp4l[531140.983]: config item (null).productDescription is ';;' ptp4l[531140.983]: config item (null).revisionData is ';;' ptp4l[531140.983]: config item (null).userDescription is ';' ptp4l[531140.983]: config item (null).manufacturerIdentity is '00:00:00' ptp4l[531140.984]: config item (null).domainNumber is 24 ptp4l[531140.984]: config item (null).slaveOnly is 1 ptp4l[531140.984]: config item (null).gmCapable is 1 ptp4l[531140.984]: config item (null).gmCapable is 1 ptp4l[531140.984]: config item (null).G.8275.defaultDS.localPriority is 128 ptp4l[531140.984]: config item (null).maxStepsRemoved is 255 ptp4l[531140.984]: config item (null).time_stamping is 1 ptp4l[531140.984]: config item (null).twoStepFlag is 1 ptp4l[531140.984]: config item (null).twoStepFlag is 1 ptp4l[531140.984]: config item (null).time_stamping is 1 ptp4l[531140.984]: config item (null).priority1 is 128 ptp4l[531140.984]: config item (null).priority2 is 128 ptp4l[531140.984]: interface index 3 is up ptp4l[531140.984]: config item (null).free_running is 0 ptp4l[531140.984]: selected /dev/ptp1 as PTP clock ptp4l[531140.984]: config item (null).clockIdentity is '00..00' ptp4l[531140.984]: config item (null).uds_address is '/var/run/ptp4l' ptp4l[531140.984]: section item /var/run/ptp4l.announceReceiptTimeout now 0 ptp4l[531140.984]: section item /var/run/ptp4l.delay_mechanism now 0 ptp4l[531140.984]: section item /var/run/ptp4l.network_transport now 0 ptp4l[531140.984]: section item /var/run/ptp4l.delay_filter_length now 1 ptp4l[531140.984]: config item (null).free_running is 0 ptp4l[531140.984]: config item (null).freq_est_interval is 1 ptp4l[531140.984]: config item (null).write_phase_mode is 0 ptp4l[531140.984]: config item (null).gmCapable is 1 ptp4l[531140.984]: config item (null).kernel_leap is 1 ptp4l[531140.984]: config item (null).utc_offset is 37 ptp4l[531140.984]: config item (null).timeSource is 160 ptp4l[531140.984]: config item (null).pi_proportional_const is 0.00 ptp4l[531140.984]: config item (null).pi_integral_const is 0.00 ptp4l[531140.984]: config item (null).pi_proportional_scale is 0.00 ptp4l[531140.984]: config item (null).pi_proportional_exponent is -0.30 ptp4l[531140.984]: config item (null).pi_proportional_norm_max is 0.70 ptp4l[531140.984]: config item (null).pi_integral_scale is 0.00 ptp4l[531140.984]: config item (null).pi_integral_exponent is 0.40 ptp4l[531140.984]: config item (null).pi_integral_norm_max is 0.30 ptp4l[531140.984]: config item (null).step_threshold is 0.00 ptp4l[531140.984]: config item (null).first_step_threshold is 0.20 ptp4l[531140.984]: config item (null).max_frequency is 9 ptp4l[531140.984]: config item (null).servo_offset_threshold is 0 ptp4l[531140.984]: config item (null).servo_num_offset_values is 10 ptp4l[531140.984]: config item (null).dataset_comparison is 1 ptp4l[531140.984]: config item (null).delay_filter_length is 10 ptp4l[531140.984]: config item (null).delay_filter is 1 ptp4l[531140.984]: config item (null).tsproc_mode is 0 ptp4l[531140.984]: config item (null).initial_delay is 0 ptp4l[531140.984]: config item (null).summary_interval is 0 ptp4l[531140.984]: config item (null).sanity_freq_limit is 2 ptp4l[531140.984]: PI servo: sync interval 1.000 kp 0.700 ki 0.30 ptp4l[531140.984]: config item /var/run/ptp4l.boundary_clock_jbod is 0 ptp4l[531140.984]: config item /var/run/ptp4l.network_transport is 0 ptp4l[531140.984]: config item /var/run/ptp4l.masterOnly is 0 ptp4l[531140.984]: config item /var/run/ptp4l.BMCA is 0 ptp4l[531140.984]: config item /var/run/ptp4l.delayAsymmetry is 0 ptp4l[531140.984]: config item /var/run/ptp4l.follow_up_info is 0 ptp4l[531140.984]: config item /var/run/ptp4l.freq_est_interval is 1 ptp4l[531140.984]: config item /var/run/ptp4l.msg_interval_request is 0 ptp4l[531140.984]: config item /var/run/ptp4l.net_sync_monitor is 0 ptp4l[531140.984]: config item /var/run/ptp4l.path_trace_enabled is 0 ptp4l[531140.984]: config item /var/run/ptp4l.tc_spanning_tree is 0 ptp4l[531140.984]: config item /var/run/ptp4l.ingressLatency is 0 ptp4l[531140.984]: config item /var/run/ptp4l.egressLatency is 0 ptp4l[531140.984]: config item /var/run/ptp4l.delay_mechanism is 0 ptp4l[531140.984]: config ite
Re: [Linuxptp-users] Accuracy in Software Timestamp Mode
On Thu, May 21, 2020 at 09:26:59AM -0400, cpham2...@comcast.net wrote: > Hi, I am running linuxptp version 2.0 in software timestamp mode, and I found > the "master offsets" are all over the places. In ~7000 offset measurements, > more than 50% is greater than 100 micro-sec. Maximum offsets observed is > around 300 micro-secs. I wonder anyone ran linuxptp in software timestamp > mode and what accuracy level was observed. > My master clock and PTP clients on are a local network with no PTP-support > switches. There are 4 switches along the path between the master clock and > the clients. When I ran linuxptp in hardware timestamp mode in the same > network setting, I achieved great results: 90% of master offsets is within 1 > micro-sec. In software timestamp mode the master offsets are higher than > expected. Is there anything I can do to improve the accuracy? There are few things you could try to improve the stability with SW timestamping: - disable interrupt coalescing on the NIC with ethtool -C if possible - disable power saving features (e.g. set the CPU to a constant frequency, disable idle states) - disable energy efficient ethernet (EEE) - this helps with HW timestamping too To improve accuracy, use the same HW, SW, and configuration on the master and slave, so the errors in RX/TX timestamping cancel out. -- Miroslav Lichvar ___ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
