integ/centos_srpms_centos.lst
Cole Walker 1f4538df28 Add collection of linuxptp patches
This commit applies several patches to the linuxptp srpm in order to
address an issue syncing multiple interfaces on a ptp node. The srpm
used is linuxptp-2.0-2.el7.src.rpm.

Patch descriptions:
base/linuxptp/centos/meta_patches:
0001 updates the srpm spec file to apply the patches during build
0002 updates the package versioning to comply with the STX format

base/linuxptp/centos/patches:
Patches 0001-0005 combine to correct a fault present when a ptp node is
configured with multiple clocks in jbod mode which results in the client
port getting stuck in the UNCALIBRATED state and unable to lock to the
Grandmaster clock. The root of the issue lies in the sanity check where
checking timestamps recieved on multiple ports will result in the
sanity_freq_limit threshold constantly being reached and the servo for
that port is repeatedly reset, preventing it from ever syncing.

The changes in patches 0001-0005 have been written by Miroslav Lichvar
on the linuxptp-devel mailing list. They are currently under review and
testing by the upstream linuxptp maintainers prior to merging. I was
able to apply them as-is to linuxptp v2.0. I have chosen to keep them as
individual patches, as that is how they will appear upstream.

Patch 0006 is my work and serves to address an issue in phc2sys
where the local ptp clocks are not synced together properly if the local
time is far behind the reference time. This issue ocurrs when phc2sys
starts and there is no client port currently synced to a grandmaster. In
the original behaviour, phc2sys selects the first configured port and
proceeds to sync all of the other clocks to it by performing the
first_step operation.

Then ptp4l will evenually lock to the Grandmaster clock, and that
single port will have its time updated to the correct value, but
phc2sys has already performed the first_step operation and will not
step the other clocks again.

My solution is to provide an option to disable the selection of a
default port by phc2sys. When no default port is selected, phc2sys waits
for ptp4l to sync to the Grandmaster before bringing the other clocks
into sync with the first_step operation.

This option is configured via the default_sync
parameter or the -D flag. The default_sync parameter is set to on by
default to in order to keep the behaviour the same as upstream linuxptp
but can be configured by users via
system service-parameter-add ptp global default_sync=0

Closes-Bug: 1930607

Signed-off-by: Cole Walker <cole.walker@windriver.com>
Change-Id: I2f660787c6753dcd4fc4c51da7b08ab9e6f197f4
2021-06-28 14:15:22 -04:00

42 lines
1.4 KiB
Plaintext

anaconda-21.48.22.147-1.el7.centos.src.rpm
cloud-init-0.7.9-24.el7.centos.1.src.rpm
dhcp-4.2.5-82.el7.centos.src.rpm
dnsmasq-2.76-7.el7.src.rpm
facter-2.4.4-4.el7.src.rpm
grub2-2.02-0.86.el7.centos.src.rpm
grubby-8.28-25.el7.src.rpm
haproxy-1.5.18-8.el7.src.rpm
initscripts-9.49.46-1.el7.src.rpm
libevent-2.0.21-4.el7.src.rpm
lighttpd-1.4.54-1.el7.src.rpm
linuxptp-2.0-2.el7.src.rpm
logrotate-3.8.6-17.el7.src.rpm
net-tools-2.0-0.24.20131004git.el7.src.rpm
ntp-4.2.6p5-29.el7.centos.2.src.rpm
openldap-2.4.44-20.el7.src.rpm
openssh-7.4p1-21.el7.src.rpm
parted-3.1-29.el7.src.rpm
puppet-4.8.2-1.el7.src.rpm
puppet-ceph-2.4.1-1.el7.src.rpm
puppet-haproxy-1.5.0-4.6ffcb07git.el7.src.rpm
puppet-horizon-11.5.0-1.el7.src.rpm
puppet-keystone-11.3.0-1.el7.src.rpm
puppet-openstacklib-11.5.0-1.el7.src.rpm
puppet-oslo-11.3.0-1.el7.src.rpm
puppet-rabbitmq-5.6.0-4.5ac45degit.el7.src.rpm
puppet-staging-1.0.4-1.b466d93git.el7.src.rpm
puppet-stdlib-4.18.0-2.el7.src.rpm
python-docker-3.3.0-1.el7.src.rpm
python-keyring-5.7.1-1.el7.src.rpm
python-psycopg2-2.5.1-3.el7.src.rpm
python-voluptuous-0.8.9-1.el7.src.rpm
resource-agents-4.1.1-12.el7_6.7.src.rpm
setup-2.8.71-10.el7.src.rpm
shim-15-1.el7.centos.src.rpm
shim-signed-15-1.el7.centos.src.rpm
sudo-1.8.23-10.el7_9.1.src.rpm
systemd-219-78.el7_9.3.src.rpm
tboot-1.9.6-3.el7.src.rpm
tpm2-tools-3.0.4-2.el7.src.rpm
watchdog-5.13-12.el7.src.rpm