From owner-freebsd-acpi@FreeBSD.ORG Tue Jan 6 03:57:23 2015 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 99576D02; Tue, 6 Jan 2015 03:57:23 +0000 (UTC) Received: from mail-ig0-x22d.google.com (mail-ig0-x22d.google.com [IPv6:2607:f8b0:4001:c05::22d]) (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 5F8AB2705; Tue, 6 Jan 2015 03:57:23 +0000 (UTC) Received: by mail-ig0-f173.google.com with SMTP id r2so3624458igi.0; Mon, 05 Jan 2015 19:57:22 -0800 (PST) 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=0lML7PtDBHct/IPvKiRbeHWUlyqZoIRHkhOtqY9ZG+g=; b=OwaHBWYqDDANFCncUj+0okWuyglbOQx+KLnxS89OYR7q0D12RnnWT5+/FG4JtbLoFD 7SoJigR9evAzm9n58dy7dAVP4r6bBMoCMq8Kfdb0ZTa9P24sZcIUPZgFc3U+3nJWptHL Q/ssjaUfF/PUckvrVQmr2nutKlC/N1ORNlEhzif9CL3r4B/nYdRhCVWax30krkMfzART J6woPr4fxPHhcwg6Bp7iAK+4JhIW15VN+0jrpzM0vnP4x97I5eEWjQndVkihmO57HaUB EsUrHFePYUM7GI0PGwWo7kYEC8+742aNbFEyFYFgYGc1Z6dc/+KdKDJrIVhOjxtJrTCH iAIg== MIME-Version: 1.0 X-Received: by 10.107.168.18 with SMTP id r18mr82997437ioe.76.1420516642639; Mon, 05 Jan 2015 19:57:22 -0800 (PST) Sender: kob6558@gmail.com Received: by 10.107.52.19 with HTTP; Mon, 5 Jan 2015 19:57:22 -0800 (PST) In-Reply-To: <54AB32AD.1070409@ignoranthack.me> References: <54AB32AD.1070409@ignoranthack.me> Date: Mon, 5 Jan 2015 19:57:22 -0800 X-Google-Sender-Auth: hoUEPzPm0hFGGvK_DxWtlIw3sY4 Message-ID: Subject: Re: Haswell, i3, fail to acpi_throttle fail From: Kevin Oberman To: Sean Bruno Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-acpi@freebsd.org" X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jan 2015 03:57:23 -0000 On Mon, Jan 5, 2015 at 4:56 PM, Sean Bruno wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > acpi_throttle0: on cpu0 > acpi_throttle0: P_CNT from P_BLK 0x1810 > est0: on cpu0 > acpi_throttle1: on cpu1 > acpi_throttle1: failed to attach P_CNT > device_attach: acpi_throttle1 attach returned 6 > est1: on cpu1 > acpi_throttle2: on cpu2 > acpi_throttle2: failed to attach P_CNT > device_attach: acpi_throttle2 attach returned 6 > est2: on cpu2 > acpi_throttle3: on cpu3 > acpi_throttle3: failed to attach P_CNT > device_attach: acpi_throttle3 attach returned 6 > est3: on cpu3 > > > The call to acpi_bus_alloc_gas() in acpi_throttle.c seems to be failing > to attach. What should I be poking at here? > Excellent! Throttling is counter-productive and always has been. It's been at least 5 years since mav@ posted his excellent wiki article on power management which demonstrated the futility of throttling. More important, even if it was useful for power management, it has long since been superseded by TCC. Intel tried to make the purpose of TCC clear by the name: Thermal Control Circuit. So it is ineffective for power management and FreeBSD still tries to use it. Looks like the vendor broke ACPI so throttling won't work. Or, maybe, Intel simply removed it as unused legacy. Don't worry. Be happy! Make sure that hint.acpi_throttle.0.disabled=1 is set in /boot/loader.conf to disable it. I'd strongly urge that you also disable P4TCC with hint.p4tcc.0.disabled=1. It will trivially improve battery life and will seriously compromise performance if powerd is enabled. It can also cause hangs with elevated C-states on some systems. If you really want to improve battery life with minimal impact on performance, set both performance_cx_lowest and economy_cx_lowest to "Cmax" in rc,conf. No other technique is more effective in saving power than C-states. EST helps, too, but not nearly so much and with a greater impact on performance. If you have not read it, read the wiki article at https://duckduckgo.com/l/?kh=-1&uddg=https%3A%2F%2Fwiki.freebsd.org%2FTuningPowerConsumption -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com