On Fri, 2015-11-13 at 15:15 +0100, frank wrote:
>
> On 11/13/2015 02:29 PM, Richard Cochran wrote:
> > On Fri, Nov 13, 2015 at 01:26:45PM +0100, frank wrote:
> >
> > > Currently the value is still the default:
> > >
> > > tx_timestamp_timeout1
> > That means one millisecond. Try ten, and if
On Fri, Nov 13, 2015 at 03:15:57PM +0100, frank wrote:
> 10ms does not work either..
I have a BBB somewhere. I'll dig it out and try it with NFS myself.
Thanks,
Richard
--
___
On 11/13/2015 02:29 PM, Richard Cochran wrote:
> On Fri, Nov 13, 2015 at 01:26:45PM +0100, frank wrote:
>
>> Currently the value is still the default:
>>
>> tx_timestamp_timeout1
> That means one millisecond. Try ten, and if that doesn't work, then
> you likely have a driver/stack issue.
>
>
Hi,
On 11/13/2015 02:29 PM, Richard Cochran wrote:
> On Fri, Nov 13, 2015 at 01:26:45PM +0100, frank wrote:
>
>> It seems that linuxptp fails to work if the rootfs is mounted with nfs.
>> I debugged this a bit and it seems that already light nfs traffic causes
>> the issue.
> Sounds like a driver
On Fri, Nov 13, 2015 at 01:26:45PM +0100, frank wrote:
> Hi,
>
> I have a question wrt. to configuring linuxptp, what are "good values"
> for tx_timestamp_timeout?
The smaller, the better.
> It seems that linuxptp fails to work if the rootfs is mounted with nfs.
> I debugged this a bit and it
Hi,
I have a question wrt. to configuring linuxptp, what are "good values"
for tx_timestamp_timeout?
It seems that linuxptp fails to work if the rootfs is mounted with nfs.
I debugged this a bit and it seems that already light nfs traffic causes
the issue.
Below is a log of a machine which boot
