public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Eggers <ceggers@arri.de>
To: <netdev@vger.kernel.org>, Brian Hutchinson <b.hutchman@gmail.com>
Cc: Vladimir Oltean <OlteanV@gmail.com>, <arun.ramadoss@microchip.com>
Subject: Re: Microchip net DSA with ptp4l getting tx_timeout failed msg using 6.3.12 kernel and KSZ9567 switch
Date: Wed, 23 Aug 2023 10:22:48 +0200	[thread overview]
Message-ID: <4860127.31r3eYUQgx@n95hx1g2> (raw)
In-Reply-To: <CAFZh4h9wHtTGFag-JDtjqFEmqnMoW4cTOr_CF3GQwKLb5jigrQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1961 bytes --]

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

[-- Attachment #2: 2023-08-23_ptp.tar.gz --]
[-- Type: application/x-compressed-tar, Size: 29954 bytes --]

  reply	other threads:[~2023-08-23  8:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-22 21:49 Microchip net DSA with ptp4l getting tx_timeout failed msg using 6.3.12 kernel and KSZ9567 switch Brian Hutchinson
2023-08-23  8:22 ` Christian Eggers [this message]
2023-08-23 18:12   ` Brian Hutchinson
     [not found]   ` <CAFZh4h-6yWvpvzJyv06zy8MbtMmXG==V0h2vU=uUN8iMMcb=ig@mail.gmail.com>
2023-08-24 18:26     ` Brian Hutchinson
2023-08-24 19:03       ` Brian Hutchinson
2023-08-25 15:49         ` Christian Eggers
2023-08-26 11:43         ` Vladimir Oltean

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4860127.31r3eYUQgx@n95hx1g2 \
    --to=ceggers@arri.de \
    --cc=OlteanV@gmail.com \
    --cc=arun.ramadoss@microchip.com \
    --cc=b.hutchman@gmail.com \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox