Most recent kernel where this bug did *NOT* occur:2.6.20.3 Distribution: Slackware Linux 11 (current) Hardware Environment: Lenovo 3000 C100 (Pentium M 1.7GHz Dothan) Problem Description: Hi, i have some problems with CPU Throttling and power states of my CPU. I get this report...CPU rest cat /proc/acpi/processor/CPU0/power active state: C4 max_cstate: C8 bus master activity: 00000000 maximum allowed latency: 2000 usec states: C1: type[C1] promotion[C2] demotion[--] latency[001] usage[00000010] duration[00000000000000000000] C2: type[C2] promotion[C3] demotion[C1] latency[001] usage[00502851] duration[00000000000275479975] C3: type[C3] promotion[C4] demotion[C2] latency[085] usage[00000431] duration[00000000000001178354] *C4: type[C3] promotion[--] demotion[C3] latency[185] usage[00053417] duration[00000000000142463775] It should be ok...but... when i start...for example...kernel compilation...state of my busy CPU is this: active state: C2 max_cstate: C8 bus master activity: 80000001 maximum allowed latency: 2000 usec states: C1: type[C1] promotion[C2] demotion[--] latency[001] usage[00000010] duration[00000000000000000000] *C2: type[C2] promotion[C3] demotion[C1] latency[001] usage[00576754] duration[00000000000315228566] C3: type[C3] promotion[C4] demotion[C2] latency[085] usage[00004034] duration[00000000000009452622] C4: type[C3] promotion[--] demotion[C3] latency[185] usage[00099626] duration[00000000000262585789] My question is this: Why my CPU is not in C1 state, when works on 100%? And where is C0 state? I have problems with Throttling function too. my command: echo -n 4 > /proc/acpi/processor/CPU0/throttling state T4 is activated, but only a few seconds and then it goes back to T0. Is this ok? I heard, that Throttling is active only in C0 state. my CPU power management: CPU Frequency scaling ondemand gowernor ACPI Processor P-State driver Intel Enhanced SpeedStep
You claim that this bug was present in 2.6.20.3 and that it was not present in 2.6.20.3. Please clarify?
Sorry, bug is present in 2.6.20.X (my current kernel is 2.6.20.3, this bug is present in 2.6.20.3 too).
OK. And are you able to identify the most recent kernel which did not have this bug? So we can work out when it was introduced? Thanks.
Please reopen this bug if: - it is still present with kernel 2.6.22 and - you can provide the requested information.
This bug is present in kernel 2.6.22(.1,2,3,4,5) too :(
Antonin, this is clearly a dup of bug# 8229 which was rejected by Len. Please reopen bug# 8229 and provide the info Len need... thanks! *** This bug has been marked as a duplicate of bug 8229 ***