1、nvidia-modeset/kthread_q
2、kworker/6:3+pm
3、kworker/2:2+pm
4、kworker/u28:0-devfreq_wq
Hi,
Please check CPU loading/frequency by running $ sudo tegrastats. The top command may not be precise because it does not show frequency, and the loading is sum of all CPU cores.
Are these threads all related to power management and CPU frequency scaling? Could you please focus on the functional implementation in this area? If so, could you provide relevant information so we can analyze it together?
nvidia-modeset/kthread_q
kworker/6:3+pm
kworker/u28:0-devfreq_wq
After the devkit is powered on, the GPU power consumption spikes three times per minute.
The following process also temporarily uses 100% of the CPU.
Xorg
kworker/1:0+pm
nv_queue
kworker/8:1+pm
kworker/2:1+pm
Provide a new clue: Every two times the GPU power consumption suddenly increases, the serial port will print the following garbled characters
mi@localhost:~$ ��INFO: END TASK:MB��
INFO: enter idle task.
INFO: END TASK:MB��
��ph =��ter idle ta��GPC ��sk.
��> logic map: 0=>0 1=>2 2=>1
��
mi@localhost:~$
mi@localhost:~$
mi@localhost:~$ ��GPC ph => logic map: 0=>0 1=>2 2=>1
��
Related Issues
Hi,
Please share steps to replicate the issue. We will set up developer kit to reproduce it and check with our teams.
Devkit R38.2.1
It can be reproduced by booting up without any other operations
Hi,
Please run the command to eliminate UART log and check again:
# echo on > /sys/bus/pci/devices/0000\:01\:00.0/power/control
The recurrence pattern is as follows:
Hi,
Do you mean you still see 100% loading after running th ecommand?
echo on > /sys/bus/pci/devices/0000\:01\:00.0/power/control
The problem does not recur after executing the command.
Have you found the specific cause of this problem?
Hi,
On Jetpack 7.0GA, please run the command. This shall not be present in next Jetpack 7.1.
Could you explain the root cause of this issue?
In Jetpack 7.1. Can the patch for the above fix be provided separately at that time?
When will Jetpack 7.1 be released?
Plan to release it at Dec.
Postponed to 2026/Jan/M
This issue no longer occurs in version JP7.1.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.