https://bugzilla.kernel.org/show_bug.cgi?id=75121 --- Comment #17 from Doug Smythies <dsmythies@xxxxxxxxx> --- (In reply to Dirk Brandewie from comment #16) > (In reply to Doug Smythies from comment #15) > > Hi Dirk: Did you ever figure out for certain why some had the CPU freq > > remains high after suspend issue? It remains unclear to me, and I do not > > know how to even try to re-create here on my test computer. > > > > I could make it happen occasionally on my ivy bridge laptop test system. > > I think it have to the hardware coordination on the chip but I haven't > proven that. > I have figured out how to "suspend" my test computer. I have tried a few times, but so far haven't been able to re-create the issue. I wanted to be able to re-create the issue, as a base line reference, so that I would know how far I can adjust C0_WEIGHT or C0_MINIMUM and still have the issue never occur. It still doesn't make sense to me that the intel_pstate driver would work fine before but not after a "suspend". If the root issue is some hardware coordination on the chip, then shouldn't that be fixed (if possible via whatever re-initialization) rather than messing with the intel_pstate servo loop? If it is not some hardware coordination on the chip, but rather due to some flaw in the servo loop, then we should be able to re-create the issue without any intervening "suspend". -- You are receiving this mail because: You are the assignee for the bug. -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
