Cpufreq log flushing dmesg

Hi,
I’m using Jetson Orin Nano 4G with jetson linux 35.4.1. Recently I found that we started to get endless logs about cpu frequency in the dmesg:

[267661.756357] cpufreq: cpu0,cur:1387000,set:1510400,set ndiv:118
[267819.099389] cpufreq: cpu0,cur:1660000,set:1510400,set ndiv:118
[267852.081830] cpufreq: cpu4,cur:1395000,set:1510400,set ndiv:118
[267990.704487] cpufreq: cpu4,cur:1392000,set:1510400,set ndiv:118
[268136.892359] cpufreq: cpu4,cur:1386000,set:1510400,set ndiv:118
[268155.659522] cpufreq: cpu4,cur:1670000,set:1510400,set ndiv:118
[268156.689468] cpufreq: cpu0,cur:1386000,set:1510400,set ndiv:118
[268333.827786] cpufreq: cpu4,cur:1394000,set:1510400,set ndiv:118
[268459.200372] cpufreq: cpu4,cur:1384000,set:1510400,set ndiv:118
[268650.524726] cpufreq: cpu0,cur:1387000,set:1510400,set ndiv:118
[268657.126695] cpufreq: cpu4,cur:1382000,set:1510400,set ndiv:118
[268729.718302] cpufreq: cpu4,cur:1639000,set:1510400,set ndiv:118
[268742.903486] cpufreq: cpu0,cur:1373000,set:1510400,set ndiv:118
[268948.536317] cpufreq: cpu4,cur:1628000,set:1510400,set ndiv:118
[269541.371444] cpufreq: cpu0,cur:1368000,set:1510400,set ndiv:118
[269567.755177] cpufreq: cpu0,cur:1627000,set:1510400,set ndiv:118
[269653.533024] cpufreq: cpu0,cur:1374000,set:1510400,set ndiv:118
[269766.756165] cpufreq: cpu4,cur:1394000,set:1510400,set ndiv:118
[269772.321216] cpufreq: cpu0,cur:1628000,set:1510400,set ndiv:118

Can you help me understand what this is about and is this something we should worry about?

DevKit or custom board?
Under what circumstances will you hit this issue?
Does it work normally other then these dmesg log?

Hi its a custom board. It hasn’t been clear to us what has changed recently to trigger this, but we have some application running on it all the time which does video capturing & processing and it consumes a lot of system resources. It works normally(we think) despite the logs.

We would like to know about the reason behind these logs(like what process is dong what), and if it indicates anything bad happening.

Thanks!

It’s a bug in CPU frequency sampling on older L4T releases.
Please upgrade to JetPack 6 to fix it.

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