PTP TX hardware timestamp timeout on Raspberry Pi CM5 (regression from 6.6 to 6.12)

Aperta
  • Qualcosa non va?
#7,515 4 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
c, linux, raspberry-pi
Ambito
embedded-iot, networking, operating-systems

Direzione di ricerca

Start with drivers/net/phy/bcm-phy-ptp.c and compare the PTP TX timestamp path between rpi-6.6.y and rpi-6.12.y, focusing on bcm_ptp_txtstamp, bcm_ptp_do_aux_work, and bcm_ptp_get_tstamp. Reproduce with ptp4l -i eth0 -m while monitoring UDP ports 319 and 320 with tcpdump. Done means PHY TX timestamps no longer time out on the Raspberry Pi CM5 with the newer kernel.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Describe the bug

Basic Information

  • Hardware: Raspberry Pi CM5 + Official CM5 IO Board
  • Network Port: eth0 (Cadence GEM MAC + BCM54213PE PHY)
  • Regression Scope: Kernel 6.6.74 (Working) → 6.12+ (Failing)

Test Matrix

Kernel Provider Result
rpi-6.6.y PHY timestamp (idx 0) PASS
rpi-6.12.y PHY timestamp (idx 0) FAIL
rpi-6.18.y PHY timestamp (idx 0) FAIL

Symptom

  1. Test side
pi@raspberrypi:~ $ sudo ptp4l -i eth0 -m
ptp4l[70.739]: selected /dev/ptp0 as PTP clock
ptp4l[70.745]: port 1: INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l[70.745]: port 0: INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l[77.867]: port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES
ptp4l[77.867]: selected local clock 2ccf67.fffe.feb41d as best master
ptp4l[77.867]: port 1: assuming the grand master role
ptp4l[78.868]: timed out while polling for tx timestamp
ptp4l[78.868]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug
ptp4l[78.868]: port 1: send sync failed
ptp4l[78.868]: port 1: MASTER to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)
  1. Monitoring end
pi@raspberrypi:~ $ sudo tcpdump -ni eth0 udp port 319 or udp port 320
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
10:11:14.984307 IP 192.168.8.4.320 > 224.0.1.129.320: PTPv2, v1 compat : no, msg type : announce msg, length : 64, domain : 0, reserved1 : 0, Flags [timescale], NS correction : 0, sub NS correction : 0, reserved2 : 0, clock identity : 0x2ccf67fffefeb41d, port id : 1, seq id : 0, control : 5 (Other), log message interval : 1, originTimeStamp : 0 seconds 0 nanoseconds, origin cur utc :37, rsvd : 0, gm priority_1 : 128, gm clock class : 248, gm clock accuracy : 254, gm clock variance : 65535, gm priority_2 : 128, gm clock id : 0x2ccf67fffefeb41d, steps removed : 0, time source : 0xa0
10:11:15.983322 IP 192.168.8.4.319 > 224.0.1.129.319: PTPv2, v1 compat : no, msg type : sync msg, length : 44, domain : 0, reserved1 : 0, Flags [two step], NS correction : 0, sub NS correction : 0, reserved2 : 0, clock identity : 0x2ccf67fffefeb41d, port id : 1, seq id : 0, control : 0 (Sync), log message interval : 0, originTimeStamp : 0 seconds, 0 nanoseconds

Reproduction (minimal)

  1. Install the following tools：
sudo apt install tcpdump  linuxptp -y
  1. Perform the following operations in a terminal：
sudo ptp4l -i eth0 -m
  1. Open a new terminal and perform the following operations：
sudo tcpdump -ni eth0 udp port 319 or udp port 320

Analysis

  1. drivers/net/phy/bcm-phy-ptp.c is functionally identical between rpi-6.6.y and rpi-6.18.y . The core TX timestamp logic ( bcm_ptp_txtstamp , bcm_ptp_do_aux_work , bcm_ptp_get_tstamp ) is unchanged.
  2. EEE is NOT the cause. ethtool --set-eee eth0 eee off does not resolve the issue.
  3. IRQ vs Poll mode irrelevant. Both modes fail on the newer kernels.
  4. Likely suspects (the regression was introduced between Linux 6.6 and 6.12)

Impact

This breaks PTP hardware timestamping via the PHY, which is required for industrial use cases requiring sub-100ns synchronization precision (motion control, IEC 61850, 5G fronthaul, TSN 802.1AS). MAC timestamps provide a lower-precision workaround (~50-200ns RGMII jitter vs <10ns for PHY timestamps).

Steps to reproduce the behaviour
  1. Install the following tools：
sudo apt install tcpdump  linuxptp -y
  1. Perform the following operations in a terminal：
sudo ptp4l -i eth0 -m
  1. Open a new terminal and perform the following operations：
sudo tcpdump -ni eth0 udp port 319 or udp port 320
Device (s)

Raspberry Pi CM5

System
  • Hardware: Raspberry Pi CM5 + Official CM5 IO Board
  • Network Port: eth0 (Cadence GEM MAC + BCM54213PE PHY)
  • Regression Scope: Kernel 6.6.74 (Working) → 6.12+ (Failing)
Logs

No response

Additional context

No response

Lingua principale
C
Stelle
13.3k
Fork
5.5k
Merge medio
3g 20h
PR unite (30g)
27

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di raspberrypi/linux

Tutte le issue di raspberrypi/linux

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.