From owner-freebsd-acpi@FreeBSD.ORG Fri Sep 3 06:36:52 2010 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9343B1065895 for ; Fri, 3 Sep 2010 06:36:52 +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 DBB478FC19 for ; Fri, 3 Sep 2010 06:36:51 +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 JAA10910; Fri, 03 Sep 2010 09:36: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 1OrPcP-0006wE-Lh; Fri, 03 Sep 2010 09:19:21 +0300 Message-ID: <4C809369.1090804@icyb.net.ua> Date: Fri, 03 Sep 2010 09:19:21 +0300 From: Andriy Gapon 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: kuba References: <20100901042852.P29840@sola.nimnet.asn.au> <4C801EE0.50505@gmail.com> In-Reply-To: <4C801EE0.50505@gmail.com> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org, Ian Smith Subject: Re: acpi shows wrong battery state (fwd) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Sep 2010 06:36:52 -0000 on 03/09/2010 01:02 kuba said the following: > > > > Take a look at these tunables: > > debug.acpi.ec.timeout: 750 > > debug.acpi.ec.polled: 0 > > debug.acpi.ec.burst: 0 > > > > Perhaps increasing timeout would help? > > Increasing timeout didn't help at all :( BTW, there is surprisingly little information in the above statement. So, what exactly did you do to increase the value? What max value did you try? I hope not 751? :-) Did you try enabling burst tunable? -- Andriy Gapon