Jetson_clocks.sh delay required even with R28.2

[Myzhar]

Jetson_clocks.sh delay required even with R28.2

[rbonghi]

Hi @Myzhar ,

I'm following the discussion on jetson_clock.sh 1 minute delay. I think require a delay of 60s for every Jetpack version, but before to upgrade my service I prefer to wait the official reply.

[rbonghi]

My jetsonTX2 have the same problem with the Jetpack 3.2. After start-up the service desn't run correctly the jetson_clock.

SOC family:tegra186  Machine:quill
Online CPUs: 0-5
CPU Cluster Switching: Disabled
cpu0: Gonvernor=schedutil MinFreq=345600 MaxFreq=2035200 CurrentFreq=345600
cpu1: Gonvernor=schedutil MinFreq=345600 MaxFreq=2035200 CurrentFreq=345600
cpu2: Gonvernor=schedutil MinFreq=345600 MaxFreq=2035200 CurrentFreq=345600
cpu3: Gonvernor=schedutil MinFreq=345600 MaxFreq=2035200 CurrentFreq=499200
cpu4: Gonvernor=schedutil MinFreq=345600 MaxFreq=2035200 CurrentFreq=345600
cpu5: Gonvernor=schedutil MinFreq=345600 MaxFreq=2035200 CurrentFreq=345600
GPU MinFreq=140250000 MaxFreq=1300500000 CurrentFreq=140250000
EMC MinFreq=40800000 MaxFreq=1866000000 CurrentFreq=1866000000 FreqOverride=1
Fan: speed=255

The jetsonTX1 doesn't have this error:

SOC family:tegra210  Machine:jetson_tx1
Online CPUs: 0-3
CPU Cluster Switching: Disabled
cpu0: Gonvernor=interactive MinFreq=1734000 MaxFreq=1734000 CurrentFreq=1734000
cpu1: Gonvernor=interactive MinFreq=1734000 MaxFreq=1734000 CurrentFreq=1734000
cpu2: Gonvernor=interactive MinFreq=1734000 MaxFreq=1734000 CurrentFreq=1734000
cpu3: Gonvernor=interactive MinFreq=1734000 MaxFreq=1734000 CurrentFreq=1734000
GPU MinFreq=998400000 MaxFreq=998400000 CurrentFreq=998400000
EMC MinFreq=12750000 MaxFreq=1600000000 CurrentFreq=1600000000 FreqOverride=1
Fan: speed=255

Maybe the problem could be the order of start-up the jetson_tx2, at this time is:

1. sudo nvpmodel -m 0
2. sudo jetson_clocks.sh

A reverse order maybe can fix this error.

[rbonghi]

Hi @Myzhar ,

I temporary add for every jetpack the delay of 60s from boot to start jetson_clock.
I tried to disable the service ondemand, but is without any change. The jetson_performance start but doesn't set correctly the CPU and GPU.

[Kiobod]

Experiencing the same issue. Regardless of wait time, jetson_clocks will not properly set CPU or GPU from boot, despite behaving as normal when interacted with manually.

[rbonghi]

A new release of jetson-stats will control the boot startup and will be more stable than before.

I didn’t test with last release of Jetpack, but maybe we will close this issue.

I’m thinking to add in jtop a countdown