lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4860127.31r3eYUQgx@n95hx1g2>
Date: Wed, 23 Aug 2023 10:22:48 +0200
From: Christian Eggers <ceggers@...i.de>
To: <netdev@...r.kernel.org>, Brian Hutchinson <b.hutchman@...il.com>
CC: Vladimir Oltean <OlteanV@...il.com>, <arun.ramadoss@...rochip.com>
Subject: Re: Microchip net DSA with ptp4l getting tx_timeout failed msg using 6.3.12 kernel and KSZ9567 switch

Hi Brian,

I just return from my holidays...

Am Dienstag, 22. August 2023, 23:49:33 CEST schrieben Sie:
> Getting this tx_timestamp_timeout error over and over when I try to run ptp4l:
> 
> ptp4l[1366.143]: selected best master clock 001747.fffe.70151b
> ptp4l[1366.143]: updating UTC offset to 37
> ptp4l[1366.143]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE
> ptp4l[1366.860]: port 1: delay timeout
> ptp4l[1376.871]: timed out while polling for tx timestamp
> ptp4l[1376.871]: increasing tx_timestamp_timeout may correct this
> issue, but it is likely caused by a driver bug
> ptp4l[1376.871]: port 1: send delay request failed
> 
> I was using 5.10.69 with Christians patches before they were mainlined
> and had everything working with the help of Christian, Vladimir and
> others.
> 
> Now I need to update kernel so tried 6.3.12 which contains Christians
> upstream patches and I also back ported v8 of the upstreamed patches
> to 6.1.38 and I'm getting the same results with that kernel too.
> 

I am also in the process of upgrading to 6.1.38 (but not really tested).
I cherry-picked all necessary patches from the latest master (see attached
archive). Maybe you would like to compare this with your patch series.

> [...]
>
> I tried increasing tx_timestamp and it doesn't appear to matter.  I
> feel like I had this problem before when first starting to work with
> 5.10.69 but can't remember if another patch resolved it.  With 5.10.69
> I've got quite a few more patches than just the 13 that were mainlined
> in 6.3.  Looking through old emails I want to say it might have been
> resolved with net-dsa-ksz9477-avoid-PTP-races-with-the-data-path-l.patch
> that Vladimir gave me but looking at the code it doesn't appear
> mainline has that one.

How is the IRQ line of you switch attached? I remember there was a problem
with the IRQ type (edge vs. level), but I think this has already been
applied to 6.1.38 (via -stable).

regards,
Christian

Download attachment "2023-08-23_ptp.tar.gz" of type "application/x-compressed-tar" (29954 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ