Thanks for the ftrace tips, Jake.I ran it with a 'igb_*' filter and grepped everything with ptp and excluded the rx_hang calls. This is the whole trace after starting the PTP client:
ptp4l-23256 [007] ...1 1064642.422359: igb_ptp_gettime_82576 <-ptp_clock_gettime ptp4l-23256 [007] d..2 1064642.422362: igb_ptp_read_82576 <-timecounter_read ptp4l-23256 [007] d..2 1064642.422362: igb_rd32 <-igb_ptp_read_82576 ptp4l-23256 [007] d..2 1064642.422366: igb_rd32 <-igb_ptp_read_82576 ptp4l-23256 [007] ...1 1064642.422388: igb_ptp_adjfreq_82576 <-ptp_clock_adjtime ptp4l-23256 [007] ...1 1064642.472550: igb_ptp_set_ts_config <-igb_ioctl ptp4l-23256 [007] ...1 1064642.472551: igb_ptp_set_timestamp_mode <-igb_ptp_set_ts_config ptp4l-23256 [007] ...1 1064642.472552: igb_rd32 <-igb_ptp_set_timestamp_mode ptp4l-23256 [007] ...1 1064642.472557: igb_rd32 <-igb_ptp_set_timestamp_mode ptp4l-23256 [007] ...1 1064642.472567: igb_rd32 <-igb_ptp_set_timestamp_mode ptp4l-23256 [007] ...1 1064642.472571: igb_rd32 <-igb_ptp_set_timestamp_mode ptp4l-23256 [007] ...1 1064642.472576: igb_rd32 <-igb_ptp_set_timestamp_mode ptp4l-23256 [007] ...1 1064642.472581: igb_rd32 <-igb_ptp_set_timestamp_mode ptp4l-23256 [007] ...1 1064642.472585: igb_rd32 <-igb_ptp_set_timestamp_mode kworker/7:0-19672 [007] ...1 1064642.682658: igb_ptp_tx_work <-process_one_work kworker/7:0-19672 [007] ...1 1064642.682660: igb_rd32 <-igb_ptp_tx_work kworker/7:0-19672 [007] ...1 1064642.682666: igb_rd32 <-igb_ptp_tx_work kworker/7:0-19672 [007] ...1 1064642.682670: igb_rd32 <-igb_ptp_tx_work kworker/7:0-19672 [007] ...1 1064642.682673: igb_ptp_systim_to_hwtstamp <-igb_ptp_tx_work kworker/7:0-19672 [007] ...1 1064644.014869: igb_ptp_tx_work <-process_one_work kworker/7:0-19672 [007] ...1 1064644.014878: igb_rd32 <-igb_ptp_tx_work kworker/7:0-19672 [007] ...1 1064644.014884: igb_rd32 <-igb_ptp_tx_work kworker/7:0-19672 [007] ...1 1064644.014888: igb_rd32 <-igb_ptp_tx_work kworker/7:0-19672 [007] ...1 1064644.014891: igb_ptp_systim_to_hwtstamp <-igb_ptp_tx_work kworker/7:0-19672 [007] ...1 1064645.055664: igb_ptp_tx_work <-process_one_work kworker/7:0-19672 [007] ...1 1064645.055665: igb_rd32 <-igb_ptp_tx_work kworker/7:0-19672 [007] ...1 1064645.055672: igb_rd32 <-igb_ptp_tx_work kworker/7:0-19672 [007] ...1 1064645.055675: igb_rd32 <-igb_ptp_tx_work kworker/7:0-19672 [007] ...1 1064645.055679: igb_ptp_systim_to_hwtstamp <-igb_ptp_tx_work kworker/7:0-19672 [007] ...1 1064645.521853: igb_ptp_tx_work <-process_one_work kworker/7:0-19672 [007] ...1 1064645.521854: igb_rd32 <-igb_ptp_tx_work kworker/7:0-19672 [007] ...1 1064645.521860: igb_rd32 <-igb_ptp_tx_work kworker/7:0-19672 [007] ...1 1064645.521864: igb_rd32 <-igb_ptp_tx_work kworker/7:0-19672 [007] ...1 1064645.521867: igb_ptp_systim_to_hwtstamp <-igb_ptp_tx_workSo there's not a single call to igb_ptp_rx_rgtstamp . There's even not a single call to igb_process_skb_fields . That's kind of weird. But wireshark sees packets coming, so they should not be discarded.
If it helps, I think this is the exact version of igb running on the machine: https://nv-tegra.nvidia.com/r/gitweb?p=linux-4.9.git;a=tree;f=drivers/net/ethernet/intel/igb;hb=43744be0144f1aefb06ade8e684fe5497d557e6f . It is compiled in the kernel, not as a module.
Thanks for further hints. On Jan 3 I should get back to the hardware, so then I can provide a "diff" of the trace with the working igb card.
Martin -- Mgr. Martin Pecka, Ph.D. Researcher at Vision for Robotics and Autonomous Systems group Faculty of Electrical Engineering Czech Technical University in Prague Phone: +420 22435 7269
smime.p7s
Description: Elektronicky podpis S/MIME
_______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
