From owner-freebsd-acpi@FreeBSD.ORG Sun Jul 24 03:47:15 2005 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 66F9516A420 for ; Sun, 24 Jul 2005 03:47:15 +0000 (GMT) (envelope-from kjelderg@gmail.com) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9543943D49 for ; Sun, 24 Jul 2005 03:47:14 +0000 (GMT) (envelope-from kjelderg@gmail.com) Received: by rproxy.gmail.com with SMTP id i8so222364rne for ; Sat, 23 Jul 2005 20:47:13 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=pi7vWuO1HKHSVxdFSapYA96k7xcIF7XPWwQMoOvcYyl9zSMXV43PhK7rM1NV/gy7A7ORLjJzZDXOJwxb7a8CdaInp+PX7yJAF3IQUloEOJNViFKMkUQosxqa8GgsclWokNCF0VZVB11s+ttQ4DnSEj/SJ14kPi/gFCjLdsGTThk= Received: by 10.38.208.46 with SMTP id f46mr398521rng; Sat, 23 Jul 2005 20:47:13 -0700 (PDT) Received: by 10.38.101.41 with HTTP; Sat, 23 Jul 2005 20:47:13 -0700 (PDT) Message-ID: Date: Sun, 24 Jul 2005 12:47:13 +0900 From: Eric Kjeldergaard To: Nate Lawson In-Reply-To: <42E29CAA.1020007@root.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <42E1481F.5040306@root.org> <20050723133819.36efb537.lists@yazzy.org> <42E29CAA.1020007@root.org> Cc: acpi@freebsd.org, Marcin Jessa , freebsd-current@freebsd.org Subject: Re: acpi battery rework patch X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Eric Kjeldergaard List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jul 2005 03:47:15 -0000 On 7/24/05, Nate Lawson wrote: > Marcin Jessa wrote: > > On Sat, 23 Jul 2005 19:00:01 +0900 > > Eric Kjeldergaard wrote: > >>>Please test to be sure your battery status works as usual, along with= =20 > >>>any apps. Since most apps (xbatt, gnome, etc.) use the apm compat=20 > >>>layer, they should work as before with no recompilation needed. > >=20 > >=20 > >>-CURRENT as of 23/07/2005, does not compile. > >=20 > >=20 > > Prolly because it's for 6.0, not 7.0 >=20 > Sorry, the problem was I left a file out of the diff. I just committed= =20 > the patch so please just cvsup and test from 7-CURRENT. >=20 > Thanks, > --=20 > Nate >=20 Excellent. compiled and appears working. It does however have different values than the old system for some of the sysctl variables. I get hw.acpi.battery.life: 98 hw.acpi.battery.time: 0 hw.acpi.battery.state: 0 hw.acpi.battery.units: 1 hw.acpi.battery.info_expire: 5 when plugged in. But used to get time as -1 when plugged in and I think state may have been 1 when plugged in before (less sure about that than the time). Thanks for the enormous amount of work your efforts are very much appreciated, Eric --=20 If I write a signature, my emails will appear more personalised. From owner-freebsd-acpi@FreeBSD.ORG Sun Jul 24 06:21:31 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D243416A41F for ; Sun, 24 Jul 2005 06:21:31 +0000 (GMT) (envelope-from takawata@init-main.com) Received: from sana.init-main.com (104.194.138.210.bn.2iij.net [210.138.194.104]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DAE043D45 for ; Sun, 24 Jul 2005 06:21:31 +0000 (GMT) (envelope-from takawata@init-main.com) Received: from init-main.com (localhost [127.0.0.1]) by sana.init-main.com (8.13.3/8.13.1) with ESMTP id j6O6ISWx093600; Sun, 24 Jul 2005 15:18:28 +0900 (JST) (envelope-from takawata@init-main.com) Message-Id: <200507240618.j6O6ISWx093600@sana.init-main.com> To: Nate Lawson In-reply-to: Your message of "Sat, 23 Jul 2005 12:38:18 MST." <42E29CAA.1020007@root.org> Date: Sun, 24 Jul 2005 15:18:28 +0900 From: Takanori Watanabe Cc: freebsd-acpi@freebsd.org Subject: Re: acpi battery rework patch 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: Sun, 24 Jul 2005 06:21:31 -0000 In message <42E29CAA.1020007@root.org>, Nate Lawson さんいわく: >Marcin Jessa wrote: >> On Sat, 23 Jul 2005 19:00:01 +0900 >> Eric Kjeldergaard wrote: >>>>Please test to be sure your battery status works as usual, along with >>>>any apps. Since most apps (xbatt, gnome, etc.) use the apm compat >>>>layer, they should work as before with no recompilation needed. >> >> >>>-CURRENT as of 23/07/2005, does not compile. >> >> >> Prolly because it's for 6.0, not 7.0 > >Sorry, the problem was I left a file out of the diff. I just committed >the patch so please just cvsup and test from 7-CURRENT. > I don't tried yet, but devclass battery should be shared between any kind of batteries in your way. So move acpi_cmbat_devclass into acpi_battery.c and change its name to acpi_battery_devclass. From owner-freebsd-acpi@FreeBSD.ORG Sun Jul 24 09:08:42 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8719216A41F; Sun, 24 Jul 2005 09:08:42 +0000 (GMT) (envelope-from matthias@staatsfeind.org) Received: from outpost.cyberadaptor.de (outpost.cyberadaptor.de [213.133.123.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F76543D46; Sun, 24 Jul 2005 09:08:41 +0000 (GMT) (envelope-from matthias@staatsfeind.org) Received: from p54ae2dee.dip0.t-ipconnect.de ([84.174.45.238] helo=mail.xhr.gi.mrm) by outpost.cyberadaptor.de with asmtp (Exim 3.35 #1 (Debian)) id 1DwcTQ-00037V-00; Sun, 24 Jul 2005 11:08:40 +0200 Received: from c0re.xhr.gi.mrm (c0re [10.253.195.101]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.xhr.gi.mrm (Postfix) with ESMTP id A607046A6E; Sun, 24 Jul 2005 11:08:38 +0200 (CEST) Received: by c0re.xhr.gi.mrm (Postfix, from userid 1000) id F03AACE; Sun, 24 Jul 2005 11:08:29 +0200 (CEST) Date: Sun, 24 Jul 2005 11:08:29 +0200 From: Matthias Schmidt To: freebsd-acpi@freebsd.org, freebsd-mobile@freebsd.org Message-ID: <20050724090828.GA1841@c0re.xhr.gi.mrm> Mail-Followup-To: freebsd-acpi@freebsd.org, freebsd-mobile@freebsd.org, schmidtm@mathematik.uni-marburg.de Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Cc: schmidtm@mathematik.uni-marburg.de Subject: Strange problems with ACPI/APM on IBM Thinkpad T43 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: Sun, 24 Jul 2005 09:08:42 -0000 [ Please CC me, I'm not subscribed to freebsd-acpi ] Hi, I experienced some strange problems with ACPI or APM on my IBM Thinkpad T43 (Type 2668) and FreeBSD 6.0-BETA. To enable suspend2RAM I tried the following things: o ACPI If ACPI is enabled, suspend work without problems. If I try to resume the machine freezes and the following message is displayed: ioapic_suspend: not implemented! ioapic_suspend: not implemented! [...] ioapic_suspend: not implemented! acpi_bus_number: can't get _ADR [freeze] If I set hint.apic.0.disabled to 1 the laptop resumes fine. Now the strange thing: Everything is incredible slow. Normal working/typing is nearly impossible. Why? o APM I disabled ACPI and enabled APM to get Suspend working. With the GENERIC kernel [2] Suspend/Resume is working fine. But I can't suspend while X is running, I have to switch back to console. If I compile a custom kernel [3] to get rid of some debugging stuff Suspend with APM isn't working anymore!? Did I something wrong? Maybe it's a problem with the builtin ICH6M SATA Controller? For further information: My dmesg [1], the GENERIC kernel config [2], my own kernel config [3] and the output of pciconf -l -v [4]. Greets Matthias [1] http://www.mathematik.uni-marburg.de/~schmidtm/dmesg [2] http://www.mathematik.uni-marburg.de/~schmidtm/GENERIC [3] http://www.mathematik.uni-marburg.de/~schmidtm/C0RE [4] http://www.mathematik.uni-marburg.de/~schmidtm/pciconf From owner-freebsd-acpi@FreeBSD.ORG Sun Jul 24 10:30:48 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 60C7E16A41F for ; Sun, 24 Jul 2005 10:30:48 +0000 (GMT) (envelope-from ben@bjencks.net) Received: from bjencks.net (sub20-225.member.dsl-only.net [63.105.20.225]) by mx1.FreeBSD.org (Postfix) with SMTP id A9DF443D46 for ; Sun, 24 Jul 2005 10:30:47 +0000 (GMT) (envelope-from ben@bjencks.net) Received: (qmail 83654 invoked from network); 24 Jul 2005 10:30:46 -0000 Received: from unknown (HELO wagner.bjencks.net) (10.11.55.30) by bjencks.net with SMTP; 24 Jul 2005 10:30:46 -0000 Received: (from brj@localhost) by wagner.bjencks.net (8.13.4/8.13.4/Submit) id j6OAUiMU039571; Sun, 24 Jul 2005 03:30:44 -0700 (PDT) (envelope-from ben@bjencks.net) X-Authentication-Warning: wagner.bjencks.net: brj set sender to ben@bjencks.net using -f To: freebsd-acpi@freebsd.org References: <20050724090828.GA1841@c0re.xhr.gi.mrm> From: Ben Jencks Date: Sun, 24 Jul 2005 03:30:37 -0700 In-Reply-To: <20050724090828.GA1841@c0re.xhr.gi.mrm> (Matthias Schmidt's message of "Sun, 24 Jul 2005 11:08:29 +0200") Message-ID: <86k6jgv6lu.fsf@wagner.bjencks.net> User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: schmidtm@mathematik.uni-marburg.de Subject: Re: Strange problems with ACPI/APM on IBM Thinkpad T43 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: Sun, 24 Jul 2005 10:30:48 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Matthias Schmidt writes: > [ Please CC me, I'm not subscribed to freebsd-acpi ] > > Hi, > > I experienced some strange problems with ACPI or APM on my IBM Thinkpad T43 (Type > 2668) and FreeBSD 6.0-BETA. > > To enable suspend2RAM I tried the following things: > > o ACPI > > If ACPI is enabled, suspend work without problems. If I try to resume the > machine freezes and the following message is displayed: APIC seems to be incompatible with suspend, at least on T43[p]. > If I set hint.apic.0.disabled to 1 the laptop resumes fine. Now the strange > thing: Everything is incredible slow. Normal working/typing is nearly > impossible. Why? This is fixed in RELENG_6 and CURRENT. The relevant patch is http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/isa/clock.c.diff?r1=1.222&r2=1.222.2.1 (What's the proper etiquette when responding to cross-posts? Should I cross-post the response, or just send to the most relevant list?) - -- Ben -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC423Upt3yYclAKVsRAl79AKCDHqGqCetR+oaRBINcHh4P9eaGFwCePWc6 PlChGaB0U326mMHqiX0opoU= =JymK -----END PGP SIGNATURE----- From owner-freebsd-acpi@FreeBSD.ORG Sun Jul 24 11:23:34 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 980B116A41F; Sun, 24 Jul 2005 11:23:34 +0000 (GMT) (envelope-from matthias@staatsfeind.org) Received: from outpost.cyberadaptor.de (outpost.cyberadaptor.de [213.133.123.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E22243D45; Sun, 24 Jul 2005 11:23:34 +0000 (GMT) (envelope-from matthias@staatsfeind.org) Received: from p54ae2dee.dip0.t-ipconnect.de ([84.174.45.238] helo=mail.xhr.gi.mrm) by outpost.cyberadaptor.de with asmtp (Exim 3.35 #1 (Debian)) id 1DweZv-0004eb-00; Sun, 24 Jul 2005 13:23:31 +0200 Received: from c0re.xhr.gi.mrm (c0re [10.253.195.101]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.xhr.gi.mrm (Postfix) with ESMTP id 278A346A6E; Sun, 24 Jul 2005 13:23:29 +0200 (CEST) Received: by c0re.xhr.gi.mrm (Postfix, from userid 1000) id 0D69DFB; Sun, 24 Jul 2005 13:23:23 +0200 (CEST) Date: Sun, 24 Jul 2005 13:23:22 +0200 From: Matthias Schmidt To: Ben Jencks , freebsd-acpi@freebsd.org, freebsd-mobile@freebsd.org Message-ID: <20050724112322.GA888@c0re.xhr.gi.mrm> Mail-Followup-To: Ben Jencks , freebsd-acpi@freebsd.org, freebsd-mobile@freebsd.org, schmidtm@mathematik.uni-marburg.de References: <20050724090828.GA1841@c0re.xhr.gi.mrm> <86k6jgv6lu.fsf@wagner.bjencks.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86k6jgv6lu.fsf@wagner.bjencks.net> Cc: schmidtm@mathematik.uni-marburg.de Subject: Re: Strange problems with ACPI/APM on IBM Thinkpad T43 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: Sun, 24 Jul 2005 11:23:34 -0000 Hi, * Ben Jencks wrote: > > This is fixed in RELENG_6 and CURRENT. The relevant patch is > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/isa/clock.c.diff?r1=1.222&r2=1.222.2.1 Thanks for the hint. This fixed the problem with Suspend and ACPI. Matthias From owner-freebsd-acpi@FreeBSD.ORG Sun Jul 24 19:58:27 2005 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CFE0216A41F; Sun, 24 Jul 2005 19:58:27 +0000 (GMT) (envelope-from lists@yazzy.org) Received: from lapdance.yazzy.net (mail.yazzy.org [217.8.140.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2420843D46; Sun, 24 Jul 2005 19:58:22 +0000 (GMT) (envelope-from lists@yazzy.org) Received: from localhost (localhost [127.0.0.1]) by lapdance.yazzy.net (8.13.4/8.13.4) with SMTP id j6OJwJVJ001911; Sun, 24 Jul 2005 21:58:19 +0200 (CEST) (envelope-from lists@yazzy.org) Date: Sun, 24 Jul 2005 21:58:18 +0200 From: Marcin Jessa To: Eric Kjeldergaard Message-Id: <20050724215818.55f951ae.lists@yazzy.org> In-Reply-To: References: <42E1481F.5040306@root.org> <20050723133819.36efb537.lists@yazzy.org> <42E29CAA.1020007@root.org> Organization: YazzY.org X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: acpi@freebsd.org, freebsd-current@freebsd.org Subject: Re: acpi battery rework patch 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: Sun, 24 Jul 2005 19:58:28 -0000 On Sun, 24 Jul 2005 12:47:13 +0900 Eric Kjeldergaard wrote: > On 7/24/05, Nate Lawson wrote: > > Marcin Jessa wrote: > > > On Sat, 23 Jul 2005 19:00:01 +0900 > > > Eric Kjeldergaard wrote: > > >>>Please test to be sure your battery status works as usual, along with > > >>>any apps. Since most apps (xbatt, gnome, etc.) use the apm compat > > >>>layer, they should work as before with no recompilation needed. > > > > > > > > >>-CURRENT as of 23/07/2005, does not compile. > > > > > > > > > Prolly because it's for 6.0, not 7.0 > > > > Sorry, the problem was I left a file out of the diff. I just committed > > the patch so please just cvsup and test from 7-CURRENT. > > > > Thanks, > > -- > > Nate > > > Excellent. compiled and appears working. It does however have > different values than the old system for some of the sysctl variables. > I get > > hw.acpi.battery.life: 98 > hw.acpi.battery.time: 0 > hw.acpi.battery.state: 0 > hw.acpi.battery.units: 1 > hw.acpi.battery.info_expire: 5 > > when plugged in. But used to get time as -1 when plugged in and I > think state may have been 1 when plugged in before (less sure about > that than the time). Thanks for the enormous amount of work your > efforts are very much appreciated, > > Eric Ditto, thanks a lot. It works well here too. I can now actually correctly see whether the lapper is connected to power or runs on battery. Before the state change could not be detected. What lacks is remining time which AFAIR worked before, now showing : hw.acpi.battery.time: -1 I don't miss it though since showing remining percentage is more than enough. Thanks again for great work! Marcin Jessa. From owner-freebsd-acpi@FreeBSD.ORG Sun Jul 24 20:57:34 2005 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 38D8216A41F; Sun, 24 Jul 2005 20:57:34 +0000 (GMT) (envelope-from lists@yazzy.org) Received: from lapdance.yazzy.net (mail.yazzy.org [217.8.140.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABE9743D49; Sun, 24 Jul 2005 20:57:32 +0000 (GMT) (envelope-from lists@yazzy.org) Received: from localhost (localhost [127.0.0.1]) by lapdance.yazzy.net (8.13.4/8.13.4) with SMTP id j6OKvL9q000840; Sun, 24 Jul 2005 22:57:21 +0200 (CEST) (envelope-from lists@yazzy.org) Date: Sun, 24 Jul 2005 22:57:21 +0200 From: Marcin Jessa To: Marcin Jessa Message-Id: <20050724225721.0f869e66.lists@yazzy.org> In-Reply-To: <20050724215818.55f951ae.lists@yazzy.org> References: <42E1481F.5040306@root.org> <20050723133819.36efb537.lists@yazzy.org> <42E29CAA.1020007@root.org> <20050724215818.55f951ae.lists@yazzy.org> Organization: YazzY.org X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: acpi@freebsd.org, freebsd-current@freebsd.org Subject: Re: acpi battery rework patch 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: Sun, 24 Jul 2005 20:57:34 -0000 On Sun, 24 Jul 2005 21:58:18 +0200 Marcin Jessa wrote: > On Sun, 24 Jul 2005 12:47:13 +0900 > Eric Kjeldergaard wrote: > > > On 7/24/05, Nate Lawson wrote: > > > Marcin Jessa wrote: > > > > On Sat, 23 Jul 2005 19:00:01 +0900 > > > > Eric Kjeldergaard wrote: > > > >>>Please test to be sure your battery status works as usual, along with > > > >>>any apps. Since most apps (xbatt, gnome, etc.) use the apm compat > > > >>>layer, they should work as before with no recompilation needed. > > > > > > > > > > > >>-CURRENT as of 23/07/2005, does not compile. > > > > > > > > > > > > Prolly because it's for 6.0, not 7.0 > > > > > > Sorry, the problem was I left a file out of the diff. I just committed > > > the patch so please just cvsup and test from 7-CURRENT. > > > > > > Thanks, > > > -- > > > Nate > > > > > Excellent. compiled and appears working. It does however have > > different values than the old system for some of the sysctl variables. > > I get > > > > hw.acpi.battery.life: 98 > > hw.acpi.battery.time: 0 > > hw.acpi.battery.state: 0 > > hw.acpi.battery.units: 1 > > hw.acpi.battery.info_expire: 5 > > > > when plugged in. But used to get time as -1 when plugged in and I > > think state may have been 1 when plugged in before (less sure about > > that than the time). Thanks for the enormous amount of work your > > efforts are very much appreciated, > > > > Eric > > Ditto, thanks a lot. It works well here too. I can now actually correctly see whether the lapper is connected to power or runs on battery. > Before the state change could not be detected. > What lacks is remining time which AFAIR worked before, now showing : hw.acpi.battery.time: -1 > I don't miss it though since showing remining percentage is more than enough. > Thanks again for great work! It seems like I was wrong. The time values showed up after a short while of running on battery. From owner-freebsd-acpi@FreeBSD.ORG Mon Jul 25 00:16:14 2005 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D1D016A41F; Mon, 25 Jul 2005 00:16:14 +0000 (GMT) (envelope-from nate@root.org) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BDEF43D46; Mon, 25 Jul 2005 00:16:13 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.5.50] (adsl-64-171-187-230.dsl.snfc21.pacbell.net [64.171.187.230]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id j6P0G7o5019802 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 24 Jul 2005 17:16:12 -0700 Message-ID: <42E42F10.3030309@root.org> Date: Sun, 24 Jul 2005 17:15:12 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Marcin Jessa References: <42E1481F.5040306@root.org> <20050723133819.36efb537.lists@yazzy.org> <42E29CAA.1020007@root.org> <20050724215818.55f951ae.lists@yazzy.org> In-Reply-To: <20050724215818.55f951ae.lists@yazzy.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: acpi@freebsd.org, freebsd-current@freebsd.org Subject: Re: acpi battery rework patch 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: Mon, 25 Jul 2005 00:16:14 -0000 Marcin Jessa wrote: > On Sun, 24 Jul 2005 12:47:13 +0900 > Eric Kjeldergaard wrote: >>Excellent. compiled and appears working. It does however have >>different values than the old system for some of the sysctl variables. >> I get >> >>hw.acpi.battery.life: 98 >>hw.acpi.battery.time: 0 >>hw.acpi.battery.state: 0 >>hw.acpi.battery.units: 1 >>hw.acpi.battery.info_expire: 5 >> >>when plugged in. But used to get time as -1 when plugged in and I >>think state may have been 1 when plugged in before (less sure about >>that than the time). Thanks for the enormous amount of work your >>efforts are very much appreciated, >> >>Eric > > > Ditto, thanks a lot. It works well here too. I can now actually correctly see whether the lapper is connected to power or runs on battery. > Before the state change could not be detected. > What lacks is remining time which AFAIR worked before, now showing : hw.acpi.battery.time: -1 > I don't miss it though since showing remining percentage is more than enough. > Thanks again for great work! Both of you please boot either the last 6.0 beta1 or a 5.x kernel and let me know for sure what your original behavior was. As far as Eric's result, I'll check that on my systems as well. I _think_ the previous behavior was more correct (-1 = unknown) so I'll commit this minor change. The "state" variable should not have changed so please let me know for sure if it has. "1" means "discharging" which doesn't sound right if you're on AC power. If you just recently plugged in the laptop, try polling the status a few more times (apm(8) gives more detail) and see if it catches up. Some systems lag reporting various values until they are sure they've restabilized after an AC line change. Marcin, if your system reports a valid rate of use, we can calculate time. If you're on AC power, there is no time available (since your batteries aren't discharging at any rate). Try a previous kernel/acpi.ko to be certain what the behavior used to be. One easy way to do this is use the FreeSBIE live CD, based on 5.3-RELEASE: http://www.freesbie.org/ -- Nate From owner-freebsd-acpi@FreeBSD.ORG Mon Jul 25 00:24:23 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4DA8A16A41F for ; Mon, 25 Jul 2005 00:24:23 +0000 (GMT) (envelope-from nate@root.org) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0753343D46 for ; Mon, 25 Jul 2005 00:24:22 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.5.50] (adsl-64-171-187-230.dsl.snfc21.pacbell.net [64.171.187.230]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id j6P0OHo5020182 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 24 Jul 2005 17:24:18 -0700 Message-ID: <42E430F9.3020009@root.org> Date: Sun, 24 Jul 2005 17:23:21 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Takanori Watanabe References: <200507240618.j6O6ISWx093600@sana.init-main.com> In-Reply-To: <200507240618.j6O6ISWx093600@sana.init-main.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: acpi battery rework patch 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: Mon, 25 Jul 2005 00:24:23 -0000 Takanori Watanabe wrote: > In message <42E29CAA.1020007@root.org>, Nate Lawson さんいわく: >>Sorry, the problem was I left a file out of the diff. I just committed >>the patch so please just cvsup and test from 7-CURRENT. > > I don't tried yet, but devclass battery should be shared between > any kind of batteries in your way. So move acpi_cmbat_devclass into > acpi_battery.c and change its name to acpi_battery_devclass. Yes, that is how the patch already works. As dfr@ told me, devclasses are matched based on name (i.e. "battery"), not by actual storage for the devclass_t. So there is no need to share anything but just reuse the same class string. Perhaps he can correct me if I'm wrong. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Mon Jul 25 03:54:37 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB5E016A41F for ; Mon, 25 Jul 2005 03:54:37 +0000 (GMT) (envelope-from takash-i@sophia.ac.jp) Received: from rockliff.cc.sophia.ac.jp (rockliff.cc.sophia.ac.jp [133.12.140.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7FE2043D46 for ; Mon, 25 Jul 2005 03:54:36 +0000 (GMT) (envelope-from takash-i@sophia.ac.jp) Received: from heuvers.cc.sophia.ac.jp (heuvers [133.12.138.37]) by rockliff.cc.sophia.ac.jp (Postfix) with ESMTP id 3DC1D10E58 for ; Mon, 25 Jul 2005 12:54:36 +0900 (JST) Received: from [133.12.65.9] (koetoi [133.12.138.217]) by heuvers.cc.sophia.ac.jp (Postfix) with ESMTP id 1FFC5A06C; Mon, 25 Jul 2005 12:54:36 +0900 (JST) Message-ID: <42E46297.7080202@sophia.ac.jp> Date: Mon, 25 Jul 2005 12:55:03 +0900 From: Takashi Inoue User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.7) Gecko/20050420 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-acpi@freebsd.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Takashi Inoue Subject: Strange problems with ACPI/APM on IBM Thinkpad T43 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: Mon, 25 Jul 2005 03:54:37 -0000 > > > If ACPI is enabled, suspend work without problems. If I try to resume the > machine freezes and the following message is displayed: > > ioapic_suspend: not implemented! > ioapic_suspend: not implemented! > [...] > ioapic_suspend: not implemented! > acpi_bus_number: can't get _ADR > [freeze] > > > If I set hint.apic.0.disabled to 1 the laptop resumes fine. > The same at here on ThinkPad X40 with 5.4R. It seems bug related to ATA. Cheers, Takashi From owner-freebsd-acpi@FreeBSD.ORG Mon Jul 25 07:12:28 2005 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 057CA16A41F; Mon, 25 Jul 2005 07:12:28 +0000 (GMT) (envelope-from lists@yazzy.org) Received: from lapdance.yazzy.net (217-13-2-82.dd.nextgentel.com [217.13.2.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68F8143D45; Mon, 25 Jul 2005 07:12:26 +0000 (GMT) (envelope-from lists@yazzy.org) Received: from localhost (localhost [127.0.0.1]) by lapdance.yazzy.net (8.13.4/8.13.4) with SMTP id j6P7CLnk000945; Mon, 25 Jul 2005 09:12:22 +0200 (CEST) (envelope-from lists@yazzy.org) Date: Mon, 25 Jul 2005 09:12:21 +0200 From: Marcin Jessa To: Nate Lawson Message-Id: <20050725091221.106a0368.lists@yazzy.org> In-Reply-To: <42E42F10.3030309@root.org> References: <42E1481F.5040306@root.org> <20050723133819.36efb537.lists@yazzy.org> <42E29CAA.1020007@root.org> <20050724215818.55f951ae.lists@yazzy.org> <42E42F10.3030309@root.org> Organization: YazzY.org X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: acpi@freebsd.org, freebsd-current@freebsd.org Subject: Re: acpi battery rework patch 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: Mon, 25 Jul 2005 07:12:28 -0000 On Sun, 24 Jul 2005 17:15:12 -0700 Nate Lawson wrote: > Marcin Jessa wrote: > > On Sun, 24 Jul 2005 12:47:13 +0900 > > Eric Kjeldergaard wrote: > >>Excellent. compiled and appears working. It does however have > >>different values than the old system for some of the sysctl variables. > >> I get > >> > >>hw.acpi.battery.life: 98 > >>hw.acpi.battery.time: 0 > >>hw.acpi.battery.state: 0 > >>hw.acpi.battery.units: 1 > >>hw.acpi.battery.info_expire: 5 > >> > >>when plugged in. But used to get time as -1 when plugged in and I > >>think state may have been 1 when plugged in before (less sure about > >>that than the time). Thanks for the enormous amount of work your > >>efforts are very much appreciated, > >> > >>Eric > > > > > > Ditto, thanks a lot. It works well here too. I can now actually correctly see whether the lapper is connected to power or runs on battery. > > Before the state change could not be detected. > > What lacks is remining time which AFAIR worked before, now showing : hw.acpi.battery.time: -1 > > I don't miss it though since showing remining percentage is more than enough. > > Thanks again for great work! > > Both of you please boot either the last 6.0 beta1 or a 5.x kernel and > let me know for sure what your original behavior was. > > As far as Eric's result, I'll check that on my systems as well. I > _think_ the previous behavior was more correct (-1 = unknown) so I'll > commit this minor change. The "state" variable should not have changed > so please let me know for sure if it has. "1" means "discharging" which > doesn't sound right if you're on AC power. If you just recently plugged > in the laptop, try polling the status a few more times (apm(8) gives > more detail) and see if it catches up. Some systems lag reporting > various values until they are sure they've restabilized after an AC line > change. > > Marcin, if your system reports a valid rate of use, we can calculate > time. If you're on AC power, there is no time available (since your > batteries aren't discharging at any rate). Try a previous > kernel/acpi.ko to be certain what the behavior used to be. One easy way > to do this is use the FreeSBIE live CD, based on 5.3-RELEASE: > > http://www.freesbie.org/ [yazzy@lapdance:~]> uname -a FreeBSD lapdance.yazzy.net 6.0-BETA1 FreeBSD 6.0-BETA1 #4: Sat Jul 23 17:35:13 CEST 2005 root@lapdance.yazzy.net:/usr/obj/usr/src/sys/LAPDANCE-6.0 i386 Running on AC: [yazzy@lapdance:~]> sysctl -a | grep battery hw.acpi.battery.life: 23 hw.acpi.battery.time: -1 hw.acpi.battery.state: 2 hw.acpi.battery.units: 1 hw.acpi.battery.info_expire: 5 Running on battery: [yazzy@lapdance:~]> sysctl -a | grep battery hw.acpi.battery.life: 23 hw.acpi.battery.time: 41 hw.acpi.battery.state: 1 hw.acpi.battery.units: 1 hw.acpi.battery.info_expire: 5 [yazzy@lapdance:~]> Cheers, Marcin. From owner-freebsd-acpi@FreeBSD.ORG Mon Jul 25 07:53:56 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B4FA816A41F for ; Mon, 25 Jul 2005 07:53:56 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from itchy.rabson.org (mailgate.nlsystems.com [80.177.232.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD95C43D4C for ; Mon, 25 Jul 2005 07:53:54 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from herring.rabson.org (herring [10.0.0.2]) by itchy.rabson.org (8.13.3/8.13.3) with ESMTP id j6P7rXDC090539; Mon, 25 Jul 2005 08:53:34 +0100 (BST) (envelope-from dfr@nlsystems.com) From: Doug Rabson To: Nate Lawson Date: Mon, 25 Jul 2005 08:53:31 +0100 User-Agent: KMail/1.8 References: <200507240618.j6O6ISWx093600@sana.init-main.com> <42E430F9.3020009@root.org> In-Reply-To: <42E430F9.3020009@root.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200507250853.32622.dfr@nlsystems.com> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.6 (itchy.rabson.org [80.177.232.242]); Mon, 25 Jul 2005 08:53:39 +0100 (BST) X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on itchy.rabson.org X-Virus-Scanned: ClamAV 0.83/989/Fri Jul 22 22:27:30 2005 on itchy.rabson.org X-Virus-Status: Clean Cc: freebsd-acpi@freebsd.org, Takanori Watanabe Subject: Re: acpi battery rework patch 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: Mon, 25 Jul 2005 07:53:56 -0000 On Monday 25 July 2005 01:23, Nate Lawson wrote: > Takanori Watanabe wrote: > > In message <42E29CAA.1020007@root.org>, Nate Lawson さんいわく: > >>Sorry, the problem was I left a file out of the diff. I just > >> committed the patch so please just cvsup and test from 7-CURRENT. > > > > I don't tried yet, but devclass battery should be shared between > > any kind of batteries in your way. So move acpi_cmbat_devclass into > > acpi_battery.c and change its name to acpi_battery_devclass. > > Yes, that is how the patch already works. As dfr@ told me, > devclasses are matched based on name (i.e. "battery"), not by actual > storage for the devclass_t. So there is no need to share anything > but just reuse the same class string. Perhaps he can correct me if > I'm wrong. You are right. From owner-freebsd-acpi@FreeBSD.ORG Mon Jul 25 08:22:19 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA18716A41F for ; Mon, 25 Jul 2005 08:22:19 +0000 (GMT) (envelope-from m.ehinger@ltur.de) Received: from posty.gateway-inter.net (posty.gateway-inter.net [213.144.19.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7390743D46 for ; Mon, 25 Jul 2005 08:22:19 +0000 (GMT) (envelope-from m.ehinger@ltur.de) To: freebsd-acpi@freebsd.org Message-ID: From: m.ehinger@ltur.de Date: Mon, 25 Jul 2005 10:21:46 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Subject: ATI Radeon power management disabled after resume 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: Mon, 25 Jul 2005 08:22:19 -0000 Hi, don't know if this is the right list. If not i apologize. I recognized an temperature raise from about 10 degrees centigrade on my radeon 9600 GPU after i resume from suspend. everthing else ist fine. This happens on console and X. If i start the Xorg server with "DynamicClocks" enabled temperature drops within 10 seconds back to normal. Is there any tool to do this per command? I'm running FreeBSD 6-BETA1 on an Thinkpad T42 with ATI Radeon 9600 M10. I got acpi_video and acpi_ibm loaded. (same behaviour when not loaded) Thanks in advance Maik From owner-freebsd-acpi@FreeBSD.ORG Mon Jul 25 11:02:05 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 68E6016A425 for ; Mon, 25 Jul 2005 11:02:05 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id C7C7343D45 for ; Mon, 25 Jul 2005 11:02:04 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j6PB24qx018289 for ; Mon, 25 Jul 2005 11:02:04 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j6PB23Pd018283 for freebsd-acpi@freebsd.org; Mon, 25 Jul 2005 11:02:03 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 25 Jul 2005 11:02:03 GMT Message-Id: <200507251102.j6PB23Pd018283@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-acpi@FreeBSD.org Cc: Subject: Current problem reports assigned to you 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: Mon, 25 Jul 2005 11:02:05 -0000 Current FreeBSD problem reports Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/07/22] i386/54756 acpi ACPI suspend/resume problem on CF-W2 lapt o [2003/08/17] i386/55661 acpi ACPI suspend/resume problem on ARMADA M70 o [2003/08/20] kern/55822 acpi No ACPI power off with SMP kernel o [2003/08/27] kern/56024 acpi ACPI suspend drains battery while in S3 o [2003/09/03] i386/56372 acpi acpi don't work on TYAN tiger100 M/B f [2003/09/10] kern/56659 acpi ACPI trouble on IBM ThinkPad X31 f [2003/12/17] i386/60317 acpi FreeBSD 5.2rc1 doesn't boot with ACPI ena f [2004/03/02] kern/63666 acpi [acpi] Network card 3c575B do not work af o [2004/03/09] i386/64002 acpi acpi problem o [2004/05/27] i386/67273 acpi [hang] system hangs with acpi and Xfree o [2004/10/12] i386/72566 acpi ACPI, FreeBSD disables fan on Compaq Arma o [2005/03/21] i386/79080 acpi acpi thermal changes freezes HP nx6110 o [2005/03/21] i386/79081 acpi ACPI suspend/resume not working on HP nx6 13 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- f [2004/01/22] i386/61703 acpi ACPI + Sound + Boot = Reboot o [2004/03/17] kern/64365 acpi ACPI problems f [2004/05/25] i386/67189 acpi ACPI S3 reboot computer on Dell Latitude o [2004/05/28] kern/67309 acpi zzz reboot computer (ACPI S3) f [2004/06/23] i386/68219 acpi ACPI + snd_maestro3 problem o [2004/07/29] i386/69750 acpi Boot without ACPI failed on ASUS L5 o [2004/11/11] i386/73822 acpi [request] add thermal support to ACPI o [2004/11/11] kern/73823 acpi acpi / power-on by timer support o [2004/11/17] kern/74030 acpi Unplugging AC causes battery % to stay lo o [2004/11/21] kern/74215 acpi [request] add ACPI headers to /usr/includ o [2005/05/09] kern/80815 acpi ACPI(pci_link) problem in 5.4-STABLE: TIM 11 problems total. From owner-freebsd-acpi@FreeBSD.ORG Mon Jul 25 16:29:07 2005 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9320C16A41F; Mon, 25 Jul 2005 16:29:07 +0000 (GMT) (envelope-from nate@root.org) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id D117C43D5C; Mon, 25 Jul 2005 16:29:06 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.33] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id j6PGT5o5002189 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 25 Jul 2005 09:29:05 -0700 Message-ID: <42E5134F.706@root.org> Date: Mon, 25 Jul 2005 09:29:03 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050723) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Marcin Jessa References: <42E1481F.5040306@root.org> <20050723133819.36efb537.lists@yazzy.org> <42E29CAA.1020007@root.org> <20050724215818.55f951ae.lists@yazzy.org> <42E42F10.3030309@root.org> <20050725091221.106a0368.lists@yazzy.org> In-Reply-To: <20050725091221.106a0368.lists@yazzy.org> Content-Type: multipart/mixed; boundary="------------060301040900060402010609" Cc: acpi@freebsd.org, freebsd-current@freebsd.org Subject: Re: acpi battery rework patch 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: Mon, 25 Jul 2005 16:29:07 -0000 This is a multi-part message in MIME format. --------------060301040900060402010609 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Marcin Jessa wrote: > On Sun, 24 Jul 2005 17:15:12 -0700 > Nate Lawson wrote: >>As far as Eric's result, I'll check that on my systems as well. I >>_think_ the previous behavior was more correct (-1 = unknown) so I'll >>commit this minor change. The "state" variable should not have changed >>so please let me know for sure if it has. "1" means "discharging" which >>doesn't sound right if you're on AC power. If you just recently plugged >>in the laptop, try polling the status a few more times (apm(8) gives >>more detail) and see if it catches up. Some systems lag reporting >>various values until they are sure they've restabilized after an AC line >>change. >> >>Marcin, if your system reports a valid rate of use, we can calculate >>time. If you're on AC power, there is no time available (since your >>batteries aren't discharging at any rate). Try a previous >>kernel/acpi.ko to be certain what the behavior used to be. > > > [yazzy@lapdance:~]> uname -a > FreeBSD lapdance.yazzy.net 6.0-BETA1 FreeBSD 6.0-BETA1 #4: Sat Jul 23 17:35:13 CEST 2005 root@lapdance.yazzy.net:/usr/obj/usr/src/sys/LAPDANCE-6.0 i386 > > Running on AC: > [yazzy@lapdance:~]> sysctl -a | grep battery > hw.acpi.battery.life: 23 > hw.acpi.battery.time: -1 > hw.acpi.battery.state: 2 > hw.acpi.battery.units: 1 > hw.acpi.battery.info_expire: 5 > > Running on battery: > [yazzy@lapdance:~]> sysctl -a | grep battery > hw.acpi.battery.life: 23 > hw.acpi.battery.time: 41 > hw.acpi.battery.state: 1 > hw.acpi.battery.units: 1 > hw.acpi.battery.info_expire: 5 > [yazzy@lapdance:~]> And with a 7-current kernel, everything is the same except "time" is always -1 both on and off AC power? Please try this patch with 7-current and report its output both on and off power. It prints out more debugging info each time the battery is read. -- Nate --------------060301040900060402010609 Content-Type: text/plain; name="batt_dbg.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="batt_dbg.diff" Index: sys/dev/acpica/acpi_battery.c =================================================================== RCS file: /home/ncvs/src/sys/dev/acpica/acpi_battery.c,v retrieving revision 1.13 diff -u -r1.13 acpi_battery.c --- sys/dev/acpica/acpi_battery.c 23 Jul 2005 19:35:59 -0000 1.13 +++ sys/dev/acpica/acpi_battery.c 25 Jul 2005 15:59:29 -0000 @@ -161,6 +161,7 @@ error = ENOMEM; goto out; } +printf("batt pass1: dev %p ", batt_dev); /* Default info for every battery is "not present". */ acpi_reset_battinfo(&bi[i]); @@ -174,11 +175,13 @@ ACPI_BATT_GET_STATUS(batt_dev, &bst[i]) != 0 || ACPI_BATT_GET_INFO(batt_dev, bif) != 0) continue; +printf("ok "); /* If a battery is not installed, we sometimes get strange values. */ if (!acpi_battery_bst_valid(&bst[i]) || !acpi_battery_bif_valid(bif)) continue; +printf("valid "); /* Record state and calculate percent capacity remaining. */ valid_units++; @@ -204,10 +207,12 @@ */ if (bst[i].rate > 0 && (bst[i].state & ACPI_BATT_STAT_DISCHARG)) valid_rate += bst[i].rate; +printf("state %d cap %d valid_rate %d\n", bi[i].state, bi[i].cap, valid_rate); } /* If the caller asked for a device but we didn't find it, error. */ if (dev != NULL && dev_idx < 0) { +printf("batt: couldn't find dev %p\n", dev); error = ENXIO; goto out; } @@ -226,6 +231,8 @@ bi[i].min = 0; total_min += bi[i].min; total_cap += bi[i].cap; +printf("batt pass2: min %d total_min %d total_cap %d\n", bi[i].min, total_min, +total_cap); } /* --------------060301040900060402010609-- From owner-freebsd-acpi@FreeBSD.ORG Mon Jul 25 16:59:47 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 52F8516A41F for ; Mon, 25 Jul 2005 16:59:47 +0000 (GMT) (envelope-from nate@root.org) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0590E43D48 for ; Mon, 25 Jul 2005 16:59:46 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.33] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id j6PGxjo5002475 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 25 Jul 2005 09:59:46 -0700 Message-ID: <42E51A7F.1010103@root.org> Date: Mon, 25 Jul 2005 09:59:43 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050723) X-Accept-Language: en-us, en MIME-Version: 1.0 To: m.ehinger@ltur.de References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: ATI Radeon power management disabled after resume 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: Mon, 25 Jul 2005 16:59:47 -0000 m.ehinger@ltur.de wrote: > Hi, > > don't know if this is the right list. If not i apologize. > > I recognized an temperature raise from about 10 degrees centigrade on my radeon 9600 GPU after i resume from suspend. everthing else > ist fine. > This happens on console and X. > > If i start the Xorg server with "DynamicClocks" enabled temperature drops within 10 seconds back to normal. > > Is there any tool to do this per command? > > I'm running FreeBSD 6-BETA1 on an Thinkpad T42 with ATI Radeon 9600 M10. > I got acpi_video and acpi_ibm loaded. (same behaviour when not loaded) I think Xorg should handle this. Unless the radeon exports some Dx state control via ACPI, only device-specific extensions like DynamicClocks can control the radeon. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Mon Jul 25 17:12:29 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8622016A41F for ; Mon, 25 Jul 2005 17:12:29 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from mv.twc.weather.com (mv.twc.weather.com [65.212.71.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 251BE43D46 for ; Mon, 25 Jul 2005 17:12:29 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from [10.50.40.201] (Not Verified[65.202.103.25]) by mv.twc.weather.com with NetIQ MailMarshal (v6, 0, 3, 8) id ; Mon, 25 Jul 2005 13:26:53 -0400 From: John Baldwin To: freebsd-acpi@freebsd.org Date: Mon, 25 Jul 2005 08:53:08 -0400 User-Agent: KMail/1.8 References: <20050724090828.GA1841@c0re.xhr.gi.mrm> In-Reply-To: <20050724090828.GA1841@c0re.xhr.gi.mrm> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200507250853.09808.jhb@FreeBSD.org> Cc: Matthias Schmidt Subject: Re: Strange problems with ACPI/APM on IBM Thinkpad T43 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: Mon, 25 Jul 2005 17:12:29 -0000 On Sunday 24 July 2005 05:08 am, Matthias Schmidt wrote: > [ Please CC me, I'm not subscribed to freebsd-acpi ] > > Hi, > > I experienced some strange problems with ACPI or APM on my IBM Thinkpad T43 > (Type 2668) and FreeBSD 6.0-BETA. > > To enable suspend2RAM I tried the following things: > > o ACPI > > If ACPI is enabled, suspend work without problems. If I try to resume > the machine freezes and the following message is displayed: > > ioapic_suspend: not implemented! > ioapic_suspend: not implemented! > [...] > ioapic_suspend: not implemented! > acpi_bus_number: can't get _ADR > [freeze] > > > If I set hint.apic.0.disabled to 1 the laptop resumes fine. Now the > strange thing: Everything is incredible slow. Normal working/typing is > nearly impossible. Why? Ok, does it still not work right after you applied the clock patch with APIC enabled? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Mon Jul 25 17:46:08 2005 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 73BD816A41F; Mon, 25 Jul 2005 17:46:08 +0000 (GMT) (envelope-from nate@root.org) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 214C343D46; Mon, 25 Jul 2005 17:46:07 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.33] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id j6PHk6o5002928 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 25 Jul 2005 10:46:07 -0700 Message-ID: <42E5255D.7050008@root.org> Date: Mon, 25 Jul 2005 10:46:05 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050723) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Marcin Jessa References: <42E1481F.5040306@root.org> <20050723133819.36efb537.lists@yazzy.org> <42E29CAA.1020007@root.org> <20050724215818.55f951ae.lists@yazzy.org> In-Reply-To: <20050724215818.55f951ae.lists@yazzy.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: acpi@freebsd.org, freebsd-current@freebsd.org Subject: Re: acpi battery rework patch 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: Mon, 25 Jul 2005 17:46:08 -0000 On Sun, 24 Jul 2005 12:47:13 +0900 Eric Kjeldergaard wrote: >>Excellent. compiled and appears working. It does however have >>different values than the old system for some of the sysctl variables. >> I get >> >>hw.acpi.battery.life: 98 >>hw.acpi.battery.time: 0 >>hw.acpi.battery.state: 0 >>hw.acpi.battery.units: 1 >>hw.acpi.battery.info_expire: 5 >> >>when plugged in. But used to get time as -1 when plugged in and I >>think state may have been 1 when plugged in before (less sure about >>that than the time). Thanks for the enormous amount of work your >>efforts are very much appreciated, Ok, I have tested and committed a patch that corrects the output for "time". I was able to verify that the behavior should be "unknown" when charging/online rather than "0". I just need Marcin's debug output now from the patch I sent earlier today. Thanks, -- Nate From owner-freebsd-acpi@FreeBSD.ORG Mon Jul 25 17:58:14 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F3FC316A41F; Mon, 25 Jul 2005 17:58:13 +0000 (GMT) (envelope-from matthias@staatsfeind.org) Received: from outpost.cyberadaptor.de (outpost.cyberadaptor.de [213.133.123.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 89E7F43D45; Mon, 25 Jul 2005 17:58:13 +0000 (GMT) (envelope-from matthias@staatsfeind.org) Received: from p54ae15b3.dip0.t-ipconnect.de ([84.174.21.179] helo=mail.xhr.gi.mrm) by outpost.cyberadaptor.de with asmtp (Exim 3.35 #1 (Debian)) id 1Dx7DM-0008DG-00; Mon, 25 Jul 2005 19:58:08 +0200 Received: from c0re.xhr.gi.mrm (c0re [10.253.195.101]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.xhr.gi.mrm (Postfix) with ESMTP id 6554446A6E; Mon, 25 Jul 2005 19:58:07 +0200 (CEST) Received: by c0re.xhr.gi.mrm (Postfix, from userid 1000) id CFB75100; Mon, 25 Jul 2005 19:58:01 +0200 (CEST) Date: Mon, 25 Jul 2005 19:58:01 +0200 From: Matthias Schmidt To: John Baldwin Message-ID: <20050725175801.GA5110@c0re.xhr.gi.mrm> Mail-Followup-To: John Baldwin , freebsd-acpi@FreeBSD.org, Matthias Schmidt References: <20050724090828.GA1841@c0re.xhr.gi.mrm> <200507250853.09808.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200507250853.09808.jhb@FreeBSD.org> Cc: freebsd-acpi@FreeBSD.org, Matthias Schmidt Subject: Re: Strange problems with ACPI/APM on IBM Thinkpad T43 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: Mon, 25 Jul 2005 17:58:14 -0000 Hi John, * John Baldwin wrote: > > Ok, does it still not work right after you applied the clock patch with APIC > enabled? It works fine with APIC disabled :) I am currently on the way to What The Hack, so I'll have time tomorrow to try it with APIC enabled. Greets Matthias From owner-freebsd-acpi@FreeBSD.ORG Mon Jul 25 18:41:09 2005 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 37B5316A41F; Mon, 25 Jul 2005 18:41:09 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from smtp-vbr11.xs4all.nl (smtp-vbr11.xs4all.nl [194.109.24.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 22A7F43D53; Mon, 25 Jul 2005 18:41:07 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp-vbr11.xs4all.nl (8.13.3/8.13.3) with ESMTP id j6PIf2J0041889; Mon, 25 Jul 2005 20:41:02 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.13.3/8.13.3) with ESMTP id j6PIf1be041045; Mon, 25 Jul 2005 20:41:01 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.3/8.13.1/Submit) id j6PIf1Zx041044; Mon, 25 Jul 2005 20:41:01 +0200 (CEST) (envelope-from wb) Date: Mon, 25 Jul 2005 20:41:01 +0200 From: Wilko Bulte To: Nate Lawson Message-ID: <20050725184101.GA41023@freebie.xs4all.nl> References: <42E1481F.5040306@root.org> <20050723133819.36efb537.lists@yazzy.org> <42E29CAA.1020007@root.org> <20050724215818.55f951ae.lists@yazzy.org> <42E42F10.3030309@root.org> <20050725091221.106a0368.lists@yazzy.org> <42E5134F.706@root.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42E5134F.706@root.org> X-OS: FreeBSD 5.4-STABLE User-Agent: Mutt/1.5.9i X-Virus-Scanned: by XS4ALL Virus Scanner Cc: acpi@freebsd.org, Marcin Jessa , freebsd-current@freebsd.org Subject: Re: acpi battery rework patch 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: Mon, 25 Jul 2005 18:41:09 -0000 On Mon, Jul 25, 2005 at 09:29:03AM -0700, Nate Lawson wrote.. > Marcin Jessa wrote: > >On Sun, 24 Jul 2005 17:15:12 -0700 > >Nate Lawson wrote: > >>As far as Eric's result, I'll check that on my systems as well. I > >>_think_ the previous behavior was more correct (-1 = unknown) so I'll > >>commit this minor change. The "state" variable should not have changed > >>so please let me know for sure if it has. "1" means "discharging" which > >>doesn't sound right if you're on AC power. If you just recently plugged > >>in the laptop, try polling the status a few more times (apm(8) gives > >>more detail) and see if it catches up. Some systems lag reporting > >>various values until they are sure they've restabilized after an AC line > >>change. > >> > >>Marcin, if your system reports a valid rate of use, we can calculate > >>time. If you're on AC power, there is no time available (since your > >>batteries aren't discharging at any rate). Try a previous > >>kernel/acpi.ko to be certain what the behavior used to be. > > > > > >[yazzy@lapdance:~]> uname -a > >FreeBSD lapdance.yazzy.net 6.0-BETA1 FreeBSD 6.0-BETA1 #4: Sat Jul 23 > >17:35:13 CEST 2005 > >root@lapdance.yazzy.net:/usr/obj/usr/src/sys/LAPDANCE-6.0 i386 > > > >Running on AC: > >[yazzy@lapdance:~]> sysctl -a | grep battery > >hw.acpi.battery.life: 23 > >hw.acpi.battery.time: -1 > >hw.acpi.battery.state: 2 > >hw.acpi.battery.units: 1 > >hw.acpi.battery.info_expire: 5 > > > >Running on battery: > >[yazzy@lapdance:~]> sysctl -a | grep battery > >hw.acpi.battery.life: 23 > >hw.acpi.battery.time: 41 > >hw.acpi.battery.state: 1 > >hw.acpi.battery.units: 1 > >hw.acpi.battery.info_expire: 5 > >[yazzy@lapdance:~]> > > And with a 7-current kernel, everything is the same except "time" is > always -1 both on and off AC power? > > Please try this patch with 7-current and report its output both on and > off power. It prints out more debugging info each time the battery is read. On an Compaq EVO N160, on AC power Trying to mount root from ufs:/dev/ad0s2a batt pass1: dev 0xc15e3100 ok valid state 2 cap 0 valid_rate 0 batt pass2: min 0 total_min 0 total_cap 0 batt pass1: dev 0xc15e3100 ok valid state 2 cap 0 valid_rate 0 batt pass2: min 0 total_min 0 total_cap 0 batt pass1: dev 0xc15e3100 ok valid state 2 cap 0 valid_rate 0 batt pass2: min 0 total_min 0 total_cap 0 batt pass1: dev 0xc15e3100 ok valid state 2 cap 0 valid_rate 0 batt pass2: min 0 total_min 0 total_cap 0 batt pass1: dev 0xc15e3100 ok valid state 2 cap 0 valid_rate 0 batt pass2: min 0 total_min 0 total_cap 0 batt pass1: dev 0xc15e3100 ok valid state 2 cap 0 valid_rate 0 batt pass2: min 0 total_min 0 total_cap 0 ichss0: transition to 1 failed ichss0: transition to 1 failed ichss0: transition to 1 failed batt pass1: dev 0xc15e3100 ok valid state 2 cap 0 valid_rate 0 batt pass2: min 0 total_min 0 total_cap 0 ichss0: transition to 1 failed ichss0: transition to 1 failed batt pass1: dev 0xc15e3100 ok valid state 2 cap 0 valid_rate 0 batt pass2: min 0 total_min 0 total_cap 0 batt pass1: dev 0xc15e3100 ok valid state 2 cap 0 valid_rate 0 batt pass2: min 0 total_min 0 total_cap 0 ichss0: transition to 1 failed APM version: 1.2 APM Management: Enabled AC Line status: on-line Battery Status: charging Remaining battery life: 0% Remaining battery time: 0:00:00 Number of batteries: 1 Battery 0: Battery Status: charging Remaining battery life: 0% Remaining battery time: 0:00:00 wb@chuck ~: Unplugging AC power: batt pass1: dev 0xc15e3100 ok valid state 1 cap 0 valid_rate 1082 batt pass2: min 166 total_min 166 total_cap 0 batt pass1: dev 0xc15e3100 ok valid state 1 cap 0 valid_rate 1082 batt pass2: min 166 total_min 166 total_cap 0 batt pass1: dev 0xc15e3100 ok valid state 1 cap 0 valid_rate 1082 batt pass2: min 166 total_min 166 total_cap 0 batt pass1: dev 0xc15e3100 ok valid state 1 cap 0 valid_rate 1082 batt pass2: min 166 total_min 166 total_cap 0 batt pass1: dev 0xc15e3100 ok valid state 1 cap 0 valid_rate 1082 batt pass2: min 166 total_min 166 total_cap 0 batt pass1: dev 0xc15e3100 ok valid state 1 cap 0 valid_rate 1082 batt pass2: min 166 total_min 166 total_cap 0 wb@chuck ~: wb@chuck ~: apm APM version: 1.2 APM Management: Enabled AC Line status: off-line Battery Status: low Remaining battery life: 0% Remaining battery time: 2:31:00 Number of batteries: 1 Battery 0: Battery Status: low Remaining battery life: 0% Remaining battery time: 2:31:00 wb@chuck ~: -- Wilko Bulte wilko@FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Mon Jul 25 23:19:48 2005 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BBB7516A41F; Mon, 25 Jul 2005 23:19:48 +0000 (GMT) (envelope-from lists@yazzy.org) Received: from mail.yazzy.org (mail.yazzy.org [217.8.140.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3938343D48; Mon, 25 Jul 2005 23:19:45 +0000 (GMT) (envelope-from lists@yazzy.org) Received: from localhost.localdomain (yazzy.yazzy.org [192.168.98.11]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yazzy.org (Postfix) with ESMTP id 387C439812; Tue, 26 Jul 2005 01:19:59 +0200 (CEST) Date: Tue, 26 Jul 2005 01:19:43 +0200 From: Marcin Jessa To: Nate Lawson Message-Id: <20050726011943.0abe83a0.lists@yazzy.org> In-Reply-To: <42E5134F.706@root.org> References: <42E1481F.5040306@root.org> <20050723133819.36efb537.lists@yazzy.org> <42E29CAA.1020007@root.org> <20050724215818.55f951ae.lists@yazzy.org> <42E42F10.3030309@root.org> <20050725091221.106a0368.lists@yazzy.org> <42E5134F.706@root.org> Organization: YazzY.org X-Mailer: Sylpheed version 1.0.4 (GTK+ 1.2.10; i386-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: acpi@freebsd.org, freebsd-current@freebsd.org Subject: Re: acpi battery rework patch 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: Mon, 25 Jul 2005 23:19:49 -0000 On Mon, 25 Jul 2005 09:29:03 -0700 Nate Lawson wrote: > Marcin Jessa wrote: > > On Sun, 24 Jul 2005 17:15:12 -0700 > > Nate Lawson wrote: > >>As far as Eric's result, I'll check that on my systems as well. I > >>_think_ the previous behavior was more correct (-1 = unknown) so I'll > >>commit this minor change. The "state" variable should not have changed > >>so please let me know for sure if it has. "1" means "discharging" which > >>doesn't sound right if you're on AC power. If you just recently plugged > >>in the laptop, try polling the status a few more times (apm(8) gives > >>more detail) and see if it catches up. Some systems lag reporting > >>various values until they are sure they've restabilized after an AC line > >>change. > >> > >>Marcin, if your system reports a valid rate of use, we can calculate > >>time. If you're on AC power, there is no time available (since your > >>batteries aren't discharging at any rate). Try a previous > >>kernel/acpi.ko to be certain what the behavior used to be. > > > > > > [yazzy@lapdance:~]> uname -a > > FreeBSD lapdance.yazzy.net 6.0-BETA1 FreeBSD 6.0-BETA1 #4: Sat Jul 23 17:35:13 CEST 2005 root@lapdance.yazzy.net:/usr/obj/usr/src/sys/LAPDANCE-6.0 i386 > > > > Running on AC: > > [yazzy@lapdance:~]> sysctl -a | grep battery > > hw.acpi.battery.life: 23 > > hw.acpi.battery.time: -1 > > hw.acpi.battery.state: 2 > > hw.acpi.battery.units: 1 > > hw.acpi.battery.info_expire: 5 > > > > Running on battery: > > [yazzy@lapdance:~]> sysctl -a | grep battery > > hw.acpi.battery.life: 23 > > hw.acpi.battery.time: 41 > > hw.acpi.battery.state: 1 > > hw.acpi.battery.units: 1 > > hw.acpi.battery.info_expire: 5 > > [yazzy@lapdance:~]> > > And with a 7-current kernel, everything is the same except "time" is > always -1 both on and off AC power? > > Please try this patch with 7-current and report its output both on and > off power. It prints out more debugging info each time the battery is read. > > -- > Nate > Test results: Running on 6.0-BETA1 #4: Sat Jul 23 17:35:13 CEST 2005 - AC: hw.acpi.battery.life: 99 hw.acpi.battery.time: -1 hw.acpi.battery.state: 0 hw.acpi.battery.units: 1 hw.acpi.battery.info_expire: 5 - Battery: hw.acpi.battery.life: 87 hw.acpi.battery.time: 103 hw.acpi.battery.state: 1 hw.acpi.battery.units: 1 hw.acpi.battery.info_expire: 5 Back on AC (notice battery.state changed to 2 from previous 0 on AC (charging) ) hw.acpi.battery.life: 86 hw.acpi.battery.time: -1 hw.acpi.battery.state: 2 hw.acpi.battery.units: 1 hw.acpi.battery.info_expire: 5 Running on FreeBSD 7.0-CURRENT #5: Mon Jul 25 22:21:05 CEST 2005 without the patch - AC: hw.acpi.battery.life: 100 hw.acpi.battery.time: -1 hw.acpi.battery.state: 0 hw.acpi.battery.units: 1 hw.acpi.battery.info_expire: 5 - Battery: hw.acpi.battery.life: 99 hw.acpi.battery.time: 113 hw.acpi.battery.state: 1 hw.acpi.battery.units: 1 hw.acpi.battery.info_expire: 5 Running on FreeBSD 7.0-CURRENT #5: Mon Jul 25 22:21:05 CEST 2005 with the patch: # sysctl -a | grep battery - AC: hw.acpi.battery.life: 70 hw.acpi.battery.time: -1 hw.acpi.battery.state: 2 hw.acpi.battery.units: 1 hw.acpi.battery.info_expire: 5 dev.battery.0.%desc: ACPI Control Method Battery dev.battery.0.%driver: battery dev.battery.0.%location: handle=\_SB_.PCI0.LPC_.EC__.BAT0 dev.battery.0.%pnpinfo: _HID=PNP0C0A _UID=0 dev.battery.0.%parent: acpi0 - Battery: hw.acpi.battery.life: 70 hw.acpi.battery.time: 125 hw.acpi.battery.state: 1 hw.acpi.battery.units: 1 hw.acpi.battery.info_expire: 5 dev.battery.0.%desc: ACPI Control Method Battery dev.battery.0.%driver: battery dev.battery.0.%location: handle=\_SB_.PCI0.LPC_.EC__.BAT0 dev.battery.0.%pnpinfo: _HID=PNP0C0A _UID=0 dev.battery.0.%parent: acpi0 From owner-freebsd-acpi@FreeBSD.ORG Tue Jul 26 05:26:17 2005 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1CA5916A41F; Tue, 26 Jul 2005 05:26:17 +0000 (GMT) (envelope-from nate@root.org) Received: from ylpvm12.prodigy.net (ylpvm12-ext.prodigy.net [207.115.57.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D89143D45; Tue, 26 Jul 2005 05:26:16 +0000 (GMT) (envelope-from nate@root.org) Received: from pimout5-ext.prodigy.net (pimout5-int.prodigy.net [207.115.4.21]) by ylpvm12.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id j6Q5Q7Hv031918; Tue, 26 Jul 2005 01:26:07 -0400 X-ORBL: [64.171.187.230] Received: from [10.0.5.50] (adsl-64-171-187-230.dsl.snfc21.pacbell.net [64.171.187.230]) by pimout5-ext.prodigy.net (8.13.4 outbound domainkey aix/8.13.4) with ESMTP id j6Q5QB7c089748; Tue, 26 Jul 2005 01:26:12 -0400 Message-ID: <42E5C96C.9060105@root.org> Date: Mon, 25 Jul 2005 22:26:04 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050723) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Marcin Jessa References: <42E1481F.5040306@root.org> <20050723133819.36efb537.lists@yazzy.org> <42E29CAA.1020007@root.org> <20050724215818.55f951ae.lists@yazzy.org> <42E42F10.3030309@root.org> <20050725091221.106a0368.lists@yazzy.org> <42E5134F.706@root.org> <20050726011943.0abe83a0.lists@yazzy.org> In-Reply-To: <20050726011943.0abe83a0.lists@yazzy.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: acpi@freebsd.org, freebsd-current@freebsd.org Subject: Re: acpi battery rework patch 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: Tue, 26 Jul 2005 05:26:17 -0000 Marcin Jessa wrote: > On Mon, 25 Jul 2005 09:29:03 -0700 > Nate Lawson wrote: >>Marcin Jessa wrote: >> >>>On Sun, 24 Jul 2005 17:15:12 -0700 >>>Nate Lawson wrote: >>>> >>>>Marcin, if your system reports a valid rate of use, we can calculate >>>>time. If you're on AC power, there is no time available (since your >>>>batteries aren't discharging at any rate). Try a previous >>>>kernel/acpi.ko to be certain what the behavior used to be. >>> >>And with a 7-current kernel, everything is the same except "time" is >>always -1 both on and off AC power? >> >>Please try this patch with 7-current and report its output both on and >>off power. It prints out more debugging info each time the battery is read. > > Test results: > > Running on 6.0-BETA1 #4: Sat Jul 23 17:35:13 CEST 2005 > - AC: > hw.acpi.battery.life: 99 > hw.acpi.battery.time: -1 > hw.acpi.battery.state: 0 > > - Battery: > hw.acpi.battery.life: 87 > hw.acpi.battery.time: 103 > hw.acpi.battery.state: 1 Completely fine. Time should be -1 (unknown) while on AC power. And state is "discharging" when on battery. > Running on FreeBSD 7.0-CURRENT #5: Mon Jul 25 22:21:05 CEST 2005 without the patch > - AC: > hw.acpi.battery.life: 100 > hw.acpi.battery.time: -1 > hw.acpi.battery.state: 0 > > - Battery: > hw.acpi.battery.life: 99 > hw.acpi.battery.time: 113 > hw.acpi.battery.state: 1 Um, this is exactly the same as above before my battery rework commit. I fail to see anything wrong with it. > Running on FreeBSD 7.0-CURRENT #5: Mon Jul 25 22:21:05 CEST 2005 with the patch: The patch should not change anything since it just adds printfs to help get more info in case you had some bug. > - AC: > hw.acpi.battery.life: 70 > hw.acpi.battery.time: -1 > hw.acpi.battery.state: 2 This is fine. On AC power and state is charging. > - Battery: > hw.acpi.battery.life: 70 > hw.acpi.battery.time: 125 > hw.acpi.battery.state: 1 Time is valid and state is "discharging". There is no bug here, this info is correct and matches the kernel behavior before my commit. So what is the buggy behavior? -- Nate From owner-freebsd-acpi@FreeBSD.ORG Tue Jul 26 05:31:15 2005 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0618D16A41F; Tue, 26 Jul 2005 05:31:15 +0000 (GMT) (envelope-from nate@root.org) Received: from ylpvm15.prodigy.net (ylpvm15-ext.prodigy.net [207.115.57.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BE7143D45; Tue, 26 Jul 2005 05:31:14 +0000 (GMT) (envelope-from nate@root.org) Received: from pimout7-ext.prodigy.net (pimout7-int.prodigy.net [207.115.4.147]) by ylpvm15.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id j6Q5VaaR020098; Tue, 26 Jul 2005 01:31:37 -0400 X-ORBL: [64.171.187.230] Received: from [10.0.5.50] (adsl-64-171-187-230.dsl.snfc21.pacbell.net [64.171.187.230]) by pimout7-ext.prodigy.net (8.13.4 outbound domainkey aix/8.13.4) with ESMTP id j6Q5VBYL344590; Tue, 26 Jul 2005 01:31:12 -0400 Message-ID: <42E5CA9E.6080309@root.org> Date: Mon, 25 Jul 2005 22:31:10 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050723) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Wilko Bulte References: <42E1481F.5040306@root.org> <20050723133819.36efb537.lists@yazzy.org> <42E29CAA.1020007@root.org> <20050724215818.55f951ae.lists@yazzy.org> <42E42F10.3030309@root.org> <20050725091221.106a0368.lists@yazzy.org> <42E5134F.706@root.org> <20050725184101.GA41023@freebie.xs4all.nl> In-Reply-To: <20050725184101.GA41023@freebie.xs4all.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: acpi@freebsd.org, freebsd-current@freebsd.org Subject: Re: acpi battery rework patch 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: Tue, 26 Jul 2005 05:31:15 -0000 Wilko Bulte wrote: >>>On Sun, 24 Jul 2005 17:15:12 -0700 >>>Nate Lawson wrote: >>Please try this patch with 7-current and report its output both on and >>off power. It prints out more debugging info each time the battery is read. > > > On an Compaq EVO N160, on AC power > batt pass1: dev 0xc15e3100 ok valid state 2 cap 0 valid_rate 0 > batt pass2: min 0 total_min 0 total_cap 0 > ichss0: transition to 1 failed This is a separate issue, you should disable ichss: hint.ichss.0.disabled="1" It appears your chipset does not actually support it. I think bruno@ has a patch for doing more detailed checking for systems that actually support it. > batt pass1: dev 0xc15e3100 ok valid state 2 cap 0 valid_rate 0 > batt pass2: min 0 total_min 0 total_cap 0 > ichss0: transition to 1 failed > > APM version: 1.2 > APM Management: Enabled > AC Line status: on-line > Battery Status: charging > Remaining battery life: 0% > Remaining battery time: 0:00:00 > Number of batteries: 1 > Battery 0: > Battery Status: charging > Remaining battery life: 0% > Remaining battery time: 0:00:00 This is strange behavior. Your system is never reporting the current battery capacity (cap = 0) even though it reports a reasonable battery status (charging). > Unplugging AC power: > > batt pass1: dev 0xc15e3100 ok valid state 1 cap 0 valid_rate 1082 > batt pass2: min 166 total_min 166 total_cap 0 > > > wb@chuck ~: apm > APM version: 1.2 > APM Management: Enabled > AC Line status: off-line > Battery Status: low > Remaining battery life: 0% > Remaining battery time: 2:31:00 > Number of batteries: 1 > Battery 0: > Battery Status: low > Remaining battery life: 0% > Remaining battery time: 2:31:00 Again, it does not report a valid cap off power but does report a valid rate of use. Did you always have this behavior or was this introduced by my commit? -- Nate From owner-freebsd-acpi@FreeBSD.ORG Tue Jul 26 07:06:48 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 61A2716A41F for ; Tue, 26 Jul 2005 07:06:48 +0000 (GMT) (envelope-from m.ehinger@ltur.de) Received: from posty.gateway-inter.net (posty.gateway-inter.net [213.144.19.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0287243D48 for ; Tue, 26 Jul 2005 07:06:47 +0000 (GMT) (envelope-from m.ehinger@ltur.de) In-Reply-To: <42E51A7F.1010103@root.org> To: Nate Lawson Message-ID: From: m.ehinger@ltur.de Date: Tue, 26 Jul 2005 09:06:14 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Cc: freebsd-acpi@freebsd.org Subject: Re: ATI Radeon power management disabled after resume 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: Tue, 26 Jul 2005 07:06:48 -0000 I already ask these guys, but no annswer yet. BTW, it's the same behaviour without X. After a reboot without ever X being started, temperature of the GPU is about 45 degrees centigrade ( from acpi_ibm). Then i do a suspend and a resume the GPU temperature go up to 55 degrees centigrade and stays there (until next reboot or X starts with DynamicClocks). thanks Maik Nate Lawson 25.07.2005 18:59 An m.ehinger@ltur.de Kopie freebsd-acpi@freebsd.org Thema Re: ATI Radeon power management disabled after resume m.ehinger@ltur.de wrote: > Hi, > > don't know if this is the right list. If not i apologize. > > I recognized an temperature raise from about 10 degrees centigrade on my radeon 9600 GPU after i resume from suspend. everthing else > ist fine. > This happens on console and X. > > If i start the Xorg server with "DynamicClocks" enabled temperature drops within 10 seconds back to normal. > > Is there any tool to do this per command? > > I'm running FreeBSD 6-BETA1 on an Thinkpad T42 with ATI Radeon 9600 M10. > I got acpi_video and acpi_ibm loaded. (same behaviour when not loaded) I think Xorg should handle this. Unless the radeon exports some Dx state control via ACPI, only device-specific extensions like DynamicClocks can control the radeon. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Tue Jul 26 07:33:15 2005 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1659E16A41F; Tue, 26 Jul 2005 07:33:15 +0000 (GMT) (envelope-from lists@yazzy.org) Received: from mail.yazzy.org (mail.yazzy.org [217.8.140.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E6BD43D4C; Tue, 26 Jul 2005 07:33:14 +0000 (GMT) (envelope-from lists@yazzy.org) Received: from 217-13-2-82.dd.nextgentel.com ([217.13.2.82] helo=h311r4z3r) by mail.yazzy.org with esmtps (TLSv1:AES256-SHA:256) (YazzY.org) id 1DxJvq-0003D3-6d; Tue, 26 Jul 2005 09:32:56 +0200 Date: Tue, 26 Jul 2005 09:33:17 +0200 From: Marcin Jessa To: Nate Lawson Message-Id: <20050726093317.522452a6.lists@yazzy.org> In-Reply-To: <42E5C96C.9060105@root.org> References: <42E1481F.5040306@root.org> <20050723133819.36efb537.lists@yazzy.org> <42E29CAA.1020007@root.org> <20050724215818.55f951ae.lists@yazzy.org> <42E42F10.3030309@root.org> <20050725091221.106a0368.lists@yazzy.org> <42E5134F.706@root.org> <20050726011943.0abe83a0.lists@yazzy.org> <42E5C96C.9060105@root.org> Organization: YazzY.org X-Mailer: Sylpheed version 2.0.0rc (GTK+ 2.6.8; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Score: -2.5 (--) Cc: acpi@freebsd.org, freebsd-current@freebsd.org Subject: Re: acpi battery rework patch 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: Tue, 26 Jul 2005 07:33:15 -0000 On Mon, 25 Jul 2005 22:26:04 -0700 Nate Lawson wrote: > Marcin Jessa wrote: > > On Mon, 25 Jul 2005 09:29:03 -0700 > > Nate Lawson wrote: > >>Marcin Jessa wrote: > >> > >>>On Sun, 24 Jul 2005 17:15:12 -0700 > >>>Nate Lawson wrote: > >>>> > >>>>Marcin, if your system reports a valid rate of use, we can calculate > >>>>time. If you're on AC power, there is no time available (since your > >>>>batteries aren't discharging at any rate). Try a previous > >>>>kernel/acpi.ko to be certain what the behavior used to be. > >>> > >>And with a 7-current kernel, everything is the same except "time" is > >>always -1 both on and off AC power? > >> > >>Please try this patch with 7-current and report its output both on and > >>off power. It prints out more debugging info each time the battery is read. > > > > Test results: > > > > Running on 6.0-BETA1 #4: Sat Jul 23 17:35:13 CEST 2005 > > - AC: > > hw.acpi.battery.life: 99 > > hw.acpi.battery.time: -1 > > hw.acpi.battery.state: 0 > > > > - Battery: > > hw.acpi.battery.life: 87 > > hw.acpi.battery.time: 103 > > hw.acpi.battery.state: 1 > > Completely fine. Time should be -1 (unknown) while on AC power. And > state is "discharging" when on battery. > > > Running on FreeBSD 7.0-CURRENT #5: Mon Jul 25 22:21:05 CEST 2005 without the patch > > - AC: > > hw.acpi.battery.life: 100 > > hw.acpi.battery.time: -1 > > hw.acpi.battery.state: 0 > > > > - Battery: > > hw.acpi.battery.life: 99 > > hw.acpi.battery.time: 113 > > hw.acpi.battery.state: 1 > > Um, this is exactly the same as above before my battery rework commit. > I fail to see anything wrong with it. > > > Running on FreeBSD 7.0-CURRENT #5: Mon Jul 25 22:21:05 CEST 2005 with the patch: > > The patch should not change anything since it just adds printfs to help > get more info in case you had some bug. > > > - AC: > > hw.acpi.battery.life: 70 > > hw.acpi.battery.time: -1 > > hw.acpi.battery.state: 2 > > This is fine. On AC power and state is charging. > > > - Battery: > > hw.acpi.battery.life: 70 > > hw.acpi.battery.time: 125 > > hw.acpi.battery.state: 1 > > Time is valid and state is "discharging". > > There is no bug here, this info is correct and matches the kernel > behavior before my commit. So what is the buggy behavior? > In the first email i could not see the remining time when running on battery but then after a short while I sent one more email as reply to my own saying it showed up and this was propably becouse ACPI did not manage to get the battery state yet. I dont know if there was any bug. I thought you had some issues so I tried to help. It seems like we both wasted our time on a perfectly good code becouse you missed my second email :) Cheers, Marcin. P.S Do you still need my dmesg ? From owner-freebsd-acpi@FreeBSD.ORG Tue Jul 26 07:34:57 2005 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E089316A41F; Tue, 26 Jul 2005 07:34:57 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from smtp-vbr14.xs4all.nl (smtp-vbr14.xs4all.nl [194.109.24.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4420643D45; Tue, 26 Jul 2005 07:34:56 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp-vbr14.xs4all.nl (8.13.3/8.13.3) with ESMTP id j6Q7Ypbv060754; Tue, 26 Jul 2005 09:34:52 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.13.3/8.13.3) with ESMTP id j6Q7Ypnl044739; Tue, 26 Jul 2005 09:34:51 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.3/8.13.1/Submit) id j6Q7YpLD044738; Tue, 26 Jul 2005 09:34:51 +0200 (CEST) (envelope-from wb) Date: Tue, 26 Jul 2005 09:34:51 +0200 From: Wilko Bulte To: Nate Lawson Message-ID: <20050726073451.GA44706@freebie.xs4all.nl> References: <20050723133819.36efb537.lists@yazzy.org> <42E29CAA.1020007@root.org> <20050724215818.55f951ae.lists@yazzy.org> <42E42F10.3030309@root.org> <20050725091221.106a0368.lists@yazzy.org> <42E5134F.706@root.org> <20050725184101.GA41023@freebie.xs4all.nl> <42E5CA9E.6080309@root.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42E5CA9E.6080309@root.org> X-OS: FreeBSD 5.4-STABLE User-Agent: Mutt/1.5.9i X-Virus-Scanned: by XS4ALL Virus Scanner Cc: acpi@freebsd.org, freebsd-current@freebsd.org Subject: Re: acpi battery rework patch 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: Tue, 26 Jul 2005 07:34:58 -0000 On Mon, Jul 25, 2005 at 10:31:10PM -0700, Nate Lawson wrote.. > Wilko Bulte wrote: > >>>On Sun, 24 Jul 2005 17:15:12 -0700 > >>>Nate Lawson wrote: > >>Please try this patch with 7-current and report its output both on and > >>off power. It prints out more debugging info each time the battery is > >>read. > > > > > >On an Compaq EVO N160, on AC power > >batt pass1: dev 0xc15e3100 ok valid state 2 cap 0 valid_rate 0 > >batt pass2: min 0 total_min 0 total_cap 0 > >ichss0: transition to 1 failed > > This is a separate issue, you should disable ichss: > hint.ichss.0.disabled="1" > > It appears your chipset does not actually support it. I think bruno@ > has a patch for doing more detailed checking for systems that actually > support it. > > >batt pass1: dev 0xc15e3100 ok valid state 2 cap 0 valid_rate 0 > >batt pass2: min 0 total_min 0 total_cap 0 > >ichss0: transition to 1 failed > > > >APM version: 1.2 > >APM Management: Enabled > >AC Line status: on-line > >Battery Status: charging > >Remaining battery life: 0% > >Remaining battery time: 0:00:00 > >Number of batteries: 1 > >Battery 0: > > Battery Status: charging > > Remaining battery life: 0% > > Remaining battery time: 0:00:00 > > This is strange behavior. Your system is never reporting the current > battery capacity (cap = 0) even though it reports a reasonable battery > status (charging). Yep. It has always been this way. > >Unplugging AC power: > > > >batt pass1: dev 0xc15e3100 ok valid state 1 cap 0 valid_rate 1082 > >batt pass2: min 166 total_min 166 total_cap 0 > > > > > >wb@chuck ~: apm > >APM version: 1.2 > >APM Management: Enabled > >AC Line status: off-line > >Battery Status: low > >Remaining battery life: 0% > >Remaining battery time: 2:31:00 > >Number of batteries: 1 > >Battery 0: > > Battery Status: low > > Remaining battery life: 0% > > Remaining battery time: 2:31:00 > > Again, it does not report a valid cap off power but does report a valid > rate of use. > > Did you always have this behavior or was this introduced by my commit? Been there since a long time. -- Wilko Bulte wilko@FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Tue Jul 26 13:51:28 2005 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D61C916A41F; Tue, 26 Jul 2005 13:51:28 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from postfix4-2.free.fr (postfix4-2.free.fr [213.228.0.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2ABAD43D48; Tue, 26 Jul 2005 13:51:27 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (vol75-8-82-233-239-98.fbx.proxad.net [82.233.239.98]) by postfix4-2.free.fr (Postfix) with ESMTP id 91576323408; Tue, 26 Jul 2005 15:51:24 +0200 (CEST) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id B6E54405B; Tue, 26 Jul 2005 15:51:49 +0200 (CEST) Date: Tue, 26 Jul 2005 15:51:49 +0200 From: Jeremie Le Hen To: Nate Lawson Message-ID: <20050726135149.GG1610@obiwan.tataz.chchile.org> References: <20050723133819.36efb537.lists@yazzy.org> <42E29CAA.1020007@root.org> <20050724215818.55f951ae.lists@yazzy.org> <42E42F10.3030309@root.org> <20050725091221.106a0368.lists@yazzy.org> <42E5134F.706@root.org> <20050726011943.0abe83a0.lists@yazzy.org> <42E5C96C.9060105@root.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42E5C96C.9060105@root.org> User-Agent: Mutt/1.5.9i Cc: acpi@freebsd.org, Marcin Jessa , freebsd-current@freebsd.org Subject: Re: acpi battery rework patch 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: Tue, 26 Jul 2005 13:51:29 -0000 Hi Nate, > >- Battery: > >hw.acpi.battery.life: 87 > >hw.acpi.battery.time: 103 > >hw.acpi.battery.state: 1 > > Completely fine. Time should be -1 (unknown) while on AC power. And > state is "discharging" when on battery. > > >- AC: > >hw.acpi.battery.life: 70 > >hw.acpi.battery.time: -1 > >hw.acpi.battery.state: 2 > > This is fine. On AC power and state is charging. > > >- Battery: > >hw.acpi.battery.life: 70 > >hw.acpi.battery.time: 125 > >hw.acpi.battery.state: 1 > > Time is valid and state is "discharging". Where are these states documented ? What do you think of the idea of using the following as a description for the hw.acpi.battery.state sysctl ? "0: battery full, 1: discharging, 2: charging" Regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > From owner-freebsd-acpi@FreeBSD.ORG Tue Jul 26 16:10:16 2005 Return-Path: X-Original-To: freebsd-acpi@FreeBSD.org Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 44EF916A41F for ; Tue, 26 Jul 2005 16:10:16 +0000 (GMT) (envelope-from abalan@bitdefender.com) Received: from mail.bitdefender.com (ns.bitdefender.com [217.156.83.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4004543D49 for ; Tue, 26 Jul 2005 16:10:14 +0000 (GMT) (envelope-from abalan@bitdefender.com) Received: (qmail 32554 invoked by uid 1010); 26 Jul 2005 19:00:03 +0300 Content-Type: multipart/mixed; boundary="=-bd-boundary-2Siqjw6kd1J9P625" Mime-Version: 1.0 Received: from ns.bitdefender.com (HELO abalan.dsd.ro) (217.156.83.1) by mail.bitdefender.com with SMTP; 26 Jul 2005 19:00:03 +0300 Received: from localhost.dsd.ro (localhost.dsd.ro [127.0.0.1]) by abalan.dsd.ro (Postfix) with ESMTP id 0CFF213CA7C for ; Sun, 24 Jul 2005 12:31:11 +0300 (EEST) From: Alexandru Balan To: freebsd-acpi@FreeBSD.org Date: Sun, 24 Jul 2005 12:31:10 +0300 Message-Id: <1122197470.972.23.camel@abalan.dsd.ro> X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port X-BitDefender-SpamStamp: 1.1.4 049000040111 X-BitDefender-Scanner: Clean, Agent: BitDefender Qmail 1.6.2 on mail.bitdefender.com X-BitDefender-Spam: No (0) Cc: Subject: system resumes by itself after S3 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: Tue, 26 Jul 2005 16:10:16 -0000 This is a multipart message in MIME format, containing the original message body and a footer added by BitDefender --=-bd-boundary-2Siqjw6kd1J9P625 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-o7ofsaTtDkQaoTqfIkwt" --=-o7ofsaTtDkQaoTqfIkwt Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hello there, Ever since i was running 5.3-RELEASE acpiconf -s 3 had this problem for me: s3 worked just fine but after 2-3 seconds the system would wake up again. I tried removing every module i could from the kernel but with no luck. I updated to 5.3-STABLE and now i'm running 6.0-BETA1 ( RELENG_6 ) but nothing has changed. Any clues, anyone ? -- J --=-o7ofsaTtDkQaoTqfIkwt Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBC41/eDK3n/S1e+fYRAvlAAJ9Ul3LgsampX57m8VqtUz0BVaACMwCbBAw0 sHPEU2rO5Axbv82BHeeU5XA= =EVFf -----END PGP SIGNATURE----- --=-o7ofsaTtDkQaoTqfIkwt-- --=-bd-boundary-2Siqjw6kd1J9P625 Content-Type: text/plain; name="BitDefender.txt" Content-Disposition: inline; filename="BitDefender.txt" -- This message was scanned for spam and viruses by BitDefender. For more information please visit http://www.bitdefender.com/ --=-bd-boundary-2Siqjw6kd1J9P625-- From owner-freebsd-acpi@FreeBSD.ORG Tue Jul 26 17:32:49 2005 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A05B016A420 for ; Tue, 26 Jul 2005 17:32:49 +0000 (GMT) (envelope-from kjelderg@gmail.com) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id C183443D48 for ; Tue, 26 Jul 2005 17:32:48 +0000 (GMT) (envelope-from kjelderg@gmail.com) Received: by rproxy.gmail.com with SMTP id i8so3003rne for ; Tue, 26 Jul 2005 10:32:48 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=EW/0OT+Vp6upYjWwE9V1cE/bbZmcLkYBmAHBYVe7EyAT4sNTh55/HIt7JSDwetthnw81Ks0CgL83DUvJ/ylXuR2+iBhGzSO1kO6KLsZ7Rehls4IZGk6hv/QjZL52NElFW2EQcj2rhxNaiegXhc3ZkUppRxOtvrB1W2eVRhPQpd8= Received: by 10.38.89.20 with SMTP id m20mr6149rnb; Tue, 26 Jul 2005 10:32:48 -0700 (PDT) Received: by 10.38.101.41 with HTTP; Tue, 26 Jul 2005 10:32:48 -0700 (PDT) Message-ID: Date: Wed, 27 Jul 2005 02:32:48 +0900 From: Eric Kjeldergaard To: Jeremie Le Hen In-Reply-To: <20050726135149.GG1610@obiwan.tataz.chchile.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <42E29CAA.1020007@root.org> <20050724215818.55f951ae.lists@yazzy.org> <42E42F10.3030309@root.org> <20050725091221.106a0368.lists@yazzy.org> <42E5134F.706@root.org> <20050726011943.0abe83a0.lists@yazzy.org> <42E5C96C.9060105@root.org> <20050726135149.GG1610@obiwan.tataz.chchile.org> Cc: acpi@freebsd.org, Marcin Jessa , freebsd-current@freebsd.org Subject: Re: acpi battery rework patch X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Eric Kjeldergaard List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jul 2005 17:32:49 -0000 On 7/26/05, Jeremie Le Hen wrote: > Hi Nate, >=20 > > >- Battery: > > >hw.acpi.battery.life: 87 > > >hw.acpi.battery.time: 103 > > >hw.acpi.battery.state: 1 > >=20 > > Completely fine. Time should be -1 (unknown) while on AC power. And= =20 > > state is "discharging" when on battery. > >=20 > > >- AC: > > >hw.acpi.battery.life: 70 > > >hw.acpi.battery.time: -1 > > >hw.acpi.battery.state: 2 > >=20 > > This is fine. On AC power and state is charging. > >=20 > > >- Battery: > > >hw.acpi.battery.life: 70 > > >hw.acpi.battery.time: 125 > > >hw.acpi.battery.state: 1 > >=20 > > Time is valid and state is "discharging". >=20 > Where are these states documented ? What do you think of the idea of > using the following as a description for the hw.acpi.battery.state > sysctl ? > "0: battery full, 1: discharging, 2: charging" >=20 Along the same lines, I notice the following: [~/mp3] #sysctl -d hw.acpi.battery hw.acpi.battery: hw.acpi.battery.life: hw.acpi.battery.time: hw.acpi.battery.state: hw.acpi.battery.units: hw.acpi.battery.info_expire: Any chance of descriptions being added to all? =20 --=20 If I write a signature, my emails will appear more personalised. From owner-freebsd-acpi@FreeBSD.ORG Tue Jul 26 18:38:23 2005 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2324216A41F; Tue, 26 Jul 2005 18:38:23 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id ACB8443D45; Tue, 26 Jul 2005 18:38:22 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id j6QIcLH2002973; Tue, 26 Jul 2005 13:38:21 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <42E68319.40105@centtech.com> Date: Tue, 26 Jul 2005 13:38:17 -0500 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050603 X-Accept-Language: en-us, en MIME-Version: 1.0 To: acpi@freebsd.org, FreeBSD Current Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: More ACPI patch problems.. 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: Tue, 26 Jul 2005 18:38:23 -0000 After updating, I now see this when on battery: hw.acpi.battery.life: 97 hw.acpi.battery.time: 337898 hw.acpi.battery.state: 1 hw.acpi.battery.units: 2 hw.acpi.battery.info_expire: 5 And when on AC, my battery life never gets to 100% (like it used to). All my systems info is here: http://www.googlebit.com/freebsd/ Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-acpi@FreeBSD.ORG Tue Jul 26 18:46:11 2005 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 049A716A41F; Tue, 26 Jul 2005 18:46:11 +0000 (GMT) (envelope-from nate@root.org) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id A1AF143D45; Tue, 26 Jul 2005 18:46:10 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.33] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id j6QIk7o5016369 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 26 Jul 2005 11:46:10 -0700 Message-ID: <42E684EF.3030601@root.org> Date: Tue, 26 Jul 2005 11:46:07 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Marcin Jessa References: <42E1481F.5040306@root.org> <20050723133819.36efb537.lists@yazzy.org> <42E29CAA.1020007@root.org> <20050724215818.55f951ae.lists@yazzy.org> <42E42F10.3030309@root.org> <20050725091221.106a0368.lists@yazzy.org> <42E5134F.706@root.org> <20050726011943.0abe83a0.lists@yazzy.org> <42E5C96C.9060105@root.org> <20050726093317.522452a6.lists@yazzy.org> In-Reply-To: <20050726093317.522452a6.lists@yazzy.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: acpi@freebsd.org, freebsd-current@freebsd.org Subject: Re: acpi battery rework patch 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: Tue, 26 Jul 2005 18:46:11 -0000 Marcin Jessa wrote: > On Mon, 25 Jul 2005 22:26:04 -0700 > Nate Lawson wrote: >>There is no bug here, this info is correct and matches the kernel >>behavior before my commit. So what is the buggy behavior? > > > In the first email i could not see the remining time when running on battery but then after a short while I sent one more email as reply to my own saying it showed up and this was propably becouse ACPI did not manage to get the battery state yet. > I dont know if there was any bug. I thought you had some issues so I tried to help. > It seems like we both wasted our time on a perfectly good code becouse you missed my second email :) Ok, thanks for clearing this up. No more info is necessary. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Tue Jul 26 19:10:11 2005 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 55BFC16A41F; Tue, 26 Jul 2005 19:10:11 +0000 (GMT) (envelope-from nate@root.org) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id C612943D48; Tue, 26 Jul 2005 19:10:10 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.33] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id j6QJA6o5016644 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 26 Jul 2005 12:10:07 -0700 Message-ID: <42E68A8D.60002@root.org> Date: Tue, 26 Jul 2005 12:10:05 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Wilko Bulte References: <20050723133819.36efb537.lists@yazzy.org> <42E29CAA.1020007@root.org> <20050724215818.55f951ae.lists@yazzy.org> <42E42F10.3030309@root.org> <20050725091221.106a0368.lists@yazzy.org> <42E5134F.706@root.org> <20050725184101.GA41023@freebie.xs4all.nl> <42E5CA9E.6080309@root.org> <20050726073451.GA44706@freebie.xs4all.nl> In-Reply-To: <20050726073451.GA44706@freebie.xs4all.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: acpi@freebsd.org, freebsd-current@freebsd.org Subject: Re: acpi battery rework patch 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: Tue, 26 Jul 2005 19:10:11 -0000 Wilko Bulte wrote: >>>Unplugging AC power: >>> >>>batt pass1: dev 0xc15e3100 ok valid state 1 cap 0 valid_rate 1082 >>>batt pass2: min 166 total_min 166 total_cap 0 >>> >>> >>>wb@chuck ~: apm >>>APM version: 1.2 >>>APM Management: Enabled >>>AC Line status: off-line >>>Battery Status: low >>>Remaining battery life: 0% >>>Remaining battery time: 2:31:00 >>>Number of batteries: 1 >>>Battery 0: >>> Battery Status: low >>> Remaining battery life: 0% >>> Remaining battery time: 2:31:00 >> >>Again, it does not report a valid cap off power but does report a valid >>rate of use. >> >>Did you always have this behavior or was this introduced by my commit? > > > Been there since a long time. I'm afraid my commit can't fix the inability to read _BST info. We'll have to address that separately in acpi-ca or the acpi_cmbat driver once the problem is understood. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Tue Jul 26 19:11:38 2005 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 78EA716A41F; Tue, 26 Jul 2005 19:11:38 +0000 (GMT) (envelope-from nate@root.org) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F59543D45; Tue, 26 Jul 2005 19:11:38 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.33] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id j6QJBbo5016678 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 26 Jul 2005 12:11:38 -0700 Message-ID: <42E68AE8.2050600@root.org> Date: Tue, 26 Jul 2005 12:11:36 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jeremie Le Hen References: <20050723133819.36efb537.lists@yazzy.org> <42E29CAA.1020007@root.org> <20050724215818.55f951ae.lists@yazzy.org> <42E42F10.3030309@root.org> <20050725091221.106a0368.lists@yazzy.org> <42E5134F.706@root.org> <20050726011943.0abe83a0.lists@yazzy.org> <42E5C96C.9060105@root.org> <20050726135149.GG1610@obiwan.tataz.chchile.org> In-Reply-To: <20050726135149.GG1610@obiwan.tataz.chchile.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: acpi@freebsd.org, Marcin Jessa , freebsd-current@freebsd.org Subject: Re: acpi battery rework patch 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: Tue, 26 Jul 2005 19:11:38 -0000 Jeremie Le Hen wrote: > Hi Nate, > > >>>- Battery: >>>hw.acpi.battery.life: 87 >>>hw.acpi.battery.time: 103 >>>hw.acpi.battery.state: 1 >> >>Completely fine. Time should be -1 (unknown) while on AC power. And >>state is "discharging" when on battery. >> >> >>>- AC: >>>hw.acpi.battery.life: 70 >>>hw.acpi.battery.time: -1 >>>hw.acpi.battery.state: 2 >> >>This is fine. On AC power and state is charging. >> >> >>>- Battery: >>>hw.acpi.battery.life: 70 >>>hw.acpi.battery.time: 125 >>>hw.acpi.battery.state: 1 >> >>Time is valid and state is "discharging". > > > Where are these states documented ? What do you think of the idea of > using the following as a description for the hw.acpi.battery.state > sysctl ? > "0: battery full, 1: discharging, 2: charging" Currently in the acpiio.h header. Changing it to a string is a problem since multiple flags can be active at once, i.e. "discharging" + "critical". The apm(8) utility does a good job of parsing these so perhaps the same code could be used in the sysctl. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Tue Jul 26 19:12:12 2005 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0AD4116A41F; Tue, 26 Jul 2005 19:12:12 +0000 (GMT) (envelope-from nate@root.org) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id A482B43D58; Tue, 26 Jul 2005 19:12:10 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.33] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id j6QJC9o5016681 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 26 Jul 2005 12:12:10 -0700 Message-ID: <42E68B08.2030701@root.org> Date: Tue, 26 Jul 2005 12:12:09 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Kjeldergaard References: <42E29CAA.1020007@root.org> <20050724215818.55f951ae.lists@yazzy.org> <42E42F10.3030309@root.org> <20050725091221.106a0368.lists@yazzy.org> <42E5134F.706@root.org> <20050726011943.0abe83a0.lists@yazzy.org> <42E5C96C.9060105@root.org> <20050726135149.GG1610@obiwan.tataz.chchile.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: acpi@freebsd.org, Marcin Jessa , Jeremie Le Hen , freebsd-current@freebsd.org Subject: Re: acpi battery rework patch 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: Tue, 26 Jul 2005 19:12:12 -0000 Eric Kjeldergaard wrote: > On 7/26/05, Jeremie Le Hen wrote: > >>Hi Nate, >> >> >>>>- Battery: >>>>hw.acpi.battery.life: 87 >>>>hw.acpi.battery.time: 103 >>>>hw.acpi.battery.state: 1 >>> >>>Completely fine. Time should be -1 (unknown) while on AC power. And >>>state is "discharging" when on battery. >>> >>> >>>>- AC: >>>>hw.acpi.battery.life: 70 >>>>hw.acpi.battery.time: -1 >>>>hw.acpi.battery.state: 2 >>> >>>This is fine. On AC power and state is charging. >>> >>> >>>>- Battery: >>>>hw.acpi.battery.life: 70 >>>>hw.acpi.battery.time: 125 >>>>hw.acpi.battery.state: 1 >>> >>>Time is valid and state is "discharging". >> >>Where are these states documented ? What do you think of the idea of >>using the following as a description for the hw.acpi.battery.state >>sysctl ? >> "0: battery full, 1: discharging, 2: charging" >> > > > Along the same lines, I notice the following: > > [~/mp3] #sysctl -d hw.acpi.battery > hw.acpi.battery: > hw.acpi.battery.life: > hw.acpi.battery.time: > hw.acpi.battery.state: > hw.acpi.battery.units: > hw.acpi.battery.info_expire: > > Any chance of descriptions being added to all? > Yes, I have a patch for this and will try to roll it into a group of them later today. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Tue Jul 26 19:12:53 2005 Return-Path: X-Original-To: freebsd-acpi@FreeBSD.org Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3535F16A41F for ; Tue, 26 Jul 2005 19:12:53 +0000 (GMT) (envelope-from nate@root.org) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id C9D3343D46 for ; Tue, 26 Jul 2005 19:12:52 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.33] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id j6QJCno5016684 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 26 Jul 2005 12:12:49 -0700 Message-ID: <42E68B30.3000702@root.org> Date: Tue, 26 Jul 2005 12:12:48 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alexandru Balan References: <1122197470.972.23.camel@abalan.dsd.ro> In-Reply-To: <1122197470.972.23.camel@abalan.dsd.ro> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@FreeBSD.org Subject: Re: system resumes by itself after S3 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: Tue, 26 Jul 2005 19:12:53 -0000 Alexandru Balan wrote: > Hello there, > > Ever since i was running 5.3-RELEASE acpiconf -s 3 had this problem for > me: s3 worked just fine but after 2-3 seconds the system would wake up > again. I tried removing every module i could from the kernel but with no > luck. I updated to 5.3-STABLE and now i'm running 6.0-BETA1 ( RELENG_6 ) > but nothing has changed. Any clues, anyone ? Try disabling apic: hint.apic.0.disabled="1" Or compile it out of the kernel. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Tue Jul 26 19:16:09 2005 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8243216A41F; Tue, 26 Jul 2005 19:16:09 +0000 (GMT) (envelope-from nate@root.org) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2BFCF43D48; Tue, 26 Jul 2005 19:16:09 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.33] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id j6QJG7o5016700 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 26 Jul 2005 12:16:08 -0700 Message-ID: <42E68BF7.4040104@root.org> Date: Tue, 26 Jul 2005 12:16:07 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Anderson References: <42E68319.40105@centtech.com> In-Reply-To: <42E68319.40105@centtech.com> Content-Type: multipart/mixed; boundary="------------060207020005090501050003" Cc: acpi@freebsd.org, FreeBSD Current Subject: Re: More ACPI patch problems.. 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: Tue, 26 Jul 2005 19:16:09 -0000 This is a multi-part message in MIME format. --------------060207020005090501050003 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Eric Anderson wrote: > After updating, I now see this when on battery: > hw.acpi.battery.life: 97 > hw.acpi.battery.time: 337898 > hw.acpi.battery.state: 1 > hw.acpi.battery.units: 2 > hw.acpi.battery.info_expire: 5 > > And when on AC, my battery life never gets to 100% (like it used to). > > All my systems info is here: > http://www.googlebit.com/freebsd/ Can you run with the attached debug printf patch and let me know the output? Run it both on and off AC power. -- Nate --------------060207020005090501050003 Content-Type: text/plain; name="batt_dbg.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="batt_dbg.diff" Index: sys/dev/acpica/acpi_battery.c =================================================================== RCS file: /home/ncvs/src/sys/dev/acpica/acpi_battery.c,v retrieving revision 1.13 diff -u -r1.13 acpi_battery.c --- sys/dev/acpica/acpi_battery.c 23 Jul 2005 19:35:59 -0000 1.13 +++ sys/dev/acpica/acpi_battery.c 25 Jul 2005 15:59:29 -0000 @@ -161,6 +161,7 @@ error = ENOMEM; goto out; } +printf("batt pass1: dev %p ", batt_dev); /* Default info for every battery is "not present". */ acpi_reset_battinfo(&bi[i]); @@ -174,11 +175,13 @@ ACPI_BATT_GET_STATUS(batt_dev, &bst[i]) != 0 || ACPI_BATT_GET_INFO(batt_dev, bif) != 0) continue; +printf("ok "); /* If a battery is not installed, we sometimes get strange values. */ if (!acpi_battery_bst_valid(&bst[i]) || !acpi_battery_bif_valid(bif)) continue; +printf("valid "); /* Record state and calculate percent capacity remaining. */ valid_units++; @@ -204,10 +207,12 @@ */ if (bst[i].rate > 0 && (bst[i].state & ACPI_BATT_STAT_DISCHARG)) valid_rate += bst[i].rate; +printf("state %d cap %d valid_rate %d\n", bi[i].state, bi[i].cap, valid_rate); } /* If the caller asked for a device but we didn't find it, error. */ if (dev != NULL && dev_idx < 0) { +printf("batt: couldn't find dev %p\n", dev); error = ENXIO; goto out; } @@ -226,6 +231,8 @@ bi[i].min = 0; total_min += bi[i].min; total_cap += bi[i].cap; +printf("batt pass2: min %d total_min %d total_cap %d\n", bi[i].min, total_min, +total_cap); } /* --------------060207020005090501050003-- From owner-freebsd-acpi@FreeBSD.ORG Tue Jul 26 19:28:27 2005 Return-Path: X-Original-To: acpi@FreeBSD.ORG Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0FD6916A41F; Tue, 26 Jul 2005 19:28:27 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from smtp-vbr14.xs4all.nl (smtp-vbr14.xs4all.nl [194.109.24.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6ACD543D46; Tue, 26 Jul 2005 19:28:26 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp-vbr14.xs4all.nl (8.13.3/8.13.3) with ESMTP id j6QJSOh9079404; Tue, 26 Jul 2005 21:28:24 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.13.3/8.13.3) with ESMTP id j6QJSOio047333; Tue, 26 Jul 2005 21:28:24 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.3/8.13.1/Submit) id j6QJSOSk047332; Tue, 26 Jul 2005 21:28:24 +0200 (CEST) (envelope-from wb) Date: Tue, 26 Jul 2005 21:28:24 +0200 From: Wilko Bulte To: Nate Lawson Message-ID: <20050726192824.GB47305@freebie.xs4all.nl> References: <42E29CAA.1020007@root.org> <20050724215818.55f951ae.lists@yazzy.org> <42E42F10.3030309@root.org> <20050725091221.106a0368.lists@yazzy.org> <42E5134F.706@root.org> <20050725184101.GA41023@freebie.xs4all.nl> <42E5CA9E.6080309@root.org> <20050726073451.GA44706@freebie.xs4all.nl> <42E68A8D.60002@root.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42E68A8D.60002@root.org> X-OS: FreeBSD 5.4-STABLE User-Agent: Mutt/1.5.9i X-Virus-Scanned: by XS4ALL Virus Scanner Cc: acpi@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: acpi battery rework patch 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: Tue, 26 Jul 2005 19:28:27 -0000 On Tue, Jul 26, 2005 at 12:10:05PM -0700, Nate Lawson wrote.. > Wilko Bulte wrote: > >>>Unplugging AC power: > >>> > >>>batt pass1: dev 0xc15e3100 ok valid state 1 cap 0 valid_rate 1082 > >>>batt pass2: min 166 total_min 166 total_cap 0 > >>> > >>> > >>>wb@chuck ~: apm > >>>APM version: 1.2 > >>>APM Management: Enabled > >>>AC Line status: off-line > >>>Battery Status: low > >>>Remaining battery life: 0% > >>>Remaining battery time: 2:31:00 > >>>Number of batteries: 1 > >>>Battery 0: > >>> Battery Status: low > >>> Remaining battery life: 0% > >>> Remaining battery time: 2:31:00 > >> > >>Again, it does not report a valid cap off power but does report a valid > >>rate of use. > >> > >>Did you always have this behavior or was this introduced by my commit? > > > > > >Been there since a long time. > > I'm afraid my commit can't fix the inability to read _BST info. We'll > have to address that separately in acpi-ca or the acpi_cmbat driver once > the problem is understood. OK. Mind you, I am really happy with the progress ACPI has made to make this laptop work with it. Basically ACPI support moved from basically unusable to just this minor snag with the battery. Thanks for all the hours you spent on ACPI support! W/ -- Wilko Bulte wilko@FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Tue Jul 26 20:57:34 2005 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C189116A41F for ; Tue, 26 Jul 2005 20:57:34 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 30A5D43D49 for ; Tue, 26 Jul 2005 20:57:33 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id j6QKvSEZ030233; Tue, 26 Jul 2005 15:57:29 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <42E6A3B4.5000102@centtech.com> Date: Tue, 26 Jul 2005 15:57:24 -0500 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050603 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nate Lawson References: <42E68319.40105@centtech.com> <42E68BF7.4040104@root.org> In-Reply-To: <42E68BF7.4040104@root.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.82/993/Tue Jul 26 02:28:36 2005 on mh1.centtech.com X-Virus-Status: Clean Cc: acpi@freebsd.org Subject: Re: More ACPI patch problems.. 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: Tue, 26 Jul 2005 20:57:35 -0000 Nate Lawson wrote: > Eric Anderson wrote: > >> After updating, I now see this when on battery: >> hw.acpi.battery.life: 97 >> hw.acpi.battery.time: 337898 >> hw.acpi.battery.state: 1 >> hw.acpi.battery.units: 2 >> hw.acpi.battery.info_expire: 5 >> >> And when on AC, my battery life never gets to 100% (like it used to). >> >> All my systems info is here: >> http://www.googlebit.com/freebsd/ > > > Can you run with the attached debug printf patch and let me know the > output? Run it both on and off AC power. On bootup, with AC plugged in: Jul 26 15:50:02 neutrino kernel: start_init: trying /sbin/init Jul 26 15:50:02 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 0 cap 100 valid_rate 0 Jul 26 15:50:02 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 100 Jul 26 15:50:02 neutrino kernel: batt pass2: min 0 total_min 0 total_cap 99 Jul 26 15:50:02 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 0 cap 100 valid_rate 0 Jul 26 15:50:02 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 100 Jul 26 15:50:02 neutrino kernel: batt pass2: min 0 total_min 0 total_cap 99 Jul 26 15:50:02 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 0 cap 100 valid_rate 0 Jul 26 15:50:02 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 100 Jul 26 15:50:02 neutrino kernel: batt pass2: min 0 total_min 0 total_cap 99 Jul 26 15:50:02 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 0 cap 100 valid_rate 0 Jul 26 15:50:02 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 100 Jul 26 15:50:02 neutrino kernel: batt pass2: min 0 total_min 0 total_cap 99 Jul 26 15:50:02 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 0 cap 100 valid_rate 0 Jul 26 15:50:02 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 100 Jul 26 15:50:02 neutrino kernel: batt pass2: min 0 total_min 0 total_cap 99 Jul 26 15:50:02 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 0 cap 100 valid_rate 0 Jul 26 15:50:02 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 100 Jul 26 15:50:02 neutrino kernel: batt pass2: min 0 total_min 0 total_cap 99 Then another bunch: Jul 26 15:50:05 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 0 cap 100 valid_rate 0 Jul 26 15:50:05 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 100 Jul 26 15:50:05 neutrino kernel: batt pass2: min 0 total_min 0 total_cap 99 Jul 26 15:50:05 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 0 cap 100 valid_rate 0 Jul 26 15:50:05 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 100 Jul 26 15:50:05 neutrino kernel: batt pass2: min 0 total_min 0 total_cap 99 Jul 26 15:50:05 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 0 cap 100 valid_rate 0 Jul 26 15:50:05 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 100 Jul 26 15:50:05 neutrino kernel: batt pass2: min 0 total_min 0 total_cap 99 Jul 26 15:50:05 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 0 cap 100 valid_rate 0 Jul 26 15:50:05 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 100 Jul 26 15:50:05 neutrino kernel: batt pass2: min 0 total_min 0 total_cap 99 Jul 26 15:50:05 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 0 cap 100 valid_rate 0 Jul 26 15:50:05 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 100 Jul 26 15:50:05 neutrino kernel: batt pass2: min 0 total_min 0 total_cap 99 Jul 26 15:50:05 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 0 cap 100 valid_rate 0 Jul 26 15:50:05 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 100 Jul 26 15:50:05 neutrino kernel: batt pass2: min 0 total_min 0 total_cap 99 Then a whole bunch like this: [..snip..] Jul 26 15:52:48 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 0 cap 100 valid_rate 0 Jul 26 15:52:48 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 100 Jul 26 15:52:48 neutrino kernel: batt pass2: min 0 total_min 0 total_cap 99 Jul 26 15:52:48 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 0 cap 100 valid_rate 0 Jul 26 15:52:48 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 100 Jul 26 15:52:48 neutrino kernel: batt pass2: min 0 total_min 0 total_cap 99 Jul 26 15:52:48 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 0 cap 100 valid_rate 0 Jul 26 15:52:48 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 100 Jul 26 15:52:48 neutrino kernel: batt pass2: min 0 total_min 0 total_cap 99 Jul 26 15:52:48 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 0 cap 100 valid_rate 0 Jul 26 15:52:48 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 100 Jul 26 15:52:48 neutrino kernel: batt pass2: min 0 total_min 0 total_cap 99 Now on battery: Jul 26 15:55:23 neutrino kernel: system power profile changed to 'economy' Jul 26 15:55:23 neutrino kernel: acpi_acad0: Off Line Jul 26 15:55:23 neutrino power_profile: changed to 'economy' Jul 26 15:55:25 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 0 cap 100 valid_rate 0 Jul 26 15:55:25 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 100 Jul 26 15:55:25 neutrino kernel: batt pass2: min 0 total_min 0 total_cap 99 Jul 26 15:55:25 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 0 cap 100 valid_rate 0 Jul 26 15:55:25 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 100 Jul 26 15:55:25 neutrino kernel: batt pass2: min 0 total_min 0 total_cap 99 Jul 26 15:55:25 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 0 cap 100 valid_rate 0 Jul 26 15:55:25 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 100 Jul 26 15:55:25 neutrino kernel: batt pass2: min 0 total_min 0 total_cap 99 Jul 26 15:55:25 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 0 cap 100 valid_rate 0 Jul 26 15:55:25 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 100 Jul 26 15:55:25 neutrino kernel: batt pass2: min 0 total_min 0 total_cap 99 Jul 26 15:55:27 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 0 cap 100 valid_rate 0 Jul 26 15:55:27 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 100 Jul 26 15:55:27 neutrino kernel: batt pass2: min 0 total_min 0 total_cap 99 Jul 26 15:55:27 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 0 cap 100 valid_rate 0 Jul 26 15:55:27 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 100 Jul 26 15:55:27 neutrino kernel: batt pass2: min 0 total_min 0 total_cap 99 Jul 26 15:55:27 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 0 cap 100 valid_rate 0 Jul 26 15:55:27 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 100 Jul 26 15:55:27 neutrino kernel: batt pass2: min 0 total_min 0 total_cap 99 Jul 26 15:55:27 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 0 cap 100 valid_rate 0 Jul 26 15:55:27 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 100 Jul 26 15:55:27 neutrino kernel: batt pass2: min 0 total_min 0 total_cap 99 Jul 26 15:55:29 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 0 cap 94 valid_rate 0 Jul 26 15:55:29 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 94 Jul 26 15:55:29 neutrino kernel: batt pass2: min 0 total_min 0 total_cap 93 Jul 26 15:55:29 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 0 cap 94 valid_rate 0 Jul 26 15:55:29 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 94 Jul 26 15:55:29 neutrino kernel: batt pass2: min 0 total_min 0 total_cap 93 Jul 26 15:55:29 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 0 cap 94 valid_rate 0 Jul 26 15:55:29 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 94 Jul 26 15:55:29 neutrino kernel: batt pass2: min 0 total_min 0 total_cap 93 Jul 26 15:55:29 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 0 cap 94 valid_rate 0 Jul 26 15:55:29 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 94 Jul 26 15:55:29 neutrino kernel: batt pass2: min 0 total_min 0 total_cap 93 Jul 26 15:55:31 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 0 cap 94 valid_rate 0 Jul 26 15:55:31 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 94 Jul 26 15:55:31 neutrino kernel: batt pass2: min 0 total_min 0 total_cap 93 Jul 26 15:55:31 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 0 cap 94 valid_rate 0 Jul 26 15:55:31 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 94 Jul 26 15:55:31 neutrino kernel: batt pass2: min 0 total_min 0 total_cap 93 Jul 26 15:55:31 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 0 cap 94 valid_rate 0 Jul 26 15:55:31 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 94 Jul 26 15:55:31 neutrino kernel: batt pass2: min 0 total_min 0 total_cap 93 Jul 26 15:55:31 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 0 cap 94 valid_rate 0 Jul 26 15:55:31 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 94 Jul 26 15:55:31 neutrino kernel: batt pass2: min 0 total_min 0 total_cap 93 Jul 26 15:55:33 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 0 cap 94 valid_rate 0 Jul 26 15:55:33 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 94 Jul 26 15:55:33 neutrino kernel: batt pass2: min 0 total_min 0 total_cap 93 Jul 26 15:55:33 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 0 cap 94 valid_rate 0 Jul 26 15:55:33 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 94 Jul 26 15:55:33 neutrino kernel: batt pass2: min 0 total_min 0 total_cap 93 Jul 26 15:55:33 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 0 cap 94 valid_rate 0 Jul 26 15:55:33 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 94 Jul 26 15:55:33 neutrino kernel: batt pass2: min 0 total_min 0 total_cap 93 Jul 26 15:55:33 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 0 cap 94 valid_rate 0 Jul 26 15:55:33 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 94 Jul 26 15:55:33 neutrino kernel: batt pass2: min 0 total_min 0 total_cap 93 And then something like: Jul 26 15:56:30 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 1 cap 93 valid_rate 2483 Jul 26 15:56:30 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 104 total_min 104 total_cap 93 Jul 26 15:56:30 neutrino kernel: batt pass2: min 329216 total_min 329320 total_cap 92 Jul 26 15:56:30 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 1 cap 93 valid_rate 2483 Jul 26 15:56:30 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 104 total_min 104 total_cap 93 Jul 26 15:56:30 neutrino kernel: batt pass2: min 329216 total_min 329320 total_cap 92 Jul 26 15:56:30 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 1 cap 93 valid_rate 2483 Jul 26 15:56:30 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 104 total_min 104 total_cap 93 Jul 26 15:56:30 neutrino kernel: batt pass2: min 329216 total_min 329320 total_cap 92 Jul 26 15:56:30 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 1 cap 93 valid_rate 2483 Jul 26 15:56:30 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 104 total_min 104 total_cap 93 Jul 26 15:56:30 neutrino kernel: batt pass2: min 329216 total_min 329320 total_cap 92 Jul 26 15:56:32 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 1 cap 93 valid_rate 2483 Jul 26 15:56:32 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 104 total_min 104 total_cap 93 Jul 26 15:56:32 neutrino kernel: batt pass2: min 329216 total_min 329320 total_cap 92 Jul 26 15:56:32 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 1 cap 93 valid_rate 2483 Jul 26 15:56:32 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 104 total_min 104 total_cap 93 Jul 26 15:56:32 neutrino kernel: batt pass2: min 329216 total_min 329320 total_cap 92 Jul 26 15:56:32 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 1 cap 93 valid_rate 2483 Jul 26 15:56:32 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 104 total_min 104 total_cap 93 Jul 26 15:56:32 neutrino kernel: batt pass2: min 329216 total_min 329320 total_cap 92 Jul 26 15:56:32 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 1 cap 93 valid_rate 2483 Jul 26 15:56:32 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 104 total_min 104 total_cap 93 Jul 26 15:56:32 neutrino kernel: batt pass2: min 329216 total_min 329320 total_cap 92 Jul 26 15:56:34 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 1 cap 93 valid_rate 2483 Jul 26 15:56:34 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 104 total_min 104 total_cap 93 Jul 26 15:56:34 neutrino kernel: batt pass2: min 329216 total_min 329320 total_cap 92 Jul 26 15:56:34 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 1 cap 93 valid_rate 2483 Jul 26 15:56:34 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 104 total_min 104 total_cap 93 Jul 26 15:56:34 neutrino kernel: batt pass2: min 329216 total_min 329320 total_cap 92 Jul 26 15:56:34 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 1 cap 93 valid_rate 2483 Jul 26 15:56:34 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 104 total_min 104 total_cap 93 Jul 26 15:56:34 neutrino kernel: batt pass2: min 329216 total_min 329320 total_cap 92 Jul 26 15:56:34 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 1 cap 93 valid_rate 2483 Jul 26 15:56:34 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 104 total_min 104 total_cap 93 Jul 26 15:56:34 neutrino kernel: batt pass2: min 329216 total_min 329320 total_cap 92 Jul 26 15:56:36 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 1 cap 93 valid_rate 2483 Jul 26 15:56:36 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 104 total_min 104 total_cap 93 Jul 26 15:56:36 neutrino kernel: batt pass2: min 329216 total_min 329320 total_cap 92 Jul 26 15:56:36 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 1 cap 93 valid_rate 2483 Jul 26 15:56:36 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 104 total_min 104 total_cap 93 Jul 26 15:56:36 neutrino kernel: batt pass2: min 329216 total_min 329320 total_cap 92 Jul 26 15:56:36 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 1 cap 93 valid_rate 2483 Jul 26 15:56:36 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 104 total_min 104 total_cap 93 Jul 26 15:56:36 neutrino kernel: batt pass2: min 329216 total_min 329320 total_cap 92 Jul 26 15:56:36 neutrino kernel: batt pass1: dev 0xc22f7500 ok valid state 1 cap 93 valid_rate 2483 Jul 26 15:56:36 neutrino kernel: batt pass1: dev 0xc22f7880 batt pass2: min 104 total_min 104 total_cap 93 Jul 26 15:56:36 neutrino kernel: batt pass2: min 329216 total_min 329320 total_cap 92 Does that help any? Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-acpi@FreeBSD.ORG Thu Jul 28 18:21:09 2005 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C624B16A41F for ; Thu, 28 Jul 2005 18:21:09 +0000 (GMT) (envelope-from nate@root.org) Received: from ylpvm12.prodigy.net (ylpvm12-ext.prodigy.net [207.115.57.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 62B5943D55 for ; Thu, 28 Jul 2005 18:21:09 +0000 (GMT) (envelope-from nate@root.org) Received: from pimout5-ext.prodigy.net (pimout5-int.prodigy.net [207.115.4.21]) by ylpvm12.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id j6SIKxcm015813 for ; Thu, 28 Jul 2005 14:21:00 -0400 X-ORBL: [67.119.74.222] Received: from [10.0.0.33] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by pimout5-ext.prodigy.net (8.13.4 outbound domainkey aix/8.13.4) with ESMTP id j6SIKxjP472648; Thu, 28 Jul 2005 14:21:06 -0400 Message-ID: <42E9220A.4030007@root.org> Date: Thu, 28 Jul 2005 11:20:58 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050723) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Anderson References: <42E68319.40105@centtech.com> <42E68BF7.4040104@root.org> <42E6A3B4.5000102@centtech.com> In-Reply-To: <42E6A3B4.5000102@centtech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: acpi@freebsd.org Subject: Re: More ACPI patch problems.. 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: Thu, 28 Jul 2005 18:21:09 -0000 Eric Anderson wrote: > Nate Lawson wrote: > >> Eric Anderson wrote: >> >>> After updating, I now see this when on battery: >>> hw.acpi.battery.life: 97 >>> hw.acpi.battery.time: 337898 >>> hw.acpi.battery.state: 1 >>> hw.acpi.battery.units: 2 >>> hw.acpi.battery.info_expire: 5 >>> >>> And when on AC, my battery life never gets to 100% (like it used to). >>> >>> All my systems info is here: >>> http://www.googlebit.com/freebsd/ >> >> Can you run with the attached debug printf patch and let me know the >> output? Run it both on and off AC power. > > On bootup, with AC plugged in: > batt pass1: dev 0xc22f7500 ok valid state 0 cap 100 valid_rate 0 > batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 100 > batt pass2: min 0 total_min 0 total_cap 99 > batt pass1: dev 0xc22f7500 ok valid state 0 cap 100 valid_rate 0 > batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 100 > batt pass2: min 0 total_min 0 total_cap 99 This is fine. It appears your second battery is not present. > Now on battery: > power_profile: changed to 'economy' > batt pass1: dev 0xc22f7500 ok valid state 0 cap 100 valid_rate 0 > batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 100 > batt pass2: min 0 total_min 0 total_cap 99 > batt pass1: dev 0xc22f7500 ok valid state 0 cap 100 valid_rate 0 > batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 100 > batt pass2: min 0 total_min 0 total_cap 99 > > And then something like: > batt pass1: dev 0xc22f7500 ok valid state 1 cap 93 valid_rate 2483 > batt pass1: dev 0xc22f7880 batt pass2: min 104 total_min 104 total_cap 93 > batt pass2: min 329216 total_min 329320 total_cap 92 > batt pass1: dev 0xc22f7500 ok valid state 1 cap 93 valid_rate 2483 > batt pass1: dev 0xc22f7880 batt pass2: min 104 total_min 104 total_cap 93 > batt pass2: min 329216 total_min 329320 total_cap 92 It appears we're getting invalid capacity data from the not-present 2nd battery. I just committed a patch that should fix this -- it zeroes the memory in question so we don't get random values for a battery that isn't present. Please let me know if it fixes this for you. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Thu Jul 28 19:38:09 2005 Return-Path: X-Original-To: freebsd-acpi@hub.freebsd.org Delivered-To: freebsd-acpi@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4432416A421; Thu, 28 Jul 2005 19:38:09 +0000 (GMT) (envelope-from njl@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D89643D72; Thu, 28 Jul 2005 19:38:05 +0000 (GMT) (envelope-from njl@FreeBSD.org) Received: from freefall.freebsd.org (njl@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j6SJc5jg060686; Thu, 28 Jul 2005 19:38:05 GMT (envelope-from njl@freefall.freebsd.org) Received: (from njl@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j6SJc40i060682; Thu, 28 Jul 2005 19:38:04 GMT (envelope-from njl) Date: Thu, 28 Jul 2005 19:38:04 GMT From: Nate Lawson Message-Id: <200507281938.j6SJc40i060682@freefall.freebsd.org> To: cejkar@fit.vutbr.cz, njl@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-acpi@FreeBSD.org Cc: Subject: Re: bin/83672: acpiconf with remaining battery life and time 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: Thu, 28 Jul 2005 19:38:09 -0000 Synopsis: acpiconf with remaining battery life and time State-Changed-From-To: open->closed State-Changed-By: njl State-Changed-When: Thu Jul 28 19:37:29 GMT 2005 State-Changed-Why: Committed variants of these, hope to MFC them to 6.0-RELEASE. Thanks. Responsible-Changed-From-To: freebsd-bugs->freebsd-acpi Responsible-Changed-By: njl Responsible-Changed-When: Thu Jul 28 19:37:29 GMT 2005 Responsible-Changed-Why: Committed variants of these, hope to MFC them to 6.0-RELEASE. Thanks. http://www.freebsd.org/cgi/query-pr.cgi?pr=83672 From owner-freebsd-acpi@FreeBSD.ORG Fri Jul 29 02:37:18 2005 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2655A16A41F for ; Fri, 29 Jul 2005 02:37:18 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E20D43D46 for ; Fri, 29 Jul 2005 02:37:17 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [192.168.42.23] (andersonbox3.centtech.com [192.168.42.23]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id j6T2bEux071554; Thu, 28 Jul 2005 21:37:14 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <42E99654.6010501@centtech.com> Date: Thu, 28 Jul 2005 21:37:08 -0500 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050603 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nate Lawson References: <42E68319.40105@centtech.com> <42E68BF7.4040104@root.org> <42E6A3B4.5000102@centtech.com> <42E9220A.4030007@root.org> In-Reply-To: <42E9220A.4030007@root.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: acpi@freebsd.org Subject: Re: More ACPI patch problems.. 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, 29 Jul 2005 02:37:18 -0000 Nate Lawson wrote: > Eric Anderson wrote: > >> Nate Lawson wrote: >> >>> Eric Anderson wrote: >>> >>>> After updating, I now see this when on battery: >>>> hw.acpi.battery.life: 97 >>>> hw.acpi.battery.time: 337898 >>>> hw.acpi.battery.state: 1 >>>> hw.acpi.battery.units: 2 >>>> hw.acpi.battery.info_expire: 5 >>>> >>>> And when on AC, my battery life never gets to 100% (like it used to). >>>> >>>> All my systems info is here: >>>> http://www.googlebit.com/freebsd/ >>> >>> >>> Can you run with the attached debug printf patch and let me know the >>> output? Run it both on and off AC power. >> >> >> On bootup, with AC plugged in: >> batt pass1: dev 0xc22f7500 ok valid state 0 cap 100 valid_rate 0 >> batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 100 >> batt pass2: min 0 total_min 0 total_cap 99 >> batt pass1: dev 0xc22f7500 ok valid state 0 cap 100 valid_rate 0 >> batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 100 >> batt pass2: min 0 total_min 0 total_cap 99 > > > This is fine. It appears your second battery is not present. > >> Now on battery: >> power_profile: changed to 'economy' >> batt pass1: dev 0xc22f7500 ok valid state 0 cap 100 valid_rate 0 >> batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 100 >> batt pass2: min 0 total_min 0 total_cap 99 >> batt pass1: dev 0xc22f7500 ok valid state 0 cap 100 valid_rate 0 >> batt pass1: dev 0xc22f7880 batt pass2: min 0 total_min 0 total_cap 100 >> batt pass2: min 0 total_min 0 total_cap 99 >> >> And then something like: >> batt pass1: dev 0xc22f7500 ok valid state 1 cap 93 valid_rate 2483 >> batt pass1: dev 0xc22f7880 batt pass2: min 104 total_min 104 total_cap 93 >> batt pass2: min 329216 total_min 329320 total_cap 92 >> batt pass1: dev 0xc22f7500 ok valid state 1 cap 93 valid_rate 2483 >> batt pass1: dev 0xc22f7880 batt pass2: min 104 total_min 104 total_cap 93 >> batt pass2: min 329216 total_min 329320 total_cap 92 > > > It appears we're getting invalid capacity data from the not-present 2nd > battery. I just committed a patch that should fix this -- it zeroes the > memory in question so we don't get random values for a battery that > isn't present. > > Please let me know if it fixes this for you. Yea, that did the trick, thanks! However, my battery still only gets to 99%. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-acpi@FreeBSD.ORG Fri Jul 29 06:42:52 2005 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1164916A41F for ; Fri, 29 Jul 2005 06:42:52 +0000 (GMT) (envelope-from roth@droopy.unibe.ch) Received: from mailhub04.unibe.ch (mailhub04-eth0.unibe.ch [130.92.9.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8AEB443D45 for ; Fri, 29 Jul 2005 06:42:51 +0000 (GMT) (envelope-from roth@droopy.unibe.ch) Received: from localhost (scanhub03.unibe.ch [130.92.254.67]) by mailhub04.unibe.ch (Postfix) with ESMTP id E82D9103C6; Fri, 29 Jul 2005 08:42:49 +0200 (CEST) Received: from mailhub04.unibe.ch ([130.92.9.71]) by localhost (scanhub03.unibe.ch [130.92.254.67]) (amavisd-new, port 10024) with LMTP id 14543-06-65; Fri, 29 Jul 2005 08:42:48 +0200 (CEST) Received: from asterix.unibe.ch (asterix.unibe.ch [130.92.64.4]) by mailhub04.unibe.ch (Postfix) with ESMTP id B810F103F5; Fri, 29 Jul 2005 08:42:48 +0200 (CEST) Received: from droopy.unibe.ch (droopy [130.92.64.20]) by asterix.unibe.ch (8.12.10+Sun/8.12.10) with ESMTP id j6T6gmdB017377; Fri, 29 Jul 2005 08:42:48 +0200 (MEST) Received: (from roth@localhost) by droopy.unibe.ch (8.12.10+Sun/8.12.9/Submit) id j6T6ghpS010842; Fri, 29 Jul 2005 08:42:43 +0200 (MEST) Date: Fri, 29 Jul 2005 08:42:43 +0200 From: Tobias Roth To: Eric Anderson Message-ID: <20050729064243.GA10813@droopy.unibe.ch> References: <42E68319.40105@centtech.com> <42E68BF7.4040104@root.org> <42E6A3B4.5000102@centtech.com> <42E9220A.4030007@root.org> <42E99654.6010501@centtech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42E99654.6010501@centtech.com> User-Agent: Mutt/1.4i X-message-flag: Warning! Using Outlook is insecure and promotes virus distribution. Please use a different email client. X-Virus-checked: by University of Berne Cc: acpi@freebsd.org Subject: Re: More ACPI patch problems.. 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, 29 Jul 2005 06:42:52 -0000 On Thu, Jul 28, 2005 at 09:37:08PM -0500, Eric Anderson wrote: > > However, my battery still only gets to 99%. Sorry for jumping in like this and not having read the whole thread before giving my .02 euros. But this looks quite normal. Older batteries tend not to be able to store the full design capacity, hence they will not go back up to 100% loaded. That's how it has been displayed for as long as I have had access to a laptop with FreeBSD. cheers, t. From owner-freebsd-acpi@FreeBSD.ORG Fri Jul 29 09:48:56 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C144B16A41F for ; Fri, 29 Jul 2005 09:48:56 +0000 (GMT) (envelope-from m.ehinger@ltur.de) Received: from posty.gateway-inter.net (posty.gateway-inter.net [213.144.19.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D67443D48 for ; Fri, 29 Jul 2005 09:48:56 +0000 (GMT) (envelope-from m.ehinger@ltur.de) To: freebsd-acpi@freebsd.org Message-ID: From: m.ehinger@ltur.de Date: Fri, 29 Jul 2005 11:48:22 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Subject: No battery critical warning on Thinkpad t42 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, 29 Jul 2005 09:48:57 -0000 Hello, i recognized that an my Thinkpad T42 i get no battery critical warnings! All i get is a battery low state. hw.acpi.battery.state becomes 1 at discharge, 2 at recharge and 0 at full. I get ACPI notifies from CMBAT at 4% and 38% with hw.acpi.battery.state: 1 and at 100% with hw.acpi.battery.state=0. Is that the correct behaviour? Is there an default action when battery becomes critical? I'm running 7.0-Current (Jul 28). Thanks Maik From owner-freebsd-acpi@FreeBSD.ORG Fri Jul 29 13:33:38 2005 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6CAC316A47A for ; Fri, 29 Jul 2005 13:33:38 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 865CB43D48 for ; Fri, 29 Jul 2005 13:33:37 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id j6TDXa1Y006949; Fri, 29 Jul 2005 08:33:36 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <42EA302A.6050502@centtech.com> Date: Fri, 29 Jul 2005 08:33:30 -0500 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050603 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tobias Roth References: <42E68319.40105@centtech.com> <42E68BF7.4040104@root.org> <42E6A3B4.5000102@centtech.com> <42E9220A.4030007@root.org> <42E99654.6010501@centtech.com> <20050729064243.GA10813@droopy.unibe.ch> In-Reply-To: <20050729064243.GA10813@droopy.unibe.ch> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.82/997/Fri Jul 29 03:07:29 2005 on mh1.centtech.com X-Virus-Status: Clean Cc: acpi@freebsd.org Subject: Re: More ACPI patch problems.. 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, 29 Jul 2005 13:33:38 -0000 Tobias Roth wrote: > On Thu, Jul 28, 2005 at 09:37:08PM -0500, Eric Anderson wrote: > >>However, my battery still only gets to 99%. > > > Sorry for jumping in like this and not having read the whole thread > before giving my .02 euros. But this looks quite normal. Older > batteries tend not to be able to store the full design capacity, > hence they will not go back up to 100% loaded. That's how it has > been displayed for as long as I have had access to a laptop with > FreeBSD. Well, possibly, but right before the changes, it always read 100%. I'll try another battery today (a new one) and report back. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-acpi@FreeBSD.ORG Sat Jul 30 00:45:19 2005 Return-Path: X-Original-To: freebsd-acpi@hub.freebsd.org Delivered-To: freebsd-acpi@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F53416A420; Sat, 30 Jul 2005 00:45:19 +0000 (GMT) (envelope-from kris@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D53E43D45; Sat, 30 Jul 2005 00:45:18 +0000 (GMT) (envelope-from kris@FreeBSD.org) Received: from freefall.freebsd.org (kris@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j6U0jI08093197; Sat, 30 Jul 2005 00:45:18 GMT (envelope-from kris@freefall.freebsd.org) Received: (from kris@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j6U0jIud093193; Sat, 30 Jul 2005 00:45:18 GMT (envelope-from kris) Date: Sat, 30 Jul 2005 00:45:18 GMT From: Kris Kennaway Message-Id: <200507300045.j6U0jIud093193@freefall.freebsd.org> To: norihiro@tmlab.osakac.ac.jp, kris@FreeBSD.org, freebsd-acpi@FreeBSD.org Cc: Subject: Re: kern/56659: ACPI trouble on IBM ThinkPad X31 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: Sat, 30 Jul 2005 00:45:19 -0000 Synopsis: ACPI trouble on IBM ThinkPad X31 State-Changed-From-To: feedback->closed State-Changed-By: kris State-Changed-When: Sat Jul 30 00:45:11 GMT 2005 State-Changed-Why: Feedback timeout http://www.freebsd.org/cgi/query-pr.cgi?pr=56659 From owner-freebsd-acpi@FreeBSD.ORG Sat Jul 30 00:47:05 2005 Return-Path: X-Original-To: freebsd-acpi@hub.freebsd.org Delivered-To: freebsd-acpi@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8806B16A41F; Sat, 30 Jul 2005 00:47:05 +0000 (GMT) (envelope-from kris@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D79543D58; Sat, 30 Jul 2005 00:47:05 +0000 (GMT) (envelope-from kris@FreeBSD.org) Received: from freefall.freebsd.org (kris@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j6U0l45w093596; Sat, 30 Jul 2005 00:47:05 GMT (envelope-from kris@freefall.freebsd.org) Received: (from kris@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j6U0l4u6093592; Sat, 30 Jul 2005 00:47:04 GMT (envelope-from kris) Date: Sat, 30 Jul 2005 00:47:04 GMT From: Kris Kennaway Message-Id: <200507300047.j6U0l4u6093592@freefall.freebsd.org> To: mharo@freebsd.org, kris@FreeBSD.org, freebsd-acpi@FreeBSD.org Cc: Subject: Re: i386/60317: FreeBSD 5.2rc1 doesn't boot with ACPI enabled under Microsoft Virtual PC 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: Sat, 30 Jul 2005 00:47:05 -0000 Synopsis: FreeBSD 5.2rc1 doesn't boot with ACPI enabled under Microsoft Virtual PC State-Changed-From-To: feedback->closed State-Changed-By: kris State-Changed-When: Sat Jul 30 00:46:57 GMT 2005 State-Changed-Why: Feedback timeout http://www.freebsd.org/cgi/query-pr.cgi?pr=60317 From owner-freebsd-acpi@FreeBSD.ORG Sat Jul 30 00:51:25 2005 Return-Path: X-Original-To: freebsd-acpi@hub.freebsd.org Delivered-To: freebsd-acpi@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB10616A420; Sat, 30 Jul 2005 00:51:25 +0000 (GMT) (envelope-from kris@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9820F43D45; Sat, 30 Jul 2005 00:51:25 +0000 (GMT) (envelope-from kris@FreeBSD.org) Received: from freefall.freebsd.org (kris@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j6U0pP2H094055; Sat, 30 Jul 2005 00:51:25 GMT (envelope-from kris@freefall.freebsd.org) Received: (from kris@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j6U0pPUv094051; Sat, 30 Jul 2005 00:51:25 GMT (envelope-from kris) Date: Sat, 30 Jul 2005 00:51:25 GMT From: Kris Kennaway Message-Id: <200507300051.j6U0pPUv094051@freefall.freebsd.org> To: damien.chaumette@free.fr, kris@FreeBSD.org, freebsd-acpi@FreeBSD.org Cc: Subject: Re: kern/63666: [acpi] Network card 3c575B do not work after the 5.1 release 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: Sat, 30 Jul 2005 00:51:26 -0000 Synopsis: [acpi] Network card 3c575B do not work after the 5.1 release State-Changed-From-To: feedback->closed State-Changed-By: kris State-Changed-When: Sat Jul 30 00:51:18 GMT 2005 State-Changed-Why: Feedback timeout http://www.freebsd.org/cgi/query-pr.cgi?pr=63666 From owner-freebsd-acpi@FreeBSD.ORG Sat Jul 30 01:25:53 2005 Return-Path: X-Original-To: freebsd-acpi@hub.freebsd.org Delivered-To: freebsd-acpi@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DDF2216A420; Sat, 30 Jul 2005 01:25:53 +0000 (GMT) (envelope-from kris@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99AAB43D4C; Sat, 30 Jul 2005 01:25:53 +0000 (GMT) (envelope-from kris@FreeBSD.org) Received: from freefall.freebsd.org (kris@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j6U1Prv8001635; Sat, 30 Jul 2005 01:25:53 GMT (envelope-from kris@freefall.freebsd.org) Received: (from kris@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j6U1PrYk001631; Sat, 30 Jul 2005 01:25:53 GMT (envelope-from kris) Date: Sat, 30 Jul 2005 01:25:53 GMT From: Kris Kennaway Message-Id: <200507300125.j6U1PrYk001631@freefall.freebsd.org> To: rrl125@psu.edu, kris@FreeBSD.org, freebsd-acpi@FreeBSD.org Cc: Subject: Re: i386/61703: ACPI + Sound + Boot = Reboot 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: Sat, 30 Jul 2005 01:25:54 -0000 Synopsis: ACPI + Sound + Boot = Reboot State-Changed-From-To: feedback->closed State-Changed-By: kris State-Changed-When: Sat Jul 30 01:25:47 GMT 2005 State-Changed-Why: Feedback timeout http://www.freebsd.org/cgi/query-pr.cgi?pr=61703 From owner-freebsd-acpi@FreeBSD.ORG Sat Jul 30 01:27:43 2005 Return-Path: X-Original-To: freebsd-acpi@hub.freebsd.org Delivered-To: freebsd-acpi@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 277E516A420; Sat, 30 Jul 2005 01:27:43 +0000 (GMT) (envelope-from kris@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id DAE0543D46; Sat, 30 Jul 2005 01:27:42 +0000 (GMT) (envelope-from kris@FreeBSD.org) Received: from freefall.freebsd.org (kris@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j6U1RgLL001885; Sat, 30 Jul 2005 01:27:42 GMT (envelope-from kris@freefall.freebsd.org) Received: (from kris@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j6U1Rgfa001880; Sat, 30 Jul 2005 01:27:42 GMT (envelope-from kris) Date: Sat, 30 Jul 2005 01:27:42 GMT From: Kris Kennaway Message-Id: <200507300127.j6U1Rgfa001880@freefall.freebsd.org> To: dsh@vlink.ru, kris@FreeBSD.org, freebsd-acpi@FreeBSD.org Cc: Subject: Re: i386/67189: ACPI S3 reboot computer on Dell Latitude D505 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: Sat, 30 Jul 2005 01:27:43 -0000 Synopsis: ACPI S3 reboot computer on Dell Latitude D505 State-Changed-From-To: feedback->closed State-Changed-By: kris State-Changed-When: Sat Jul 30 01:27:33 GMT 2005 State-Changed-Why: Feedback timeout http://www.freebsd.org/cgi/query-pr.cgi?pr=67189 From owner-freebsd-acpi@FreeBSD.ORG Sat Jul 30 01:28:51 2005 Return-Path: X-Original-To: freebsd-acpi@hub.freebsd.org Delivered-To: freebsd-acpi@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D6C9116A420; Sat, 30 Jul 2005 01:28:51 +0000 (GMT) (envelope-from kris@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 70AA943D46; Sat, 30 Jul 2005 01:28:51 +0000 (GMT) (envelope-from kris@FreeBSD.org) Received: from freefall.freebsd.org (kris@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j6U1SpK3002039; Sat, 30 Jul 2005 01:28:51 GMT (envelope-from kris@freefall.freebsd.org) Received: (from kris@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j6U1Spwv002035; Sat, 30 Jul 2005 01:28:51 GMT (envelope-from kris) Date: Sat, 30 Jul 2005 01:28:51 GMT From: Kris Kennaway Message-Id: <200507300128.j6U1Spwv002035@freefall.freebsd.org> To: fab@gnux.info, kris@FreeBSD.org, freebsd-acpi@FreeBSD.org Cc: Subject: Re: i386/68219: ACPI + snd_maestro3 problem 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: Sat, 30 Jul 2005 01:28:52 -0000 Synopsis: ACPI + snd_maestro3 problem State-Changed-From-To: feedback->closed State-Changed-By: kris State-Changed-When: Sat Jul 30 01:28:38 GMT 2005 State-Changed-Why: Feedback timeout http://www.freebsd.org/cgi/query-pr.cgi?pr=68219