That script is turning on the cores only if "${SOCFAMILY}" != "tegra186"
Is there a security reason why cores are not enabled when the SOC family is tegra186?
I would like to know if I could remove that validation without security risks.
Also check the output of: cat /proc/cmdline
…and look to see if there is an “isolcpus” parameter. This might tell the system some cores are disabled except when manually scheduled. Not sure if that would affect what jetson_clocks.sh does, but probably worth checking.
Hello @DaneLLL, thanks for your reply
I’m checking the jetson_clocks file you suggested and it also has the condition to not turn on the cpus if SOCFAMILY = "tegra186"
Note: I found a jetson_clocks.sh file
This is all the do_hotplug() function
do_hotplug()
{
case "${ACTION}" in
show)
echo "Online CPUs: `cat /sys/devices/system/cpu/online`"
;;
store)
for file in /sys/devices/system/cpu/cpu[0-9]/online; do
store "${file}"
done
;;
*)
if [ "${SOCFAMILY}" != "tegra186" ]; then
for file in /sys/devices/system/cpu/cpu*/online; do
if [ `cat $file` -eq 0 ]; then
echo 1 > "${file}"
fi
done
fi
esac
}