Closed chris-kuhr closed 1 year ago
What devices are used in this setup and what firmware stack are they running?
Where can I find that info?
Here is my lspci output:
christoph@srv3 ~/sources/jack2.git $ lspci -vvv -s04:00.0
04:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
Subsystem: Intel Corporation Ethernet Server Adapter I210-T1
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 35
Region 0: Memory at fe200000 (32-bit, non-prefetchable) [size=1M]
Region 3: Memory at fe300000 (32-bit, non-prefetchable) [size=16K]
Expansion ROM at fe100000 [disabled] [size=1M]
Capabilities: <access denied>
Kernel driver in use: igb_avb
Kernel modules: igb
How can I find the firmware stack version?
PTP only works with 2 802.1AS capable devices on a network. I see you have an i210. What is the other 802.1AS capable device that it is connected to?
It's a Extreme Networks x440. my setup usually works fine.
any suggestions?
My only suggestion would be to turn on more logging and do a wireshark capture. After that, more careful analysis will be required.
Ok, I have identified the problem.
It is mandatory to set
hwconfig.tx_type = HWTSTAMP_TX_ON;
otherwise the ptp daemon loses sync as.
Great! It is not on by default?
Sorry, I think there is a misunderstanding...
I had an avtp listener socket configured for timestamping, not the ptp daemon. Thus, I only would want the Rx timestamps and configured the socket accordingly. Now I have tried these options since the ptp daemon works well with them.
It seems, that it affects the socket of the ptp daemon, when I open a new socket with SO_TIMESTAMPING in my application.
Thanks for clarifying.
Hi *,
I have a problem with the hw timestamping of incoming ethernet frames.
The gPTP daemon looses sync and never recovers. reboot required.
I have setup up a raw socket with the following socket option, as it was proposed in https://github.com/AVnu/OpenAvnu/issues/437
...and try to read the ancillary data as follows:
I cannot receive any avtp packet on this socket, since the bridge port is not AS Capable anymore.
Can someone tell me, what I am doing wrong?
Thanks! Best, Ck