http://bugzilla.kernel.org/show_bug.cgi?id=13911 Corrado Zoccolo <czoccolo@xxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |czoccolo@xxxxxxxxx --- Comment #4 from Corrado Zoccolo <czoccolo@xxxxxxxxx> 2009-08-19 08:23:24 --- C states are managed by cpuidle, not cpufreq. If the problem persists with 'performance' cpufreq governor, when C1E is enabled, then cpufreq is definitely not guilty. C1E state is a deep sleep state that is selected automatically in some occasions, when entering C1, so the OS has very low control on it. In particular, the latency control usually adopted to select the proper C state to enter is bypassed, since the hardware exports a single state, with varying latency. -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- 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
