From owner-freebsd-current@FreeBSD.ORG Sun Sep 12 08:12:44 2010 Return-Path: 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 CA092106566B for ; Sun, 12 Sep 2010 08:12:44 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 528F28FC17 for ; Sun, 12 Sep 2010 08:12:43 +0000 (UTC) Received: by bwz20 with SMTP id 20so336941bwz.13 for ; Sun, 12 Sep 2010 01:12:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=zx3UopHs2kS6fHtJLWbjMG7a+S/4sZgb0Au9HZmmMxw=; b=aTsKpD076+OeAvtmO6vImi0JXRwoiRGeaB0kQvKwaUuiqtdh/TBjaDepdjAG69Qkgt sWaZ7wvU4GqoN936Gmov5RmYb4EuwxFHOsNYyiS81uNlrT1orYbS4jmJPkTse+PT3aTw MNMoPu1lAozunIpIiJLCxwGXexs362vTxjRzs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; b=SIWnZ3ZNbgvG+uy+bMH4lfXeamC06YE1LQDNhYkYN+QGLJDC4j7SMl0gYPiEiTX7V9 LuWhvRNReczzEzoOLKPznqc1OWNnC5agMvve34TWm11HTsSfO9HrOMepfn9UNc7EGqGq 2/utsAaxObjjyzRzaILCAJbWiTDzfgOy0rojI= Received: by 10.204.117.136 with SMTP id r8mr2068164bkq.119.1284279158282; Sun, 12 Sep 2010 01:12:38 -0700 (PDT) Received: from mavbook2.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id y2sm3513608bkx.8.2010.09.12.01.12.36 (version=SSLv3 cipher=RC4-MD5); Sun, 12 Sep 2010 01:12:37 -0700 (PDT) Sender: Alexander Motin Message-ID: <4C8C8B64.8020907@FreeBSD.org> Date: Sun, 12 Sep 2010 11:12:20 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: Andriy Gapon , Norikatsu Shigemura , FreeBSD-Current References: <4C8BCAC5.5050008@root.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Sep 2010 08:12:44 -0000 Andriy Gapon wrote: > on 11/09/2010 21:30 Nate Lawson said the following: >>> PROCESSOR-0311 [255895] cpu_attach : acpi_cpu3: P_BLK at 0x410/6 >>> 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 which states are available, these limitations may not apply there. I would try to comment these checks in acpi_cpu_cx_cst() and look what happen. At least I haven't found in ACPI 3.0 specification any latency limits applied to _CST. -- Alexander Motin