From owner-freebsd-arch@FreeBSD.ORG Fri May 9 20:36:03 2014 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B612B38D; Fri, 9 May 2014 20:36:03 +0000 (UTC) Received: from mail-qc0-x230.google.com (mail-qc0-x230.google.com [IPv6:2607:f8b0:400d:c01::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5A703CA; Fri, 9 May 2014 20:36:03 +0000 (UTC) Received: by mail-qc0-f176.google.com with SMTP id r5so5242998qcx.35 for ; Fri, 09 May 2014 13:36:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=nj3nn7zXA86NwjVh1fr7cUxbCzjDb/XQbOKNBgghR6o=; b=k8+mt1lNssLHLK9PMYYHSnBpbwdjQdF3RWJ3SAPvp/BWiadPsEUww3OTOVf5z3hKgp znqgnb/dV16VtxKDCnHNP6zi7rNQplPJqJ4OSQzyWt9B/mHfAxXg8djsRgEOwZ5Bv0w6 NuMdEGlbNeY2ptnthTEJJqH/4q+ZvaQymHILE3oZ99vGsUIX8dBFqnSI4nKZcv2k8MK2 kaOFgOvHHrvb7CpCsM95RbUoG9PWrxGWhNs031T9gUBIZnDO/AW2cKb62CGMA4Vlotkp vOCdudFlBsYwLnXZ7vcH70lb9PkB4hFB1T+vk6X0eR3H4a7gDnHtAI6GrcFtMJqIvjOc KB3Q== MIME-Version: 1.0 X-Received: by 10.224.16.199 with SMTP id p7mr18507242qaa.76.1399667762540; Fri, 09 May 2014 13:36:02 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.191.201 with HTTP; Fri, 9 May 2014 13:36:02 -0700 (PDT) In-Reply-To: References: <20140505011654.O11699@sola.nimnet.asn.au> <2223.1399233644@critter.freebsd.dk> <20140505153421.W11699@sola.nimnet.asn.au> <85787.1399271121@critter.freebsd.dk> <20140505163316.R11699@sola.nimnet.asn.au> <7681.1399629328@critter.freebsd.dk> Date: Fri, 9 May 2014 13:36:02 -0700 X-Google-Sender-Auth: buWpk3LJagVjuFoJaUfq78cAcNg Message-ID: Subject: Re: proposal: set default lid state to S3, performance/economy Cx states to Cmax From: Adrian Chadd To: Kevin Oberman Content-Type: text/plain; charset=UTF-8 Cc: Poul-Henning Kamp , "freebsd-arch@freebsd.org" , Ian Smith , "freebsd-acpi@freebsd.org" X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 May 2014 20:36:03 -0000 cool! next; # pkg install intel-pcm # kldload cpuctl # pcm.x 1 See what it reports. -a On 9 May 2014 13:12, Kevin Oberman wrote: > On Fri, May 9, 2014 at 3:25 AM, Adrian Chadd wrote: >> >> Hi! >> >> On 9 May 2014 02:55, Poul-Henning Kamp wrote: >> > In message <20140505163316.R11699@sola.nimnet.asn.au>, Ian Smith writes: >> >>On Mon, 5 May 2014 06:25:21 +0000, Poul-Henning Kamp wrote: >> >> > In message <20140505153421.W11699@sola.nimnet.asn.au>, Ian Smith >> >> > writes: >> >> > >> >> > Do we have a canonical page with all the various workarounds one >> >> > should >> >> > attempt in order to get suspend/resume to work ? >> >> >> >>Bits scattered all over the place. For the above there's: >> > >> > So based on various scattered hints, I tried booting the VT kernel, >> > r265336, on my Thinkpad T430s and that seems to fix both Suspend/Resume >> > and also console switching. >> > >> > Much appreciated! >> > >> > I'll keep an eye on any peripheral bogons as I used it now. >> >> Woo! >> >> Would you mind populating http://wiki.freebsd.org/Laptops with your >> details? >> >> Thanks! >> >> >> -a > > > Excellent! This alone will save batteries and also lower the carbon > footprint of FreeBSD servers! > > Just to clarify the various settings of *_cx_lowest in rc.conf, HIGH is > obvious. At one time, LOW was also obvious, but then some vendors started > shipping BIOS that "skipped" some C-states in different power conditions. > E.g. C1, C2 and C3 when on Battery, but only C1 and C3 when on AC. This > scenario was common on Sandybridge systems (like my T320). Skipping a state > broke "LOW" as it only saw C1 when on AC. Thus, Cmax appeared. Cmax is > simply C8. It is just easier ot remember then C8. The code was re-written to > ignore "missing" C-states and try all possible C-states until C8 was > reached. > > Why "LOW" was not just changed to deal with this I don't understand, but > Cmax (or C8) is recommended to gain the maximum power savings from > C-states. > > On AC power: > dev.cpu.0.cx_supported: C1/1/1 C2/3/104 > dev.cpu.0.cx_lowest: C8 > dev.cpu.0.cx_usage: 8.86% 91.13% last 2685us > > On battery: > dev.cpu.0.cx_supported: C1/1/1 C2/2/80 C3/3/109 > dev.cpu.0.cx_lowest: C8 > dev.cpu.0.cx_usage: 3.09% 0.74% 96.15% last 728us > > Note the supported list on AC? > C2/3/104 The first part, "C2", is what the OS labels that second state. The > next part, "3", is the ACPI number of this state. On AC, this system has no > C-state 2, so FreeBSD call the ACPI state 3 "C2". Oh, the last number is the > number of clock cycles required to get into/out of that state. so in my > case, when on battery, my CPU goes ot C2 after being halted for 80 clock > cycles and C3 after 109. I hope this makes sense to everyone. I'm not really > sure that it does to me! > -- > R. Kevin Oberman, Network Engineer, Retired > E-mail: rkoberman@gmail.com