Cpufreq warrning: cpufreq: cpu4,cur:1850000,set:1984000,set ndiv:155

Hi

Currently I am working on an embedded project using Orin NX 16G, Jetpack5.1.2.
I have fixed cpu frequency in /etc/rc.local like this

echo 1 > /sys/devices/system/cpu/cpu0/online
echo 1 > /sys/devices/system/cpu/cpu1/online
echo 1 > /sys/devices/system/cpu/cpu2/online
echo 1 > /sys/devices/system/cpu/cpu3/online
echo 1 > /sys/devices/system/cpu/cpu4/online
echo 1 > /sys/devices/system/cpu/cpu5/online
echo 1 > /sys/devices/system/cpu/cpu6/online
echo 1 > /sys/devices/system/cpu/cpu7/online
sleep 2
echo performance > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo performance > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
echo performance > /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor
echo performance > /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor
echo performance > /sys/devices/system/cpu/cpu4/cpufreq/scaling_governor
echo performance > /sys/devices/system/cpu/cpu5/cpufreq/scaling_governor
echo performance > /sys/devices/system/cpu/cpu6/cpufreq/scaling_governor
echo performance > /sys/devices/system/cpu/cpu7/cpufreq/scaling_governor

echo 1 > /sys/kernel/debug/bpmp/debug/clk/vi/mrq_rate_locked
echo 1 > /sys/kernel/debug/bpmp/debug/clk/isp/mrq_rate_locked
echo 1 > /sys/kernel/debug/bpmp/debug/clk/nvcsi/mrq_rate_locked
echo 1 > /sys/kernel/debug/bpmp/debug/clk/emc/mrq_rate_locked
sleep 1
cat /sys/kernel/debug/bpmp/debug/clk/vi/max_rate |tee /sys/kernel/debug/bpmp/debug/clk/vi/rate
cat /sys/kernel/debug/bpmp/debug/clk/isp/max_rate | tee /sys/kernel/debug/bpmp/debug/clk/isp/rate
cat /sys/kernel/debug/bpmp/debug/clk/nvcsi/max_rate | tee /sys/kernel/debug/bpmp/debug/clk/nvcsi/rate
cat /sys/kernel/debug/bpmp/debug/clk/emc/max_rate | tee /sys/kernel/debug/bpmp/debug/clk/emc/rate

During Kernel startup I am seeing some error messages related to CPU clock frequencies like,

Mar 15 23:04:18 Linux kernel: [    7.614531] OF: /i2c@3180000/max96712@4b: could not get #gpio-cells for /iommu@12000000
Mar 15 23:04:18 Linux kernel: [    7.634645] tegra23x-oc-event soctherm-oc-event: Finished tegra23x overcurrent event probing
**Mar 15 23:04:18 Linux kernel: [    7.657233] cpufreq: cpufreq_online: CPU0: Running at unlisted initial frequency: 2006000 KHz, changing to: 1984000 KHz**
**Mar 15 23:04:18 Linux kernel: [    7.670155] cpufreq: cpufreq_online: CPU4: Running at unlisted initial frequency: 2034000 KHz, changing to: 1984000 KHz**
Mar 15 23:04:18 Linux kernel: [    7.681968] tegra194-cpufreq e000000.ccplex: probed with ICC, cl:3
Mar 15 23:04:18 Linux kernel: [    7.689017] tegra194-pcie 14100000.pcie: Using GICv2m MSI allocator
Mar 15 23:04:18 Linux kernel: [    7.696367] tegra194-pcie 14100000.pcie: host bridge /pcie@14100000 ranges:
Mar 15 23:04:18 Linux kernel: [    7.703542] tegra194-pcie 14100000.pcie:       IO 0x0030100000..0x00301fffff -> 0x0030100000
Mar 15 23:04:18 Linux kernel: [    7.712227] tegra194-pcie 14100000.pcie:      MEM 0x20a8000000..0x20afffffff -> 0x0040000000
Mar 15 23:04:18 Linux kernel: [    7.720908] tegra194-pcie 14100000.pcie:      MEM 0x2080000000..0x20a7ffffff -> 0x2080000000

After startup, some times I also see lot of messges like

Mar 15 23:04:24 Linux kernel: [   19.548164] nvidia-modeset: Loading NVIDIA UNIX Open Kernel Mode Setting Driver for aarch64  35.4.1  Release Build  (buildbrain@mobile-u64-6422-d7000)  Tue Aug  1 12:45:42 PDT 2023
Mar 15 23:04:24 Linux kernel: [   20.430941] NVRM nvAssertFailedNoLog: Assertion failed: minRequiredIsoBandwidthKBPS <= clientBwValues[DISPLAY_ICC_BW_CLIENT_EXT].minRequiredIsoBandwidthKBPS @ kern_disp_0402.c:111
Mar 15 23:04:24 Linux kernel: [   20.430952] CPU: 6 PID: 735 Comm: kworker/u16:4 Tainted: G           OE     5.10.120-tegra #2
Mar 15 23:04:24 Linux kernel: [   20.430954] Hardware name: Unknown NVIDIA Orin NX Developer Kit/NVIDIA Orin NX Developer Kit, BIOS 4.1-33958178 08/01/2023
Mar 15 23:04:24 Linux kernel: [   20.430965] Workqueue: dce-async-ipc-wq dce_client_async_event_work
Mar 15 23:04:24 Linux kernel: [   20.430969] Call trace:
Mar 15 23:04:24 Linux kernel: [   20.430975]  dump_backtrace+0x0/0x1d0
Mar 15 23:04:24 Linux kernel: [   20.430978]  show_stack+0x30/0x40
Mar 15 23:04:24 Linux kernel: [   20.430983]  dump_stack+0xd8/0x138
Mar 15 23:04:24 Linux kernel: [   20.431031]  os_dump_stack+0x18/0x20 [nvidia]
Mar 15 23:04:24 Linux kernel: [   20.431072]  tlsEntryGet+0x130/0x138 [nvidia]
Mar 15 23:04:24 Linux kernel: [   20.431110]  kdispArbAndAllocDisplayBandwidth_v04_02+0x274/0x288 [nvidia]
Mar 15 23:04:24 Linux kernel: [   20.431148]  kdispInvokeDisplayModesetCallback_KERNEL+0xa8/0xf0 [nvidia]
Mar 15 23:04:24 Linux kernel: [   20.431186]  dceclientHandleAsyncRpcCallback+0x17c/0x2f0 [nvidia]
Mar 15 23:04:24 Linux kernel: [   20.431223]  initVGXSpecificRegistry+0x1dc/0x300 [nvidia]
Mar 15 23:04:24 Linux kernel: [   20.431226]  dce_client_async_event_work+0x8c/0x190
Mar 15 23:04:24 Linux kernel: [   20.431230]  process_one_work+0x1c4/0x4a0
Mar 15 23:04:24 Linux kernel: [   20.431231]  worker_thread+0x54/0x430
Mar 15 23:04:24 Linux kernel: [   20.431233]  kthread+0x148/0x170
Mar 15 23:04:24 Linux kernel: [   20.431235]  ret_from_fork+0x10/0x24
Mar 15 23:04:25 Linux kernel: [   21.227614] cpufreq: cpu4,cur:2100000,set:1984000,set ndiv:155
Mar 15 23:04:35 Linux kernel: [   31.330780] cpufreq: cpu4,cur:2108000,set:1984000,set ndiv:155
Mar 15 23:04:36 Linux kernel: [   32.341998] cpufreq: cpu4,cur:1863000,set:1984000,set ndiv:155
Mar 15 23:04:40 Linux kernel: [   36.363943] cpufreq: cpu4,cur:2168000,set:1984000,set ndiv:155
Mar 15 23:04:43 Linux kernel: [   39.395505] cpufreq: cpu4,cur:1852000,set:1984000,set ndiv:155
Mar 15 23:04:57 Linux kernel: [   52.535213] cpufreq: cpu4,cur:2150000,set:1984000,set ndiv:155
Mar 15 23:04:58 Linux kernel: [   53.546040] cpufreq: cpu4,cur:2139000,set:1984000,set ndiv:155
Mar 15 23:05:00 Linux kernel: [   55.566251] cpufreq: cpu4,cur:2128000,set:1984000,set ndiv:155
Mar 15 23:05:02 Linux kernel: [   57.577291] cpufreq: cpu4,cur:2117000,set:1984000,set ndiv:155
Mar 15 23:05:10 Linux kernel: [   65.665224] cpufreq: cpu4,cur:1861000,set:1984000,set ndiv:155
Mar 15 23:05:15 Linux kernel: [   70.715422] cpufreq: cpu4,cur:2211000,set:1984000,set ndiv:155
Mar 15 23:05:17 Linux kernel: [   72.739699] cpufreq: cpu4,cur:1762000,set:1984000,set ndiv:155
Mar 15 23:05:18 Linux kernel: [   73.750529] cpufreq: cpu4,cur:1861000,set:1984000,set ndiv:155
Mar 15 23:05:19 Linux kernel: [   74.765947] cpufreq: cpu4,cur:2102000,set:1984000,set ndiv:155
Mar 15 23:05:24 Linux kernel: [   79.827418] cpufreq: cpu4,cur:1861000,set:1984000,set ndiv:155
Mar 15 23:05:26 Linux kernel: [   81.854053] cpufreq: cpu4,cur:2108000,set:1984000,set ndiv:155
Mar 15 23:05:29 Linux kernel: [   84.890205] cpufreq: cpu4,cur:1836000,set:1984000,set ndiv:155
Mar 15 23:05:30 Linux kernel: [   85.903129] cpufreq: cpu4,cur:2108000,set:1984000,set ndiv:155
Mar 15 23:05:30 Linux kernel: [   85.903651] cpufreq: cpu4,cur:2127000,set:1984000,set ndiv:155
Mar 15 23:05:32 Linux kernel: [   87.929634] cpufreq: cpu4,cur:2103000,set:1984000,set ndiv:155
Mar 15 23:05:32 Linux kernel: [   87.930156] cpufreq: cpu4,cur:2172000,set:1984000,set ndiv:155
Mar 15 23:05:32 Linux kernel: [   87.931206] cpufreq: cpu4,cur:2156000,set:1984000,set ndiv:155
Mar 15 23:05:33 Linux kernel: [   88.943606] cpufreq: cpu4,cur:2101000,set:1984000,set ndiv:155
Mar 15 23:05:34 Linux kernel: [   89.953780] cpufreq: cpu4,cur:1854000,set:1984000,set ndiv:155
Mar 15 23:05:34 Linux kernel: [   89.954300] cpufreq: cpu4,cur:2148000,set:1984000,set ndiv:155
Mar 15 23:05:36 Linux kernel: [   91.979365] cpufreq: cpu0,cur:2173000,set:1984000,set ndiv:155
Mar 15 23:05:37 Linux kernel: [   92.994909] cpufreq: cpu4,cur:2219000,set:1984000,set ndiv:155
Mar 15 23:05:38 Linux kernel: [   94.001415] cpufreq: cpu0,cur:2170000,set:1984000,set ndiv:155
Mar 15 23:05:38 Linux kernel: [   94.001939] cpufreq: cpu0,cur:1803000,set:1984000,set ndiv:155

On seeing this I have a feeling that the cpu clock frequency might not right - as lot of application problem rising.

Any suggestions on how to fix this problem. Please note that only one board have this problem, others running OK.

kern.log (4.2 MB)
Attach kernel log.

Please check your tegrastats when this error happened.

How to check tegrastats? can you please give some commands, thank you!

sudo tegrastats

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