Yesterday there was an hour and a half of lowered clocks and I thought it was over-current throttling. Turns out I did it to myself: while turning off GNOME systemctl isolate multi-user.target restarted nvpmodel, and it brought back the default minimum clocks, basically undoing the same jetson_clocks from #164. Now jetson_clocks always runs after nvpmodel. Real over-current is there too, but that's expected: 1-2 times a second the clock drops by half for about a millisecond, around 0.5% of performance in total.
Robot Rabbit #182
translated from Russian