From owner-freebsd-acpi@FreeBSD.ORG Sun Dec 7 07:55:44 2014 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0E8C2FEE for ; Sun, 7 Dec 2014 07:55:44 +0000 (UTC) Received: from o1.l99.sendgrid.net (o1.l99.sendgrid.net [198.37.153.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C3200FBF for ; Sun, 7 Dec 2014 07:55:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.info; h=from:mime-version:to:subject:content-type; s=smtpapi; bh=5eqQXVj2mbFj+qX8rwQk19c25zk=; b=SHOb11i9RGe4Pw9Oa+M4Gtow3Ui7v cTleYhTsqPgk6S2u7Rvaf85r78bz75T2VUUd12G4YM/EH1CaSAgjzygV5zRa4xOh CxB38n+cpDFtkMEQvBpivPVaWuFkhDx/2gPBo++KnOGrry3HpK9LkTsddqfGyQZY AhG1/8C2yww10o= Received: by filter0177p1mdw1.sendgrid.net with SMTP id filter0177p1mdw1.2692.548407EBF 2014-12-07 07:55:24.701091829 +0000 UTC Received: from mail.tarsnap.com (unknown [10.100.60.108]) by ismtpd-004 (SG) with ESMTP id 14a23bef439.8c2.3a2d2c for ; Sun, 07 Dec 2014 07:55:24 +0000 (UTC) Received: (qmail 55738 invoked from network); 7 Dec 2014 07:55:24 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by ec2-107-20-205-189.compute-1.amazonaws.com with ESMTP; 7 Dec 2014 07:55:24 -0000 Received: (qmail 61821 invoked from network); 7 Dec 2014 07:53:37 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by clamshell.daemonology.net with SMTP; 7 Dec 2014 07:53:37 -0000 Message-ID: <54840781.70603@freebsd.org> Date: Sat, 06 Dec 2014 23:53:37 -0800 From: Colin Percival User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: freebsd-acpi@freebsd.org Subject: ENXIOing non-present battery Content-Type: multipart/mixed; boundary="------------010302010806090809050207" X-SG-EID: t2fXfoZHCw6vGsGKHqKxJ9qWwHSlQfPdDS+3+p6rOCudNMbltcytpX5LGgkrH7G7qDL1+9O9E/odd4 /A+6jdXVgucrkTI02EX0XtotnXYy5E0dXu1oTtDrjHLg8EfAm2a4omWtHN/whOH7BZlweKg3+DjN6Q jNFE6IW9rvVbmcM= X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 07:55:44 -0000 This is a multi-part message in MIME format. --------------010302010806090809050207 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hi ACPI people, On my Dell Latitude E7440 laptop, the ACPI reports two batteries: First the battery which exists; and second, a "Not Present" battery with zeroed statistics. FreeBSD, not realizing that this second battery is a complete myth -- the E7440 only has one battery, and there is nowhere to add another -- faithfully reports the data from ACPI to userland. Unfortunately it causes some problems there; in particular, KDE interprets it as meaning that the system should have two batteries, and when it sees that the "second" battery has 0% power remaining it kicks off the "battery is low, turn the laptop off" code. If that code is disabled, it still displays the wrong battery-charge-remaining status icons. For dealing with such broken ACPIs, it seems like not attaching a non-present battery would be a good idea. This shouldn't be the default behaviour, since there are plenty of systems where a non-present battery might be inserted at a later time; but I see nothing wrong with adding an option. The attached patch adds a acpi.cmbat.hide_not_present loader tunable which, as the name suggests, hides non-present batteries; this is done in the probe code by returning ENXIO if the tunable is set to a nonzero value and acpi_BatteryIsPresent returns zero. With this patch and the tunable set my laptop behaves appropriately; and (aside from wasting a few bytes of memory) there should be no effect on systems where the tunable is not set. Any objections to me committing this? -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid --------------010302010806090809050207 Content-Type: text/x-patch; name="hide_not_present.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="hide_not_present.patch" Index: sys/dev/acpica/acpi_cmbat.c =================================================================== --- sys/dev/acpica/acpi_cmbat.c (revision 274932) +++ sys/dev/acpica/acpi_cmbat.c (working copy) @@ -112,13 +112,17 @@ DRIVER_MODULE(acpi_cmbat, acpi, acpi_cmbat_driver, acpi_cmbat_devclass, 0, 0); MODULE_DEPEND(acpi_cmbat, acpi, 1, 1, 1); +static unsigned long hide_not_present = 0; +TUNABLE_ULONG("acpi.cmbat.hide_not_present", &hide_not_present); + static int acpi_cmbat_probe(device_t dev) { static char *cmbat_ids[] = { "PNP0C0A", NULL }; if (acpi_disabled("cmbat") || - ACPI_ID_PROBE(device_get_parent(dev), dev, cmbat_ids) == NULL) + ACPI_ID_PROBE(device_get_parent(dev), dev, cmbat_ids) == NULL || + (hide_not_present && !acpi_BatteryIsPresent(dev))) return (ENXIO); device_set_desc(dev, "ACPI Control Method Battery"); --------------010302010806090809050207-- From owner-freebsd-acpi@FreeBSD.ORG Sun Dec 7 08:28:50 2014 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 93D9345B; Sun, 7 Dec 2014 08:28:50 +0000 (UTC) Received: from smtp1.ms.mff.cuni.cz (smtp1.ms.mff.cuni.cz [IPv6:2001:718:1e03:801::4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2456F268; Sun, 7 Dec 2014 08:28:49 +0000 (UTC) Received: from [172.20.1.29] (fw.ax.cz [77.240.102.126]) by smtp1.ms.mff.cuni.cz (8.14.9/8.14.9) with ESMTP id sB78SeRg099481 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=OK); Sun, 7 Dec 2014 09:28:46 +0100 (CET) (envelope-from dan@obluda.cz) Message-ID: <54840FBA.5050409@obluda.cz> Date: Sun, 07 Dec 2014 09:28:42 +0100 From: Dan Lukes Reply-To: freebsd-acpi@freebsd.org User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:34.0) Gecko/20100101 Firefox/34.0 SeaMonkey/2.31 MIME-Version: 1.0 To: Colin Percival Subject: Re: ENXIOing non-present battery References: <54840781.70603@freebsd.org> In-Reply-To: <54840781.70603@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 08:28:50 -0000 Colin Percival wrote: > it seems like not attaching a non-present battery would be a good idea. This shouldn't be the default behaviour, since > there are plenty of systems where a non-present battery might be inserted at > a later time; but I see nothing wrong with adding an option. > > The attached patch adds a acpi.cmbat.hide_not_present loader tunable which, > as the name suggests, hides non-present batteries; this is done in the probe > code by returning ENXIO > Any objections to me committing this? No, but it may be more useful to create more generalized interface. A remember broken ACPI with issues related to ghost floppy drive when no real floppy drive has been present. Not only battery, but any device should be considered non-attachable upon administrator request. Just my $0.02 Dan From owner-freebsd-acpi@FreeBSD.ORG Sun Dec 7 09:05:54 2014 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 77A36AA5 for ; Sun, 7 Dec 2014 09:05:54 +0000 (UTC) Received: from o1.l99.sendgrid.net (o1.l99.sendgrid.net [198.37.153.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1C52B7E3 for ; Sun, 7 Dec 2014 09:05:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.info; h=from:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; s=smtpapi; bh=LpyLqXmeZ7hCcXw0H7+uGmn+N00=; b=GpZykBU+lDVn2U5G0J 8MbI9ZZmq1/spq78yPBKdWzEiPvLfnmNy+tlviSfxSQtUskSAXBKsNhFu28tGguU 1EFFpeoRWApcQITYt4eivOLCu+vfsyBS0TGfzYOjbdMMpXvQN/YsY+GigoRiStLE 3nnCy4BhIeOTYL1wZC63+8wfY= Received: by filter0166p1mdw1.sendgrid.net with SMTP id filter0166p1mdw1.29081.5484186F8 2014-12-07 09:05:51.656549879 +0000 UTC Received: from mail.tarsnap.com (unknown [10.100.60.97]) by ismtpd-032 (SG) with ESMTP id 14a23ff73ee.7d85.3a7b91 for ; Sun, 07 Dec 2014 09:05:51 +0000 (UTC) Received: (qmail 57736 invoked from network); 7 Dec 2014 09:05:51 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by ec2-107-20-205-189.compute-1.amazonaws.com with ESMTP; 7 Dec 2014 09:05:51 -0000 Received: (qmail 62276 invoked from network); 7 Dec 2014 09:04:04 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by clamshell.daemonology.net with SMTP; 7 Dec 2014 09:04:04 -0000 Message-ID: <54841804.5050700@freebsd.org> Date: Sun, 07 Dec 2014 01:04:04 -0800 From: Colin Percival User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: freebsd-acpi@freebsd.org Subject: Re: ENXIOing non-present battery References: <54840781.70603@freebsd.org> <54840FBA.5050409@obluda.cz> In-Reply-To: <54840FBA.5050409@obluda.cz> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SG-EID: t2fXfoZHCw6vGsGKHqKxJ9qWwHSlQfPdDS+3+p6rOCszDK4X43Mgfq7AVricQeSCfyItGgR82jIZ04 5RpB66vkO8s5o8B4cQeU1ST0G0zCc7Xk/wd9t0AkoE/UqUPB1oILsqYNiPmCDvEJIVpzcx/2HOLX5+ QvoW1xouccFe5zXzB9DE8PMuShFELs3SNYdT X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 09:05:54 -0000 On 12/07/14 00:28, Dan Lukes wrote: > Colin Percival wrote: >> it seems like not attaching a non-present battery would be a good idea. This shouldn't be the default behaviour, since >> there are plenty of systems where a non-present battery might be inserted at >> a later time; but I see nothing wrong with adding an option. >> >> The attached patch adds a acpi.cmbat.hide_not_present loader tunable which, >> as the name suggests, hides non-present batteries; this is done in the probe >> code by returning ENXIO >> >> Any objections to me committing this? > > No, but it may be more useful to create more generalized interface. I agree in theory, but do you have any idea how to do this? > A remember broken ACPI with issues related to ghost floppy drive when no > real floppy drive has been present. > > Not only battery, but any device should be considered non-attachable > upon administrator request. In the case of my laptop, the only way I can see to distinguish between the real battery and the "ghost" battery is that the latter returns zero from acpi_BatteryIsPresent; and that won't work for non-battery devices. There is, of course, the option of using debug.apci.disabled to disable complete subsystems, but I only want to hide the ghost battery, not the real one. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid From owner-freebsd-acpi@FreeBSD.ORG Sun Dec 7 10:11:04 2014 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AE08AB31; Sun, 7 Dec 2014 10:11:04 +0000 (UTC) Received: from smtp1.ms.mff.cuni.cz (smtp1.ms.mff.cuni.cz [IPv6:2001:718:1e03:801::4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2986DD7B; Sun, 7 Dec 2014 10:11:03 +0000 (UTC) Received: from [172.20.1.29] (fw.ax.cz [77.240.102.126]) by smtp1.ms.mff.cuni.cz (8.14.9/8.14.9) with ESMTP id sB7AAsIZ004507 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=OK); Sun, 7 Dec 2014 11:11:01 +0100 (CET) (envelope-from dan@obluda.cz) Message-ID: <548427AF.3060309@obluda.cz> Date: Sun, 07 Dec 2014 11:10:55 +0100 From: Dan Lukes User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:34.0) Gecko/20100101 Firefox/34.0 SeaMonkey/2.31 MIME-Version: 1.0 To: Colin Percival Subject: Re: ENXIOing non-present battery References: <54840781.70603@freebsd.org> <54840FBA.5050409@obluda.cz> <54841804.5050700@freebsd.org> In-Reply-To: <54841804.5050700@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 10:11:04 -0000 Colin Percival wrote: >>> The attached patch adds a acpi.cmbat.hide_not_present loader tunable which, >>> as the name suggests, hides non-present batteries; this is done in the probe >>> code by returning ENXIO >> No, but it may be more useful to create more generalized interface. > I agree in theory, but do you have any idea how to do this? Well, may be I'm not the best expert on the matter, but I assume there is an device enumerator which invoke "probe" function of device drivers. Such enumerator should skip the devices listen in "don't probe" list. I'm aware there is no single enumerator in the kernel. All those enumerators needs to be patched to honor such list. Other solutions: No enumerator needs to be patched. There needs to be device driver module which will claim high priority ownership of all devices on the "disabled device" list. So particular device will be attached to such special driver, not to the standard one. > In the case of my laptop, the only way I can see to distinguish between the > real battery and the "ghost" battery is that the latter returns zero from > acpi_BatteryIsPresent; In case of your particular laptop you can claim second battery to be ghost battery as you know there is no second battery now and will not be even in the future. So no "battery" device driver needs to be attached to such device. It will hide such battery from applications. By the way, as long as your ACPI claim non-existent battery as non existent, it seems not to be broken. If KDE read remaining capacity of battery claimed to be non-present, then it seems to be KDE who have broken logic ... > There is, of course, the option of using debug.apci.disabled to disable > complete subsystems, but I only want to hide the ghost battery, not the > real one. I asked for more generic mechanism, but not as generic as you described. It would eb nice if we can disable enumeration of broken devices only (despite they are enumerated trough ACPI, PNP, PCI, USB or so enumerator), not the just ACPI at all. Dan From owner-freebsd-acpi@FreeBSD.ORG Sun Dec 7 16:03:22 2014 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D66BC27C; Sun, 7 Dec 2014 16:03:22 +0000 (UTC) Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 69BB620E; Sun, 7 Dec 2014 16:03:22 +0000 (UTC) Received: by mail-wg0-f47.google.com with SMTP id n12so4461789wgh.20 for ; Sun, 07 Dec 2014 08:03:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=hEfZHFCfzrDbA803BFRrwNZ9YwJXiSQpeGW2gmZqsl8=; b=C7bXOlikIQ4vnra8XiffuMk4Xkm781FRviyI/ajTUuiCaCTYWC3vSfTk4d/Ma2J555 9l14z802H/6wT7CYXt1LgIcfP0S07CDQaVSN36fkpftOssUdMeRMWXrGHg/QOfrC3j2I zi6Pf9P8Q02D+1bFOfEX0LehufbwLdNDqK+RLQsN6Qy37FIjNiJyzT2mO2x+NdnHeqOY oQJHzsR/1op5UQNIXUHIkW43y1HmI52sZqW2ypxnoMTEnd4DFW17tEjZYnB0fwdT+Bwm 0a8WbXKfG5GtFZ500B/5a7wiRszi/QZWNS1FMrABAuLHNRvGPqiOJQhBY/mhhbq0JLwb ewSw== MIME-Version: 1.0 X-Received: by 10.194.24.103 with SMTP id t7mr39092192wjf.15.1417968200808; Sun, 07 Dec 2014 08:03:20 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.106.195 with HTTP; Sun, 7 Dec 2014 08:03:20 -0800 (PST) In-Reply-To: <54840781.70603@freebsd.org> References: <54840781.70603@freebsd.org> Date: Sun, 7 Dec 2014 08:03:20 -0800 X-Google-Sender-Auth: sw-xfkkwgBsswPbvwxeswYYKp8U Message-ID: Subject: Re: ENXIOing non-present battery From: Adrian Chadd To: Colin Percival Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-acpi@freebsd.org" X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 16:03:23 -0000 Hi, Wait - so it reports a battery with 0% in it, but not that it's not present? How's this work on other systems? KDE on Linux doesn't lose its mind if the second battery is totally flat. -adrian On 6 December 2014 at 23:53, Colin Percival wrote: > Hi ACPI people, > > On my Dell Latitude E7440 laptop, the ACPI reports two batteries: First > the battery which exists; and second, a "Not Present" battery with zeroed > statistics. FreeBSD, not realizing that this second battery is a complete > myth -- the E7440 only has one battery, and there is nowhere to add another > -- faithfully reports the data from ACPI to userland. > > Unfortunately it causes some problems there; in particular, KDE interprets > it as meaning that the system should have two batteries, and when it sees > that the "second" battery has 0% power remaining it kicks off the "battery > is low, turn the laptop off" code. If that code is disabled, it still > displays the wrong battery-charge-remaining status icons. > > For dealing with such broken ACPIs, it seems like not attaching a non-present > battery would be a good idea. This shouldn't be the default behaviour, since > there are plenty of systems where a non-present battery might be inserted at > a later time; but I see nothing wrong with adding an option. > > The attached patch adds a acpi.cmbat.hide_not_present loader tunable which, > as the name suggests, hides non-present batteries; this is done in the probe > code by returning ENXIO if the tunable is set to a nonzero value and > acpi_BatteryIsPresent returns zero. With this patch and the tunable set my > laptop behaves appropriately; and (aside from wasting a few bytes of memory) > there should be no effect on systems where the tunable is not set. > > Any objections to me committing this? > > -- > Colin Percival > Security Officer Emeritus, FreeBSD | The power to serve > Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid > > _______________________________________________ > freebsd-acpi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-acpi > To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org" From owner-freebsd-acpi@FreeBSD.ORG Sun Dec 7 20:50:53 2014 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E2323C5F for ; Sun, 7 Dec 2014 20:50:53 +0000 (UTC) Received: from o1.l99.sendgrid.net (o1.l99.sendgrid.net [198.37.153.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 94700C8 for ; Sun, 7 Dec 2014 20:50:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.info; h=from:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; s=smtpapi; bh=wlqf8bOKnt5k9ThR4F7TRtMFqfY=; b=bVjQKDZCmSYuhDXm+w SPGTrvAkFkx27OamSPJjfJu6ZevxcNpemGVaEsOqnlkD3g0aaOKJyF5QUxCW4Mjf A5Z34mDS1MOzNSvEIyo4GAsgWIZxB4UHMqqN8+UItCNzoDvYwvUW8nLZ+L6k0i3a R2nheW9STWWDctv0i3QqyjCrc= Received: by filter0037p1mdw1.sendgrid.net with SMTP id filter0037p1mdw1.6038.5484BDAA4 2014-12-07 20:50:50.654606984 +0000 UTC Received: from mail.tarsnap.com (unknown [10.100.60.97]) by ismtpd-027 (SG) with ESMTP id 14a2684e25f.1c13.4546e7 for ; Sun, 07 Dec 2014 20:50:50 +0000 (UTC) Received: (qmail 77981 invoked from network); 7 Dec 2014 20:50:50 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by ec2-107-20-205-189.compute-1.amazonaws.com with ESMTP; 7 Dec 2014 20:50:50 -0000 Received: (qmail 64843 invoked from network); 7 Dec 2014 20:49:01 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by clamshell.daemonology.net with SMTP; 7 Dec 2014 20:49:01 -0000 Message-ID: <5484BD3D.3030605@freebsd.org> Date: Sun, 07 Dec 2014 12:49:01 -0800 From: Colin Percival User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: ENXIOing non-present battery References: <54840781.70603@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SG-EID: t2fXfoZHCw6vGsGKHqKxJ9qWwHSlQfPdDS+3+p6rOCvrgwj/EBpO7tdpHF+Ydsk02mwLf+pQ6vDFmY GOXvtHq4iFrNXdUh7yuBAOPCrlSbbixgZo3H08njiyKP9A1tzVKpPu1h/N4wfxmKL/ejmYV7hZpKEG 28ubyPMfGCVDAAAb3x7oFJoWfe0lbvOvxN8h Cc: "freebsd-acpi@freebsd.org" X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 20:50:54 -0000 On 12/07/14 08:03, Adrian Chadd wrote: > Wait - so it reports a battery with 0% in it, but not that it's not present? It reports all zeroes: Not Present, 0% power, 0V, 0mA design capacity, etc. > How's this work on other systems? KDE on Linux doesn't lose its mind > if the second battery is totally flat. Good question. I'll download an Ubuntu image and find out. Given that KDE gets this information via hald, it's possible that hald's linux code has a workaround for this though -- the battery-status-reading code is entirely separate between FreeBSD and Linux. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid From owner-freebsd-acpi@FreeBSD.ORG Sun Dec 7 21:00:17 2014 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 032FEFC3 for ; Sun, 7 Dec 2014 21:00:17 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CE0C91DE for ; Sun, 7 Dec 2014 21:00:16 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sB7L0GAi031357 for ; Sun, 7 Dec 2014 21:00:16 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201412072100.sB7L0GAi031357@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: freebsd-acpi@FreeBSD.org Subject: Problem reports for freebsd-acpi@FreeBSD.org that need special attention X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 Date: Sun, 07 Dec 2014 21:00:16 +0000 Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 21:00:17 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- Open | 194884 | [acpi] Asus UX31E USB hangs during suspend, due t 1 problems total for which you should take action. From owner-freebsd-acpi@FreeBSD.ORG Sun Dec 7 21:12:35 2014 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DA6D13FF; Sun, 7 Dec 2014 21:12:35 +0000 (UTC) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 5EB613E7; Sun, 7 Dec 2014 21:12:34 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id XAA22444; Sun, 07 Dec 2014 23:14:20 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1Xxj7x-0005aS-9q; Sun, 07 Dec 2014 23:12:25 +0200 Message-ID: <5484C294.6030104@FreeBSD.org> Date: Sun, 07 Dec 2014 23:11:48 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Colin Percival , Adrian Chadd Subject: Re: ENXIOing non-present battery References: <54840781.70603@freebsd.org> <5484BD3D.3030605@freebsd.org> In-Reply-To: <5484BD3D.3030605@freebsd.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: "freebsd-acpi@freebsd.org" X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 21:12:36 -0000 On 07/12/2014 22:49, Colin Percival wrote: > On 12/07/14 08:03, Adrian Chadd wrote: >> Wait - so it reports a battery with 0% in it, but not that it's not present? > > It reports all zeroes: Not Present, 0% power, 0V, 0mA design capacity, etc. > >> How's this work on other systems? KDE on Linux doesn't lose its mind >> if the second battery is totally flat. > > Good question. I'll download an Ubuntu image and find out. Given that KDE > gets this information via hald, it's possible that hald's linux code has a > workaround for this though -- the battery-status-reading code is entirely > separate between FreeBSD and Linux. Or that HAL is no longer used at all in most Linux-based OSes... -- Andriy Gapon From owner-freebsd-acpi@FreeBSD.ORG Mon Dec 8 23:10:14 2014 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 681C6911 for ; Mon, 8 Dec 2014 23:10:14 +0000 (UTC) Received: from o3.shared.sendgrid.net (o3.shared.sendgrid.net [208.117.48.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2AE92E43 for ; Mon, 8 Dec 2014 23:10:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.info; h=from:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; s=smtpapi; bh=9DF6FYbdgvatd9iRjwyYSIfHUso=; b=cwrgVcRkl6jCrFQYV+ UYhvl5D8jYWwAihDzMCB39itEp1hSpQQoT7eq3SXnTI4ca+Iilsnte/IaAXBzRWj cElVOHA9Ag3QYv06L+yzin/vKY7Hp2simgxSzmqi7t7KudKV3YhZ5a8zDSblsafW VPzl6ZAmzDL0X62nfuosrHvVw= Received: by filter0165p1mdw1.sendgrid.net with SMTP id filter0165p1mdw1.340.54862FCDB 2014-12-08 23:10:07.724525426 +0000 UTC Received: from mail.tarsnap.com (unknown [10.100.60.97]) by ismtpd-004 (SG) with ESMTP id 14a2c2ac32e.8b7.27ebe9 for ; Mon, 08 Dec 2014 23:10:07 +0000 (UTC) Received: (qmail 31310 invoked from network); 8 Dec 2014 23:10:07 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by ec2-107-20-205-189.compute-1.amazonaws.com with ESMTP; 8 Dec 2014 23:10:07 -0000 Received: (qmail 71849 invoked from network); 8 Dec 2014 23:08:14 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by clamshell.daemonology.net with SMTP; 8 Dec 2014 23:08:14 -0000 Message-ID: <54862F5E.4040909@freebsd.org> Date: Mon, 08 Dec 2014 15:08:14 -0800 From: Colin Percival User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: ENXIOing non-present battery References: <54840781.70603@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SG-EID: t2fXfoZHCw6vGsGKHqKxJ9qWwHSlQfPdDS+3+p6rOCsGn7ShaDYm4FqK7s9pehVdyHrHNGP9dO5i4i Em1qp2QUe6k9+/EUC/qscQzgHFymDENbPLL7a1YK3PLASw75TaGKPRtr+PHVqFS9uzvtMiFS+Eiy5S JINDRCMUTZNHyCI= Cc: "freebsd-acpi@freebsd.org" X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2014 23:10:14 -0000 On 12/07/14 08:03, Adrian Chadd wrote: > How's this work on other systems? KDE on Linux doesn't lose its mind > if the second battery is totally flat. I just booted Ubuntu 14.04, and both "batteries" appear in /proc/acpi/battery; but BAT1 just shows "present: no" without any statistics, and the GUI shows the correct state for the single present battery. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid From owner-freebsd-acpi@FreeBSD.ORG Mon Dec 8 23:27:12 2014 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D6A0CD0E; Mon, 8 Dec 2014 23:27:12 +0000 (UTC) Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 69915FFA; Mon, 8 Dec 2014 23:27:12 +0000 (UTC) Received: by mail-wi0-f174.google.com with SMTP id h11so6222095wiw.1 for ; Mon, 08 Dec 2014 15:27:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=3mq0C6tRaWPJhH2eSEbmttAQMIeHEzTnjNdYG87dqzw=; b=xBwjVLuJm87VBGO5u09bq/YWMGUZIIy9xMBvIaFv4+25tup1SffIZ3HFF6T/JdInxE Ze5YpboGCAWzeOPFqGWIHrDxTezOMgzZLOm9NfAieqylG7CtzfVPerMcXihOu6H8d9Wn 0x2LEKcQALBYMHvhQDmbl44MRD0245vaU5ilw+AJTgElY9P34iW0mISIrTNLPFe9t1j2 kMbMrMYwUbxMuRGfLCYtspLILulf7r6qKSaPxcd41oeCByNl6aMsaCFhcFXL+jo8UM7l tVQlt26Hxqq/NQH6WEFLtU9ln28jTrZ3pr628qWC6iyvXmu5Yeq9VexwBlmRq00We87e +ypA== MIME-Version: 1.0 X-Received: by 10.180.92.169 with SMTP id cn9mr34388wib.26.1418081230801; Mon, 08 Dec 2014 15:27:10 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.106.195 with HTTP; Mon, 8 Dec 2014 15:27:10 -0800 (PST) In-Reply-To: <54862F5E.4040909@freebsd.org> References: <54840781.70603@freebsd.org> <54862F5E.4040909@freebsd.org> Date: Mon, 8 Dec 2014 15:27:10 -0800 X-Google-Sender-Auth: I0pwtfqUNLrXa4ubjgLcwh1t5E0 Message-ID: Subject: Re: ENXIOing non-present battery From: Adrian Chadd To: Colin Percival Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-acpi@freebsd.org" X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2014 23:27:12 -0000 What's the output of acpiconf -i0 and acpiconf -i1? I wonder if changing 'state' to something else would keep everything happy. -adrian On 8 December 2014 at 15:08, Colin Percival wrote: > On 12/07/14 08:03, Adrian Chadd wrote: >> How's this work on other systems? KDE on Linux doesn't lose its mind >> if the second battery is totally flat. > > I just booted Ubuntu 14.04, and both "batteries" appear in /proc/acpi/battery; > but BAT1 just shows "present: no" without any statistics, and the GUI shows > the correct state for the single present battery. > > -- > Colin Percival > Security Officer Emeritus, FreeBSD | The power to serve > Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid From owner-freebsd-acpi@FreeBSD.ORG Tue Dec 9 05:33:57 2014 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AD646428; Tue, 9 Dec 2014 05:33:57 +0000 (UTC) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2B1ABCBA; Tue, 9 Dec 2014 05:33:56 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id sB95Xkhb049055; Tue, 9 Dec 2014 16:33:46 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Tue, 9 Dec 2014 16:33:45 +1100 (EST) From: Ian Smith To: Adrian Chadd Subject: Re: ENXIOing non-present battery In-Reply-To: Message-ID: <20141209162141.R48067@sola.nimnet.asn.au> References: <54840781.70603@freebsd.org> <54862F5E.4040909@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: "freebsd-acpi@freebsd.org" , Colin Percival X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2014 05:33:57 -0000 On Mon, 8 Dec 2014 15:27:10 -0800, Adrian Chadd wrote: > What's the output of acpiconf -i0 and acpiconf -i1? > > I wonder if changing 'state' to something else would keep everything happy. > On 8 December 2014 at 15:08, Colin Percival wrote: > > On 12/07/14 08:03, Adrian Chadd wrote: > >> How's this work on other systems? KDE on Linux doesn't lose its mind > >> if the second battery is totally flat. > > > > I just booted Ubuntu 14.04, and both "batteries" appear in /proc/acpi/battery; > > but BAT1 just shows "present: no" without any statistics, and the GUI shows > > the correct state for the single present battery. And what does 'grep battery /var/run/dmesg.boot' have to say? Normally with 2 batteries catered for and only one fitted you'd expect to see eg: ./nicks_acpi/dmesg-bootwithacpi-2-part.txt:battery0: on acpi0 ./nicks_acpi/dmesg-bootwithacpi-2-part.txt:battery1: on acpi0 ./nicks_acpi/dmesg-bootwithacpi-2-part.txt:battery0: battery initialization start ./nicks_acpi/dmesg-bootwithacpi-2-part.txt:battery1: battery initialization start ./nicks_acpi/dmesg-bootwithacpi-2-part.txt:battery0: battery initialization done, tried 1 times ./nicks_acpi/dmesg-bootwithacpi-2-part.txt:battery1: battery initialization failed, giving up cheers, Ian From owner-freebsd-acpi@FreeBSD.ORG Tue Dec 9 09:42:44 2014 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9477E698 for ; Tue, 9 Dec 2014 09:42:44 +0000 (UTC) Received: from smtp1.ms.mff.cuni.cz (smtp1.ms.mff.cuni.cz [IPv6:2001:718:1e03:801::4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2B29EA2A for ; Tue, 9 Dec 2014 09:42:43 +0000 (UTC) Received: from kgw.obluda.cz ([194.108.204.138]) by smtp1.ms.mff.cuni.cz (8.14.9/8.14.9) with ESMTP id sB99gdPx070433 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=OK) for ; Tue, 9 Dec 2014 10:42:40 +0100 (CET) (envelope-from dan@obluda.cz) Message-ID: <5486C40F.20802@obluda.cz> Date: Tue, 09 Dec 2014 10:42:39 +0100 From: Dan Lukes User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:29.0) Gecko/20100101 Firefox/29.0 SeaMonkey/2.26.1 MIME-Version: 1.0 To: freebsd-acpi@freebsd.org Subject: Re: ENXIOing non-present battery References: <54840781.70603@freebsd.org> <54862F5E.4040909@freebsd.org> <20141209162141.R48067@sola.nimnet.asn.au> In-Reply-To: <20141209162141.R48067@sola.nimnet.asn.au> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2014 09:42:44 -0000 On 12/09/14 06:33, Ian Smith: > Normally with 2 batteries catered for and only one fitted you'd expect to see > battery1: on acpi0 > battery1: battery initialization start > battery1: battery initialization failed, giving up Just for the completeness ... ... it is expected behavior for non-present battery. Relevant part of code (sys/dev/acpica/acpi_cmbat.c): > ACPI_VPRINT(dev, acpi_device_get_parent_softc(dev), > "battery initialization start\n"); ... > for (retry = 0; retry < ACPI_CMBAT_RETRY_MAX; retry++, AcpiOsSleep(10000)) { ... > if (!acpi_BatteryIsPresent(dev)) > continue; ... > } > > if (retry == ACPI_CMBAT_RETRY_MAX) { > ACPI_VPRINT(dev, acpi_device_get_parent_softc(dev), > "battery initialization failed, giving up\n"); Dan From owner-freebsd-acpi@FreeBSD.ORG Tue Dec 9 10:48:59 2014 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D89DAAB9 for ; Tue, 9 Dec 2014 10:48:59 +0000 (UTC) Received: from o1.l99.sendgrid.net (o1.l99.sendgrid.net [198.37.153.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8BCA4A8 for ; Tue, 9 Dec 2014 10:48:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.info; h=from:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; s=smtpapi; bh=tpeR3iiNFcqPAueoEa3yaQi92yA=; b=yLXXuOhTEASDb8HVDu HKoZPuaPmemqscbmGJmVbcdnWKgUC1JFACCEl7alsWiM5Uz2/QXocn8W8Ha2B7RJ cqrm1ZV4uV4wPFrHdgC4Q/rnjulLyEshr//3uxBDkbguETVmkp0Kvo5wAsIe5Fwo KarhRZVAsWvvMYOC5EAFrEEnY= Received: by filter0028p1mdw1.sendgrid.net with SMTP id filter0028p1mdw1.28725.5486D39813 2014-12-09 10:48:57.117960845 +0000 UTC Received: from mail.tarsnap.com (unknown [10.100.60.108]) by ismtpd-040 (SG) with ESMTP id 14a2eaa8dd9.5406.306025 for ; Tue, 09 Dec 2014 10:48:57 +0000 (UTC) Received: (qmail 73149 invoked from network); 9 Dec 2014 10:48:56 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by ec2-107-20-205-189.compute-1.amazonaws.com with ESMTP; 9 Dec 2014 10:48:56 -0000 Received: (qmail 73746 invoked from network); 9 Dec 2014 10:47:02 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by clamshell.daemonology.net with SMTP; 9 Dec 2014 10:47:02 -0000 Message-ID: <5486D326.5080708@freebsd.org> Date: Tue, 09 Dec 2014 02:47:02 -0800 From: Colin Percival User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: ENXIOing non-present battery References: <54840781.70603@freebsd.org> <54862F5E.4040909@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SG-EID: t2fXfoZHCw6vGsGKHqKxJ9qWwHSlQfPdDS+3+p6rOCvoGUXwugTfFWnxRF5tDclv5vLzITmW1XjH6K ULYR8Wvwa8h+XUMwLNmP9H63l04MKk3rIhoZQE0tsjn86qtv/WqhrHcLtBtvKU7b9OFHehbIBJPiCc I/FuF1P9qL5jnUm7C2P2hF+U8qULuF8nGwe3 X-SendGrid-Contentd-ID: {"test_id":"1418122137"} Cc: "freebsd-acpi@freebsd.org" X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2014 10:48:59 -0000 On 12/08/14 15:27, Adrian Chadd wrote: > What's the output of acpiconf -i0 and acpiconf -i1? acpiconf -i0 is exactly what you'd expect. acpiconf -i1 shows blank for the model/serial/type/OEM info strings, and 0 mAh/mV for the rest except State which is "not present". > I wonder if changing 'state' to something else would keep everything happy. I can't see how it would. The hald code uses hw.acpi.battery.units to see how many batteries there are, then reads the _BIF data via ioctl; the "state" isn't even in _BIF. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid From owner-freebsd-acpi@FreeBSD.ORG Wed Dec 10 01:06:51 2014 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id ABADA1AA for ; Wed, 10 Dec 2014 01:06:51 +0000 (UTC) Received: from smtp1.ms.mff.cuni.cz (smtp1.ms.mff.cuni.cz [IPv6:2001:718:1e03:801::4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3FB1694 for ; Wed, 10 Dec 2014 01:06:50 +0000 (UTC) Received: from [10.135.106.47] (ip-37-188-136-3.eurotel.cz [37.188.136.3]) by smtp1.ms.mff.cuni.cz (8.14.9/8.14.9) with ESMTP id sBA16YQF074697 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=OK) for ; Wed, 10 Dec 2014 02:06:47 +0100 (CET) (envelope-from dan@obluda.cz) Message-ID: <54879C94.1090800@obluda.cz> Date: Wed, 10 Dec 2014 02:06:28 +0100 From: Dan Lukes User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:33.0) Gecko/20100101 Firefox/33.0 SeaMonkey/2.30 MIME-Version: 1.0 CC: "freebsd-acpi@freebsd.org" Subject: Re: ENXIOing non-present battery References: <54840781.70603@freebsd.org> <54862F5E.4040909@freebsd.org> <5486D326.5080708@freebsd.org> In-Reply-To: <5486D326.5080708@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2014 01:06:51 -0000 Colin Percival wrote: > The hald code uses hw.acpi.battery.units to see how many batteries there are, then reads the _BIF data via ioctl; the "state" > isn't even in _BIF. ACPI specification 3.0a par. 10.2.1 : ------------- ... Unlike most other devices, when a battery is inserted or removed from the system, the device itself (the battery bay) is still considered to be present in the system. For most systems, the _STA for this device will always return a value with bits 0-3 set and will toggle bit 4 to indicate the actual presence of a battery (see section 6.3.7, "_STA [Status]"). When this insertion or removal occurs, the AML code handler for this event should issue a Notify(battery_device, 0x81) to indicate that the static battery information has changed. For systems that have battery slots in a docking station or batteries that cannot be surprise-removed, it may be beneficial or necessary to indicate that the entire device has been removed. In this case, the standard methods and notifications described in section 6.3, "Device Insertion, Removal, and Status Objects," should be used. ------------- It seems that hald is broken as it doesn't handle properly both cases. It should query bit 4 of _STA. Dan From owner-freebsd-acpi@FreeBSD.ORG Wed Dec 10 05:34:10 2014 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 047F26E5 for ; Wed, 10 Dec 2014 05:34:10 +0000 (UTC) Received: from o1.l99.sendgrid.net (o1.l99.sendgrid.net [198.37.153.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A1D8B1F4 for ; Wed, 10 Dec 2014 05:34:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.info; h=from:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; s=smtpapi; bh=q+ChTzjqGG0rTGZCv59hkvjIyaw=; b=NE+9pVEh94mUi8spzf vi5CNGSJRnhN7BngHY6r/gzfw4LZMhkMEdXPFlVa1LM0/azBVkammukbBADFYSlM qoYzEMbxofL7FUDTP6c6laFAmSoYrAb6MxfEMkeXwEPzaizJ4bHiTrbQ2uhaM+mL 9SgF51OHMhFTE3j8qMu9DMqws= Received: by filter0236p1mdw1.sendgrid.net with SMTP id filter0236p1mdw1.18799.5487DB45D 2014-12-10 05:34:00.480658795 +0000 UTC Received: from mail.tarsnap.com (unknown [10.100.60.108]) by ismtpd-003 (SG) with ESMTP id 14a32b092dd.3b5c.100f for ; Wed, 10 Dec 2014 05:34:00 +0000 (UTC) Received: (qmail 14118 invoked from network); 10 Dec 2014 05:33:59 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by ec2-107-20-205-189.compute-1.amazonaws.com with ESMTP; 10 Dec 2014 05:33:59 -0000 Received: (qmail 77794 invoked from network); 10 Dec 2014 05:32:02 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by clamshell.daemonology.net with SMTP; 10 Dec 2014 05:32:02 -0000 Message-ID: <5487DAD2.80001@freebsd.org> Date: Tue, 09 Dec 2014 21:32:02 -0800 From: Colin Percival User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Ian Smith , Adrian Chadd Subject: Re: ENXIOing non-present battery References: <54840781.70603@freebsd.org> <54862F5E.4040909@freebsd.org> <20141209162141.R48067@sola.nimnet.asn.au> In-Reply-To: <20141209162141.R48067@sola.nimnet.asn.au> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SG-EID: t2fXfoZHCw6vGsGKHqKxJ9qWwHSlQfPdDS+3+p6rOCt6wxEzQ7fyMuwGQAHKDhNijSCgj2WpnM6p1P Ry069T/Nkq3DFA2eTQvAw5/abmJPBHnVb+mZzIznFaOQUBvvxwxcJNtga1vtyhrmIuNJLfMMLUGlrj /vbbCnVUd+ntwJU= Cc: "freebsd-acpi@freebsd.org" X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2014 05:34:10 -0000 On 12/08/14 21:33, Ian Smith wrote: > And what does 'grep battery /var/run/dmesg.boot' have to say? Normally > with 2 batteries catered for and only one fitted you'd expect to see eg: > > ./nicks_acpi/dmesg-bootwithacpi-2-part.txt:battery0: on acpi0 > ./nicks_acpi/dmesg-bootwithacpi-2-part.txt:battery1: on acpi0 > ./nicks_acpi/dmesg-bootwithacpi-2-part.txt:battery0: battery initialization start > ./nicks_acpi/dmesg-bootwithacpi-2-part.txt:battery1: battery initialization start > ./nicks_acpi/dmesg-bootwithacpi-2-part.txt:battery0: battery initialization done, tried 1 times > ./nicks_acpi/dmesg-bootwithacpi-2-part.txt:battery1: battery initialization failed, giving up Yes, that's exactly what I see. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid From owner-freebsd-acpi@FreeBSD.ORG Wed Dec 10 11:16:03 2014 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 63AE87F3 for ; Wed, 10 Dec 2014 11:16:03 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4B547F49 for ; Wed, 10 Dec 2014 11:16:03 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sBABG3Dj092028 for ; Wed, 10 Dec 2014 11:16:03 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-acpi@FreeBSD.org Subject: [Bug 162859] [acpi] ACPI battery/acline monitoring partialy working (switching) Date: Wed, 10 Dec 2014 11:16:03 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.0-PRERELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: juris.kaminskis@gmail.com X-Bugzilla-Status: In Progress X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-acpi@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2014 11:16:03 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=162859 juris changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |juris.kaminskis@gmail.com --- Comment #12 from juris --- Battery status only updates after reboot on HP 8440p and for all HP laptops as it seems from previous comments as of Freebsd 9.0 - Release Current workaround: Install Freebsd 8.4 - Release and do not upgrade -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-acpi@FreeBSD.ORG Wed Dec 10 19:21:05 2014 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B8611470 for ; Wed, 10 Dec 2014 19:21:05 +0000 (UTC) Received: from spfilter-1.secure-dns.net (spfilter1-out1.secure-dns.net [173.248.162.250]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8BC8D6F1 for ; Wed, 10 Dec 2014 19:21:05 +0000 (UTC) Received: from plesk07.ns01.net ([116.12.48.135]) by spfilter-1.secure-dns.net with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.84) (envelope-from ) id 1XymU2-00058z-4r for freebsd-acpi@freebsd.org; Wed, 10 Dec 2014 11:59:36 -0700 Received: from plesk07.ns01.net (unknown [127.0.0.1]) by plesk07.ns01.net (Postfix) with ESMTP id 308DF111E025C for ; Wed, 10 Dec 2014 18:59:15 +0000 (UTC) Received: from Reference.com (unknown [109.102.30.122]) by plesk07.ns01.net (Postfix) with ESMTP for ; Wed, 10 Dec 2014 18:59:14 +0000 (UTC) From: Australian Taxation Office To: freebsd-acpi@freebsd.org Subject: NOTICE OF TAX RETURN ! Customer ID: 73545548 Date: 10 Dec 2014 20:59:28 +0200 Message-ID: <20141210205928.AA80D8D81FBC56C9@Reference.com> X-Filter-ID: s0sct1PQhAABKnZB5plbIZav8+wsfptTzwBxZUCxYhBJ1ioVChx931tCJ+MGCcUuV/TiE7mB7wmr 7RVDRQXlbzkc8e1nhn0Vt8MmVjSSfKVW6bxmQnw9sAbd88J4mkBGQv5RrK13LEtMWNCdfH+qO8Qe uglr13Hyg31401PvruunByR81NHP+1BXOc5WkhqxjSlpKico8Q+2YFVouZa3SmbjO41FyBEqIaDu dcVplPFJhpQreFDms6V2sch67mj2c/prv42YqTwOO8PpyAOGYheU+JLt2/b9AJZdFnu6meQmgnGG vKDVj+f6zCZ32XvSR9Da3pQBI7+XCytIldDzLl6GUv/Bg8EFW5Cl+YXPdGk3fBtfpE0ywsEa6OYG gY1hERWeKKG4PAQYNyavp7c49OMuCFM+q2sVY8hx40Ge6HVmD4HSrT2a/hKnFbSj3v4EGEgNVzBS AOghzk1WT/Bw5pFGL/hE7hjEvGldTOHCxbIlMJ6K8oIFHKsrKTHG3ikZ1HeR0rD/5y/VqjTJC8n8 KIZ2KmZ4g2TrHzGZZ0qWJ9BVROdiAfLLFfnNVKtcKGDDz6x9ku3CS6fm6BL7cUswm5FGL/hE7hjE vGldTOHCxbJs9GL9IIt6Y3t+vIFcB/81BAsV6F5GCjruWsuKW5Y5hm4R9ow3wz24Jguv1DeOUfeE ko7QdeMg48aVY4pa17icU+523z3kgYGHd/0So0D8ofY4ocfmWv3Fe9Iziczdq+A= X-Report-Abuse-To: spam@spfilter-1.secure-dns.net X-Filter-Fingerprint: IFrWXGses7OKB5S5G8/dJcFIkh7yuznlTeFPLSNUgKZA3cTUQ1R++keuE7RDJ8Kg3RbMLUalw1oC mj99/u+PoqoVy8a3lsStJtAvpObFX0Wok1JBYnOLzfRIhlEHQynLUpndEJ0YoaLytXXo8BMTaX2p Mk7LBarWD9Fj4R3eIu6C5spubTEXAEkuBKN3yOZvUxf7JO+oAUByCkP7cAJnEooJtGZFyF6tI/I5 CWVQH2sjWUvnt4XQmbZjx+Gtm4/p X-Originating-IP: 116.12.48.135 X-SpamExperts-Domain: spamexpertfilter.secure-dns.net X-SpamExperts-Username: 116.12.48.135 Authentication-Results: secure-dns.net; auth=pass smtp.auth=116.12.48.135 X-SpamExperts-Outgoing-Class: unsure X-SpamExperts-Outgoing-Evidence: Combined (0.62) X-Recommended-Action: accept MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2014 19:21:05 -0000 Dear freebsd-acpi@freebsd.org Tax Refund of: AUD 795 Please complete this form in order to receive your tax refund. To access the form for your tax refund, Please click on the link below: [1]http://www.ato_my.gov.au Please submit the tax refund form before: 13 Dec 2014 References 1. http://babykidswholesaler.com/catalog/ato/log/ From owner-freebsd-acpi@FreeBSD.ORG Thu Dec 11 03:53:26 2014 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DA92548F for ; Thu, 11 Dec 2014 03:53:26 +0000 (UTC) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5338F3CF for ; Thu, 11 Dec 2014 03:53:25 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id sBB3rCvQ043919; Thu, 11 Dec 2014 14:53:13 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Thu, 11 Dec 2014 14:53:12 +1100 (EST) From: Ian Smith To: Dan Lukes Subject: Re: ENXIOing non-present battery In-Reply-To: <5486C40F.20802@obluda.cz> Message-ID: <20141211142932.X48067@sola.nimnet.asn.au> References: <54840781.70603@freebsd.org> <54862F5E.4040909@freebsd.org> <20141209162141.R48067@sola.nimnet.asn.au> <5486C40F.20802@obluda.cz> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-acpi@freebsd.org X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Dec 2014 03:53:26 -0000 On Tue, 9 Dec 2014 10:42:39 +0100, Dan Lukes wrote: > On 12/09/14 06:33, Ian Smith: > > Normally with 2 batteries catered for and only one fitted you'd expect to > > see > > > battery1: on acpi0 > > battery1: battery initialization start > > battery1: battery initialization failed, giving up > > Just for the completeness ... > > ... it is expected behavior for non-present battery. Relevant part of code > (sys/dev/acpica/acpi_cmbat.c): > > > ACPI_VPRINT(dev, acpi_device_get_parent_softc(dev), > > "battery initialization start\n"); > ... > > for (retry = 0; retry < ACPI_CMBAT_RETRY_MAX; retry++, > > AcpiOsSleep(10000)) { > ... > > if (!acpi_BatteryIsPresent(dev)) > > continue; > ... > > } > > > > if (retry == ACPI_CMBAT_RETRY_MAX) { > > ACPI_VPRINT(dev, acpi_device_get_parent_softc(dev), > > "battery initialization failed, giving up\n"); Yes, I just wanted to eliminate the battery being erroneously detected as being present on initialisation. So this problem seems likely to be down to (at least) one of: a) a bug in our ACPI code; b) a bug in this machine's AML (which we haven't seen); c) a bug in hald. .. which is hardly helpful, I know. I had a quick browse of the scripts and FreeBSD backend bits of sysutils/hal, and was frankly too horrified to consider trying to browse its full sources. cheers, Ian From owner-freebsd-acpi@FreeBSD.ORG Thu Dec 11 20:17:04 2014 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 52B1D14A for ; Thu, 11 Dec 2014 20:17:04 +0000 (UTC) Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D479ABE3 for ; Thu, 11 Dec 2014 20:17:03 +0000 (UTC) Received: by mail-wi0-f172.google.com with SMTP id n3so443932wiv.17 for ; Thu, 11 Dec 2014 12:17:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=AE90m43HbLYcyZFb4lkN07J2kNxPQt2NjdnvTZgP1uY=; b=V7peLmKiTruWMNm3U0paxCM9vqMoeNO3pXZT8T6+tMCAYWFeMsTZz/TEsV2Yt6XHzl VaMQ9KyuH1LdyqjqWbzdD/xXbouFAqwGhphMS/14/sEkXZPr4+SuaACTjd9GdQDcyNwR ntXziIRRtEeNOBin2oIveUzkptcVL68lxVQoeSXilf3iW4WzVrGCSTCgI6l55sZLxKvT BIuTD3kELcF+On+vA2BiPQ2/sQy18aZ0Le7Nf0rf9ChUoxIYaDPzmg8g5P/eYUHXMsaX vl08Xd8PRYg2ZrVuGBC69g+dZpxvdJRKXUbNuikQNs18vyP8XGI6hYu2uheXWpOdB4sT Gozw== MIME-Version: 1.0 X-Received: by 10.180.83.98 with SMTP id p2mr1283856wiy.20.1418329021777; Thu, 11 Dec 2014 12:17:01 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.106.195 with HTTP; Thu, 11 Dec 2014 12:17:01 -0800 (PST) In-Reply-To: <20141211142932.X48067@sola.nimnet.asn.au> References: <54840781.70603@freebsd.org> <54862F5E.4040909@freebsd.org> <20141209162141.R48067@sola.nimnet.asn.au> <5486C40F.20802@obluda.cz> <20141211142932.X48067@sola.nimnet.asn.au> Date: Thu, 11 Dec 2014 12:17:01 -0800 X-Google-Sender-Auth: FwlqW9NIXlCmM_hvHOiZr5eDtTA Message-ID: Subject: Re: ENXIOing non-present battery From: Adrian Chadd To: Ian Smith Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-acpi@freebsd.org" X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Dec 2014 20:17:04 -0000 Just remember, batteries can come and go, so we can't just ignore a battery because the status says "not present." So I think it's a bug in hald. -adrian From owner-freebsd-acpi@FreeBSD.ORG Thu Dec 11 20:56:00 2014 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7535EC61; Thu, 11 Dec 2014 20:56:00 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5077AE4; Thu, 11 Dec 2014 20:56:00 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id B250BB93E; Thu, 11 Dec 2014 15:55:58 -0500 (EST) From: John Baldwin To: freebsd-acpi@freebsd.org Subject: Re: ENXIOing non-present battery Date: Thu, 11 Dec 2014 14:08:50 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20140415; KDE/4.5.5; amd64; ; ) References: <54840781.70603@freebsd.org> In-Reply-To: <54840781.70603@freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201412111408.50866.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 11 Dec 2014 15:55:58 -0500 (EST) Cc: Colin Percival X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Dec 2014 20:56:00 -0000 On Sunday, December 07, 2014 2:53:37 am Colin Percival wrote: > Hi ACPI people, > > On my Dell Latitude E7440 laptop, the ACPI reports two batteries: First > the battery which exists; and second, a "Not Present" battery with zeroed > statistics. FreeBSD, not realizing that this second battery is a complete > myth -- the E7440 only has one battery, and there is nowhere to add another > -- faithfully reports the data from ACPI to userland. > > Unfortunately it causes some problems there; in particular, KDE interprets > it as meaning that the system should have two batteries, and when it sees > that the "second" battery has 0% power remaining it kicks off the "battery > is low, turn the laptop off" code. If that code is disabled, it still > displays the wrong battery-charge-remaining status icons. > > For dealing with such broken ACPIs, it seems like not attaching a non-present > battery would be a good idea. This shouldn't be the default behaviour, since > there are plenty of systems where a non-present battery might be inserted at > a later time; but I see nothing wrong with adding an option. > > The attached patch adds a acpi.cmbat.hide_not_present loader tunable which, > as the name suggests, hides non-present batteries; this is done in the probe > code by returning ENXIO if the tunable is set to a nonzero value and > acpi_BatteryIsPresent returns zero. With this patch and the tunable set my > laptop behaves appropriately; and (aside from wasting a few bytes of memory) > there should be no effect on systems where the tunable is not set. > > Any objections to me committing this? Does setting hint.battery.1.disabled=1 work for you? -- John Baldwin From owner-freebsd-acpi@FreeBSD.ORG Thu Dec 11 21:08:44 2014 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8D11AECD for ; Thu, 11 Dec 2014 21:08:44 +0000 (UTC) Received: from o1.l99.sendgrid.net (o1.l99.sendgrid.net [198.37.153.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 40B1D22C for ; Thu, 11 Dec 2014 21:08:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.info; h=from:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; s=smtpapi; bh=5a5B0hiK6mXnA3c3+t/+ReHIVIU=; b=z2Dx+ERvV8Up9Q6Kdt TLJbSlD6iZ87vUyQvx0pV3fG7pXqgvRtNALvjHFwNxvMkmEJaAef8KYfvehCboA/ peazBBDT5FHl3zcFRLsXb9BCHsNG3QmQvSAjGOsAUibGlK49TKOFbgqNcYrK/G7x Du6pz/uNkZLGvFHlH0wZXWBy0= Received: by filter0104p1mdw1.sendgrid.net with SMTP id filter0104p1mdw1.29669.548A07A93 2014-12-11 21:07:53.429479409 +0000 UTC Received: from mail.tarsnap.com (unknown [10.100.60.97]) by ismtpd-015 (SG) with ESMTP id 14a3b2ded9e.11c6.2ae37 for ; Thu, 11 Dec 2014 21:07:53 +0000 (UTC) Received: (qmail 91869 invoked from network); 11 Dec 2014 21:07:52 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by ec2-107-20-205-189.compute-1.amazonaws.com with ESMTP; 11 Dec 2014 21:07:52 -0000 Received: (qmail 90306 invoked from network); 11 Dec 2014 21:05:49 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by clamshell.daemonology.net with SMTP; 11 Dec 2014 21:05:49 -0000 Message-ID: <548A072D.7090304@freebsd.org> Date: Thu, 11 Dec 2014 13:05:49 -0800 From: Colin Percival User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: John Baldwin , freebsd-acpi@freebsd.org Subject: Re: ENXIOing non-present battery References: <54840781.70603@freebsd.org> <201412111408.50866.jhb@freebsd.org> In-Reply-To: <201412111408.50866.jhb@freebsd.org> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit X-SG-EID: t2fXfoZHCw6vGsGKHqKxJ9qWwHSlQfPdDS+3+p6rOCu6uq3VakQpvOaE8ykMvAQpIsvx2li+ugYxt/ mPVCNMPsLeA+BjvWY9uX6jThG46UB8JJi7WaSJNQqID3fXtnN45/5vcR3Ybb4spgqXMzLnMppustYu 50an34eWpV32sBvO5a9QufLHXYAy5rFkFV2j X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Dec 2014 21:08:44 -0000 On 12/11/14 11:08, John Baldwin wrote: > On Sunday, December 07, 2014 2:53:37 am Colin Percival wrote: >> On my Dell Latitude E7440 laptop, the ACPI reports two batteries: First >> the battery which exists; and second, a "Not Present" battery with zeroed >> statistics. FreeBSD, not realizing that this second battery is a complete >> myth -- the E7440 only has one battery, and there is nowhere to add another >> -- faithfully reports the data from ACPI to userland. > > Does setting hint.battery.1.disabled=1 work for you? That fixes the dev.battery sysctls and KDE's battery monitor. The hw.acpi.battery.units sysctl still reports "2", and `acpiconf -i 1` still reports the phantom battery; but I suppose those don't matter much... -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid From owner-freebsd-acpi@FreeBSD.ORG Fri Dec 12 15:34:32 2014 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7001C375; Fri, 12 Dec 2014 15:34:32 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4AA55989; Fri, 12 Dec 2014 15:34:32 +0000 (UTC) Received: from ralph.baldwin.cx (pool-173-70-85-31.nwrknj.fios.verizon.net [173.70.85.31]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id F1234B99A; Fri, 12 Dec 2014 10:34:30 -0500 (EST) From: John Baldwin To: Colin Percival Subject: Re: ENXIOing non-present battery Date: Fri, 12 Dec 2014 10:21:59 -0500 Message-ID: <6449474.BnGsyZAKhP@ralph.baldwin.cx> User-Agent: KMail/4.14.2 (FreeBSD/10.1-STABLE; KDE/4.14.2; amd64; ; ) In-Reply-To: <548A072D.7090304@freebsd.org> References: <54840781.70603@freebsd.org> <201412111408.50866.jhb@freebsd.org> <548A072D.7090304@freebsd.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 12 Dec 2014 10:34:31 -0500 (EST) Cc: freebsd-acpi@freebsd.org X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2014 15:34:32 -0000 On Thursday, December 11, 2014 01:05:49 PM Colin Percival wrote: > On 12/11/14 11:08, John Baldwin wrote: > > On Sunday, December 07, 2014 2:53:37 am Colin Percival wrote: > >> On my Dell Latitude E7440 laptop, the ACPI reports two batteries: First > >> the battery which exists; and second, a "Not Present" battery with zeroed > >> statistics. FreeBSD, not realizing that this second battery is a complete > >> myth -- the E7440 only has one battery, and there is nowhere to add another > >> -- faithfully reports the data from ACPI to userland. > > > > Does setting hint.battery.1.disabled=1 work for you? > > That fixes the dev.battery sysctls and KDE's battery monitor. The > hw.acpi.battery.units sysctl still reports "2", and `acpiconf -i 1` > still reports the phantom battery; but I suppose those don't matter > much... Ok. That is the "generic" thing we already have in place to disable devices, so I'd probably prefer to use that as the known workaround rather than adding another knob. That said, it looks like we report the userland state of "not present" correctly. I wonder if the bug is in KDE itself and its FreeBSD-specific power management bits (rather than hald)? -- John Baldwin From owner-freebsd-acpi@FreeBSD.ORG Fri Dec 12 22:38:35 2014 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CC32AAE0 for ; Fri, 12 Dec 2014 22:38:35 +0000 (UTC) Received: from o3.shared.sendgrid.net (o3.shared.sendgrid.net [208.117.48.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8C697CDC for ; Fri, 12 Dec 2014 22:38:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.info; h=from:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; s=smtpapi; bh=1uiWLKQpk4ITdtkvJxCzz2VH7TE=; b=jLLws4+IbPAGbRygAO O0E9S5lPedFdvZZH3SJVM45Y9lvx6LpyJi+OIWJ9f89Bq1fdxX3Sqr00m3yIzEeM gSf3V5Idi1sjN/bnd9/1xiPiqv3rX4WDOnpnUHBsyAvHC6Ok9QuFpLYY4lSCwz4S jvGheVB2m+lLuyTv1CBpgyVEg= Received: by filter0090p1mdw1.sendgrid.net with SMTP id filter0090p1mdw1.25258.548B6E6111 2014-12-12 22:38:26.354949715 +0000 UTC Received: from mail.tarsnap.com (unknown [10.100.60.108]) by ismtpd-042 (SG) with ESMTP id 14a40a72ffc.34ed.1cabd3 for ; Fri, 12 Dec 2014 22:38:26 +0000 (UTC) Received: (qmail 48385 invoked from network); 12 Dec 2014 22:38:25 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by ec2-107-20-205-189.compute-1.amazonaws.com with ESMTP; 12 Dec 2014 22:38:25 -0000 Received: (qmail 97960 invoked from network); 12 Dec 2014 22:36:18 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by clamshell.daemonology.net with SMTP; 12 Dec 2014 22:36:18 -0000 Message-ID: <548B6DE2.10509@freebsd.org> Date: Fri, 12 Dec 2014 14:36:18 -0800 From: Colin Percival User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: John Baldwin Subject: Re: ENXIOing non-present battery References: <54840781.70603@freebsd.org> <201412111408.50866.jhb@freebsd.org> <548A072D.7090304@freebsd.org> <6449474.BnGsyZAKhP@ralph.baldwin.cx> In-Reply-To: <6449474.BnGsyZAKhP@ralph.baldwin.cx> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SG-EID: t2fXfoZHCw6vGsGKHqKxJ9qWwHSlQfPdDS+3+p6rOCtJ/ffsGzU76XNv01xIcXIBtbthL7N/004pMG ow6a2rlFAQnpjTJxOh5OuVTH058LBm2TyEJypMsOFEKVdQDbQ9iv3ma+rcEZ/YR632MGjsklbhLNoA ZwaF6TuuH3z5p7pyHwtBu1Xzm8fKy4X4WeSU Cc: freebsd-acpi@freebsd.org X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2014 22:38:35 -0000 On 12/12/14 07:21, John Baldwin wrote: > On Thursday, December 11, 2014 01:05:49 PM Colin Percival wrote: >> On 12/11/14 11:08, John Baldwin wrote: >>> Does setting hint.battery.1.disabled=1 work for you? >> >> That fixes the dev.battery sysctls and KDE's battery monitor. The >> hw.acpi.battery.units sysctl still reports "2", and `acpiconf -i 1` >> still reports the phantom battery; but I suppose those don't matter >> much... > > Ok. That is the "generic" thing we already have in place to disable devices, > so I'd probably prefer to use that as the known workaround rather than adding > another knob. OK, I'll stick to using that one. My original thinking was that disabling "whatever isn't present" would avoid the need for a user to figure out which number it was; but it's probably safe to assume that batteries will always be probed in the same order... > That said, it looks like we report the userland state of "not > present" correctly. I wonder if the bug is in KDE itself and its > FreeBSD-specific power management bits (rather than hald)? The FreeBSD-specific userland bits are in hald. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid From owner-freebsd-acpi@FreeBSD.ORG Sat Dec 13 05:48:55 2014 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 13EEB3D5; Sat, 13 Dec 2014 05:48:55 +0000 (UTC) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5AE96B2C; Sat, 13 Dec 2014 05:48:53 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id sBD5mnqM043808; Sat, 13 Dec 2014 16:48:49 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Sat, 13 Dec 2014 16:48:48 +1100 (EST) From: Ian Smith To: Colin Percival Subject: Re: ENXIOing non-present battery In-Reply-To: <548B6DE2.10509@freebsd.org> Message-ID: <20141213154603.L68123@sola.nimnet.asn.au> References: <54840781.70603@freebsd.org> <201412111408.50866.jhb@freebsd.org> <548A072D.7090304@freebsd.org> <6449474.BnGsyZAKhP@ralph.baldwin.cx> <548B6DE2.10509@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-acpi@freebsd.org X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Dec 2014 05:48:55 -0000 On Fri, 12 Dec 2014 14:36:18 -0800, Colin Percival wrote: > On 12/12/14 07:21, John Baldwin wrote: > > On Thursday, December 11, 2014 01:05:49 PM Colin Percival wrote: > >> On 12/11/14 11:08, John Baldwin wrote: > >>> Does setting hint.battery.1.disabled=1 work for you? > >> > >> That fixes the dev.battery sysctls and KDE's battery monitor. The > >> hw.acpi.battery.units sysctl still reports "2", and `acpiconf -i 1` > >> still reports the phantom battery; but I suppose those don't matter > >> much... > > > > Ok. That is the "generic" thing we already have in place to disable devices, > > so I'd probably prefer to use that as the known workaround rather than adding > > another knob. > > OK, I'll stick to using that one. My original thinking was that disabling > "whatever isn't present" would avoid the need for a user to figure out which > number it was; but it's probably safe to assume that batteries will always > be probed in the same order... I believe so, given that they're enumerated that way in the AML, and disassemble to such as BAT0 and BAT1. On my X200 for instance, there's quite a bit of ASL code about whether it's docked or not controlling BATn notifications, as with these and some HPs I've tried to follow that's where a second battery may live. It wouldn't surprise me to find 'DCK' or similar symbols in your ASL, and BAT0 or BAT1 conditionally enabled (or visible) or not, assuming there'd be a dock available for that model, or family? > > That said, it looks like we report the userland state of "not > > present" correctly. I wonder if the bug is in KDE itself and its > > FreeBSD-specific power management bits (rather than hald)? > > The FreeBSD-specific userland bits are in hald. I've yet to update my 9.3-PRE X200 to new Xorg and a later KDE than that installed at 9.2-R, and disabled what I could of KDE's power mgmt stuff, but haven't noticed reports of other laptops having this specific issue. Maybe hald is being misinformed? Care to put up the acpidump somewhere? Not that I could follow it well enough to debug, if that were the issue, but there might be an obvious clue .. Though you may be happy with the workaround and have other stuff to do! cheers, Ian