http://bugzilla.kernel.org/show_bug.cgi?id=14190
--- Comment #30 from ykzhao <yakui.z...@intel.com> 2010-02-22 01:46:41 ---
The issue on this box is very weird.
>From the test in comment #25 it seems that it can work well after using the
following boot option:
>processor.max_cstate =1 (only C1 is used)
>nolapic_timer : C1/C2/C3 is used. The cpu will be waked up from C-state
periodically and local APIC timer is disabled.
>processor.max_cstate=2 : C1/C2 is used.
When the system is in C2/C3 state, the local APIC timer is also disabled.
But the system can't work well without the boot option of "nolapic_timer" if
the system can enter the deep C-state(C3). The only difference with/without the
boot option of "nolapic_timer" is that the timer will bring the cpu out of deep
C-state periodically.
Hi, Venki
Any idea about this issue?
thanks.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
Download Intel® 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
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
