From owner-freebsd-acpi@FreeBSD.ORG Tue Jul 15 18:22:30 2014 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 65AAD3D5 for ; Tue, 15 Jul 2014 18:22:30 +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 B1E0824D9 for ; Tue, 15 Jul 2014 18:22:28 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id s6FIMLFt086874; Wed, 16 Jul 2014 04:22:21 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Wed, 16 Jul 2014 04:22:21 +1000 (EST) From: Ian Smith To: Daniele Mazzotti Subject: Re: ACPI support - Freebsd 10 on Sony Vaio VPCCA3C5E In-Reply-To: Message-ID: <20140716040719.Y50382@sola.nimnet.asn.au> References: <53BF0546.70505@att.net> <53BFCBF4.2090104@att.net> <53C020CE.8010205@att.net> <53C02604.9070207@att.net> <53C3D322.3080302@att.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Anthony Jenkins , freebsd-acpi@freebsd.org X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jul 2014 18:22:30 -0000 On Tue, 15 Jul 2014 19:49:46 +0200, Daniele Mazzotti wrote: > I made a few step ahead (at least on my side) and tried to follow the > recommendation from the handbook ( > http://www.pl.freebsd.org/doc/handbook/acpi-debug.html). > > I was able to turn on the verbose boot and here you can find the output: > http://pastebin.com/kkDAZEVb. At boot time I can see an error stating > "battery0: battery initialization failed, giving up" which is thrown by the > acpi_cmbat_init_battery within acpi_cmbat.c module. After six retries the > error is printed out. Actually I am not able to figure out who is calling > the method, but that is another story. Actually you'll see those messages on a 'normal' verbose boot, ie there's nothing extra logged of note regarding battery issues. If you are up for lots more output on one boot at least, perhaps try what acpi(4) suggests: debug.acpi.layer="ACPI_ALL_COMPONENTS ACPI_ALL_DRIVERS" debug.acpi.level="ACPI_LV_ALL_EXCEPTIONS" which is less deep, but wider :) Communications with batteries often, likely usually, is moderated by the embedded controler (ACPI_EC) and it wouldn't hurt to report any exceptions from other subsystems also. If that yields nothing useful you could increase the level .. Sorry, I can't read messages backwards very well, so I'll drop the tail. cheers, Ian