TX2 L4T 32.5.1 exssive interrupts on tegra-gpio pin 101 phy_interrupt


While trying to update to L4T 32.5.1, while the update works and all user applications don’t have an issue, there is an enormous amount of interrupts being generated on the phy_interrupt line causing CPU0 to be maxed out at 100% at all times.

[root@SRH123456789 of_node]$ tegrastats 
RAM 510/7858MB (lfb 1292x4MB) CPU [100%@2035,0%@2034,0%@2035,8%@2036,11%@2035,7%@2035] EMC_FREQ 1%@1866 GR3D_FREQ 0%@1300 VIC_FREQ 0%@985 APE 150 MTS fg 0% bg 0% PLL@33.5C MCPU@33.5C PMIC@100C Tboard@28C GPU@31C BCPU@33.5C thermal@32.5C Tdiode@30.5C VDD_SYS_GPU 387/387 VDD_SYS_SOC 1451/1451 VDD_4V0_WIFI 345/345 VDD_IN 5107/5107 VDD_SYS_CPU 919/919 VDD_SYS_DDR 1284/1284
[root@SRH123456789 of_node]$ cat /proc/interrupts | grep phy_interrupt
233:  840998473          0          0          0          0          0  tegra-gpio 101 Level     phy_interrupt

The .dts file has not changed between the two install version so I’m not sure why there would be so many interrupts. As far as i can tell, the pin phy_interrupt is not even an external pin. Any idea what might be going on?

Do you observe the issue on TX2 developer kit or your custom board? By default we have done SQA test on developer kit and it should not happen. Would like to know if it is specific to your custom board.

This is specific to our custom board. The Nvidia provided kernel and device-tree works fine on the developer kit. However when using the new kernel with the same device tree, gpio layout, etc, from our previous L4T install, the issue appears on our custom board.

After looking through some forums, I noticed this page Jetson TX2 NX Ethernet Interrupt Pin, which states that the interrupt pin for eth_phy is not actually pin 101 (M.05) but is actually AA.07. We set our pinmux up assuming M.05 is the correct interrupt pin, could this have caused the weird behaviour? We use the TX2 with ethernet SOC, not the TX2-NX SOC, I assume the internal connections are the same but I’d like confirmation.

hello daniel.vasile,

since it’s customize board, you should apply the Pinmux Changes to change the pinmux configuration applied by the software.
please check pin groups to review the pinmux configuration,
for example, $ sudo cat /sys/kernel/debug/pinctrl/<address>.pinmux/pinconf-groups

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.