Norikatsu Shigemura wrote: > On Sun, 12 Sep 2010 11:12:20 +0300 > Alexander Motin <mav_at_freebsd.org> wrote: >>>>> PROCESSOR-0696 [257314] cpu_cx_cst : acpi_cpu3: C2[1] not available. >>>>> PROCESSOR-0730 [257314] cpu_cx_cst : acpi_cpu3: Got C3 - 245 latency >>>> I think the issue is that C2 is not available for some reason and thus >>>> C3 can't be used either. The way to tell is to use acpidump and look for >>>> the CPU objects' _CST fields. >>> The "not available" message means that transition latency is defined too high. >>> That is, in this case latency is greater than 100 for C2. >> Just an idea. Limits of 100 and 1000 are defined for detection of >> C-states using P_LVLx_LAT registers. Because _CST explicitly specifies > > Oops! I forgot. Thank you, I tried. > But cx_lowest is not changed: > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > $ sysctl -a | grep cx > hw.acpi.cpu.cx_lowest: C1 > dev.cpu.0.cx_supported: C1/3 C2/245 > dev.cpu.0.cx_lowest: C1 > dev.cpu.0.cx_usage: 100.00% 0.00% last 3641us > dev.cpu.1.cx_supported: C1/3 C2/245 > dev.cpu.1.cx_lowest: C1 > dev.cpu.1.cx_usage: 100.00% 0.00% last 798us > dev.cpu.2.cx_supported: C1/3 C2/245 > dev.cpu.2.cx_lowest: C1 > dev.cpu.2.cx_usage: 100.00% 0.00% last 158us > dev.cpu.3.cx_supported: C1/3 C2/245 > dev.cpu.3.cx_lowest: C1 > dev.cpu.3.cx_usage: 100.00% 0.00% last 227us > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - hw.acpi.cpu.cx_lowest has default in C1. Have you tried to rise it via sysctl? -- Alexander MotinReceived on Sun Sep 12 2010 - 07:29:59 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:07 UTC