From owner-freebsd-current@FreeBSD.ORG  Sun Sep 12 15:22:43 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id BEBA6106564A;
	Sun, 12 Sep 2010 15:22:43 +0000 (UTC) (envelope-from avg@icyb.net.ua)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
	by mx1.freebsd.org (Postfix) with ESMTP id A00BF8FC17;
	Sun, 12 Sep 2010 15:22:42 +0000 (UTC)
Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua
	[212.40.38.100])
	by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id SAA28260;
	Sun, 12 Sep 2010 18:22:40 +0300 (EEST)
	(envelope-from avg@icyb.net.ua)
Received: from localhost.topspin.kiev.ua ([127.0.0.1])
	by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD))
	id 1OuoO8-000FyD-Ja; Sun, 12 Sep 2010 18:22:40 +0300
Message-ID: <4C8CF03F.1050902@icyb.net.ua>
Date: Sun, 12 Sep 2010 18:22:39 +0300
From: Andriy Gapon <avg@icyb.net.ua>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US;
	rv:1.9.2.8) Gecko/20100822 Lightning/1.0b2 Thunderbird/3.1.2
MIME-Version: 1.0
To: Alexander Motin <mav@FreeBSD.org>
References: <4C8BCAC5.5050008@root.org>	<mailpost.1284277196.1767764.83548.mailing.freebsd.current@FreeBSD.cs.nctu.edu.tw>	<4C8C8B64.8020907@FreeBSD.org>	<20100912182625.c49d3f1d.nork@FreeBSD.org>	<4C8C9F06.4090505@icyb.net.ua>	<20100912190537.621e357e.nork@FreeBSD.org>	<20100912190952.8c0d5726.nork@FreeBSD.org>
	<20100912192518.e791c191.nork@FreeBSD.org>
	<4C8CAC01.70004@icyb.net.ua> <4C8CAD7D.50602@FreeBSD.org>
In-Reply-To: <4C8CAD7D.50602@FreeBSD.org>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: FreeBSD-Current <freebsd-current@FreeBSD.org>,
	Norikatsu Shigemura <nork@FreeBSD.org>
Subject: Re: CPU C-state storange on Panasonic TOUGH BOOK CF-R9
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Sep 2010 15:22:43 -0000

on 12/09/2010 13:37 Alexander Motin said the following:
> Andriy Gapon wrote:
>> acpi_lid0: Lid closed
>> em0: Link is up 1000 Mbps Full Duplex
>> PROCESSOR-0722 [402244] cpu_cx_cst            : acpi_cpu0: Got C2 - 245 latency
>> PROCESSOR-0722 [403097] cpu_cx_cst            : acpi_cpu1: Got C2 - 245 latency
>> PROCESSOR-0722 [403855] cpu_cx_cst            : acpi_cpu2: Got C2 - 245 latency
>> PROCESSOR-0722 [405022] cpu_cx_cst            : acpi_cpu3: Got C2 - 245 latency
>>
>> Maybe because of this?
>> It seems like you do something and ACPI disables C3, leaving only C2/
> 
> One strange thing. During boot it can be seen:
> acpi_cpu0: Got C2 - 205 latency
> acpi_cpu0: Got C3 - 245 latency
> , but after boot in sysctl we can see:
> dev.cpu.0.cx_supported: C1/3 C2/245
> 
> It respecting latency it looks like not C3 got lost, but C2. AFAIR,
> sysctl numbers C-states completely abstract, just as array indexes. So
> thing reported as C2 could instead be C3, while C2 is absent for some
> reason.

Observations are correct, but incomplete; the conclusions are wrong.
At the end of the boot there are message like this one:
PROCESSOR-0722 [402244] cpu_cx_cst            : acpi_cpu0: Got C2 - 245 latency
This is a result of re-evaluation of _CST because of a notification from ACPI.

-- 
Andriy Gapon