> -----Original Message----- > From: jord.p...@gmail.com [mailto:jord.p...@gmail.com] > Sent: Friday, August 10, 2018 10:45 AM > To: Keller, Jacob E <jacob.e.kel...@intel.com> > Cc: Richard Cochran <richardcoch...@gmail.com>; Cliff Spradlin via Linuxptp- > users <linuxptp-users@lists.sourceforge.net>; Chris Caudle > <ch...@chriscaudle.org>; Cliff Spradlin <csprad...@waymo.com> > Subject: Re: [Linuxptp-users] Fixing offset jump at reset? > > Hi Richard and Jacob, > > The most interesting is that on RHEL7 the 36 second offset occurs after the > tx_timestamp_timeout error and after that the offset only drifts further away. > (After staying ‘synchronised’ in the 36xxxxxxxxx range for a little of time) > > I had tried the exact same thing between two HP Z440 PC’s (including the exact > same Ethernet adapter + driver) running Ubuntu (instead of RHEL7). The > tx_timestamp_timeout erorr occurred also on this slave server when pushing an > .iso of +-5GB over the Ethernet line, except it didn’t got an offset of 36 > seconds, > and it even re-synchronised after a while, while the RHEL7 slave only drifts > further away when pushing a lot of network traffic from that PTP slave server > over the network. > > Jord
Yep, this is indicative of a driver issue, possibly a bug in some RHEL backport. Thanks, Jake ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
