https://bugzilla.kernel.org/show_bug.cgi?id=15675


Len Brown <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO
                 CC|                            |[email protected]
         Regression|No                          |Yes
            Summary|Very high power             |Starting 2.6.32, C2 is used
                   |consumption, 40000+ wakeups |and results in 40000
                   |from idle per second --     |wake/sec -- Lenovo 3000
                   |Lenovo 3000 N200            |N200




--- Comment #20 from Len Brown <[email protected]>  2010-04-03 21:13:14 ---
This looks exactly like bug 14742.

Linux 2.6.31 uses C1 and avoids C2.
Linux 2.6.32 (and later) includes a logic update in cpuidle
which causes it to use C2 and thrash with C0 time and huge wakeups/sec.

(Thus, marking this as a regression, even though it is because
 2.6.32 has exposed a latent bug)

"idle=halt" works around the problem.
Please verify that "processor.max_cstate=1" also
works around the problem. (it is like idle=halt,
but will allow using mwait in C1 instead of HLT)

> Intel Pentium Dual Core T2370 @1.73GHz

Please paste here the output from "cat /proc/cpuinfo"

Also, regarding bug 15377 -- that one is similar, but
has some differences.  Please boot without enabling
the network interfaces and run powertop -d to see if
the problem is still there.  If no, then enable the network
and if that provokes the failure.

On a failing kernel, please attach the output from "dmesg -s64000".
Please attach the standard output from acpidump,
plus a copy of the files in /sys/firmware/acpi/tables/dynamic/*

Finally, if you happen to have a Windows partition on this box,
please run perfmon, add the C2 counter and report what you see.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
acpi-bugzilla mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to