This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
fuss:linux [2020/02/07 21:03] – [Allow Binding Privileged Ports] office | fuss:linux [2020/02/25 05:07] – [Determining the Last Power On Method] office | ||
---|---|---|---|
Line 1101: | Line 1101: | ||
will print the last wake-up type. | will print the last wake-up type. | ||
+ | |||
+ | ====== Issues with Stuck Cores ====== | ||
+ | |||
+ | It may happen that logs fill up with messages indicating that some power management policy cannot be enforced on a given CPU core: | ||
+ | < | ||
+ | cpufreqd: cpufreqd_loop | ||
+ | cpufreqd: cpufreqd_set_profile | ||
+ | </ | ||
+ | |||
+ | It may be that the CPU core is simply stuck and may need replugging. The following two commands will take the CPU offline and the next one will start the CPU back up: | ||
+ | <code bash> | ||
+ | echo " | ||
+ | echo " | ||
+ | </ | ||
+ | |||
+ | In doing so, the power management issue seems to be resolved. | ||