> I have now found a very hacky workaround that is slightly better than > disabling C3 altogether; making C3 exclusive to one core at a time. It > seems to kill the noise and the system now spends 50% in C3, instead of > 0%. I suspect it won't do much of C3 if only one core is idle this way. Most likely you just disabled C3 this way in a way invisible to software. -Andi _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
