Constant CPU usage of processes 'irq/297-1-0008' and 'sugov:8'

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Orin
1

Hi everyone,

I realized that there is a constant CPU usage of around 10% due to two processes on both my Jetson AGX Orins:

  • irq/297-1-0008

  • sugov:8

Now IRQ 297 seems to ‘fire’ around 800 times per second, according to watch -n 1 grep 297: /proc/interrupts, and seems to be GPIO-related. Since I am not really familiar with how GPIOs work on this board I don’t know if this is intended behaviour or not.

My question is this: Can this somehow be stopped? We don’t need the GPIOs, so we could turn them off completely.

3

Hi sebastian.fontius,

Are you using the devkit or custom board?
What’s your Jetpack version in use?

How did you check CPU usage?
Could you share the full result of cat /proc/interrupts for further check?

4

Hi KevinFFF,

both devices are bog-standard Nvidia Jetson AGX Orin (part number 945-13730-0000-000).

The JetPack version is as follows:

user@duke:~$ cat /etc/nv_tegra_release
# R34 (release), REVISION: 0.1, GCID: 29941907, BOARD: t186ref, EABI: aarch64, DATE: Sat Mar 12 02:32:39 UTC 2022

And:

user@gordon:~$ cat /etc/nv_tegra_release
# R34 (release), REVISION: 0.1, GCID: 29955323, BOARD: t186ref, EABI: aarch64, DATE: Tue Mar 15 08:13:50 UTC 2022

I checked the CPU usage using htop, but top shows the same. Also programs of a colleague ran measurably slower, if they were running on the affected CPU core.

Attached you will find a dump of /proc/interrupts. The line in question is 161.

Regards,

Sebastian
interrupts.txt (29.9 KB)

5

Is that the devkit or custom board?

It seems a quite old release and I would suggest you verifying with the latest JP5.1.2(R35.4.1).

297:   83008628          0          0          0          0          0          0          0          0          0          0          0      gpio  10 Level     1-0008

Please check which node in your device tree registering for 1-0008.

7

@KevinFFF you were right! Flashing the latest release fixed the issue :).

Thanks for your help!

8

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