From owner-freebsd-acpi@FreeBSD.ORG Sun Nov 6 01:34: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 912C016A41F; Sun, 6 Nov 2005 01:34:18 +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 27D1643D46; Sun, 6 Nov 2005 01:34:18 +0000 (GMT) (envelope-from nate@root.org) Received: from ylpvm01.prodigy.net (ylpvm01-int.prodigy.net [207.115.5.207]) by ylpvm12.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id jA61Yfil032701; Sat, 5 Nov 2005 20:34:41 -0500 X-ORBL: [71.139.0.107] Received: from [10.0.5.50] (ppp-71-139-0-107.dsl.snfc21.pacbell.net [71.139.0.107]) by ylpvm01.prodigy.net (8.13.4 dk-milter linux/8.13.4) with ESMTP id jA61cNM2032405; Sat, 5 Nov 2005 20:38:23 -0500 Message-ID: <436D5D95.3040901@root.org> Date: Sat, 05 Nov 2005 17:34:13 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050723) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mike Silbersack References: <200511052355.jA5NtuPg026403@repoman.freebsd.org> <20051105191616.M870@odysseus.silby.com> In-Reply-To: <20051105191616.M870@odysseus.silby.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: acpi@FreeBSD.org Subject: Re: cvs commit: src/sys/conf files src/sys/modules/acpi/acpi Makefile src/sys/dev/acpica acpi_battery.c acpi_smbat.c acpi_smbus.h acpiio.h 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, 06 Nov 2005 01:34:19 -0000 Moving to the acpi@ list. Mike Silbersack wrote: > > Hm, since I cvsup'd from last week's releng_6 to today's, I noticed two > acpi-related things. > > 1. The smart battery support seems to work properly for me. However, > the sysctls hw.acpi.battery.life, hw.acpi.battery.time, and > hw.acpi.battery.state take forever to read, so a sysctl -a | grep acpi > (or any other use of sysctl -a) takes far longer than it used to. Sprinkle some printfs into sys/dev/acpica/acpi_smbat.c, in particular the bst and bif functions. Are they timing out? Where is the time spent, reading from the EC? > 2. Now, powerd seems to be causing ~30% system cpu load - top shows it > switching between the "nanslp" and "ecpoll" wait states. This may be > due to some other recent change to acpi, I'm not sure how to best test. ecpoll is the sleep label in acpi_ec.c for accessing the embedded controller. The only thing powerd does that is related to acpi is read the AC line status. So perhaps that hits your ec and it is timing out. Can you try the powerd from -current? It waits for events from devd instead of polling the AC line status. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Sun Nov 6 22:40:00 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 C1C9C16A41F; Sun, 6 Nov 2005 22:40:00 +0000 (GMT) (envelope-from vaibhave@cs.utah.edu) Received: from mail-svr1.cs.utah.edu (mail-svr1.cs.utah.edu [155.98.64.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5FB8743D6E; Sun, 6 Nov 2005 22:40:00 +0000 (GMT) (envelope-from vaibhave@cs.utah.edu) Received: from localhost (localhost [127.0.0.1]) by mail-svr1.cs.utah.edu (Postfix) with ESMTP id F0061346E0; Sun, 6 Nov 2005 15:39:58 -0700 (MST) Received: from mail-svr1.cs.utah.edu ([127.0.0.1]) by localhost (mail-svr1.cs.utah.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 20413-02; Sun, 6 Nov 2005 15:39:58 -0700 (MST) Received: from trust.cs.utah.edu (trust.cs.utah.edu [155.98.65.28]) by mail-svr1.cs.utah.edu (Postfix) with ESMTP id 99F2A346D3; Sun, 6 Nov 2005 15:39:58 -0700 (MST) Received: by trust.cs.utah.edu (Postfix, from userid 4969) id 779AD3F71; Sun, 6 Nov 2005 15:39:58 -0700 (MST) Received: from localhost (localhost [127.0.0.1]) by trust.cs.utah.edu (Postfix) with ESMTP id 5F6723F6C; Sun, 6 Nov 2005 15:39:58 -0700 (MST) Date: Sun, 6 Nov 2005 15:39:58 -0700 (MST) From: Vaibhave Agarwal To: John Baldwin In-Reply-To: <200511061012.57212.jhb@FreeBSD.org> Message-ID: References: <20051027233636.GA39380@dmw.hopto.org> <200511061012.57212.jhb@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: amavisd-new at cs.utah.edu Cc: freebsd-net@FreeBSD.org, freebsd-acpi@freebsd.org, current@FreeBSD.org, chris@gnome.co.uk Subject: Re: Freebsd 6.0 doesnt detect local APIC on a Pentium 3 machine 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, 06 Nov 2005 22:40:01 -0000 On Sun, 6 Nov 2005, John Baldwin wrote: > We don't detect the local APIC via MSR's or the APIC bit in cpu_features, but > rely on a working MP Table or MADT table to setup both the local APIC(s) and > I/O APIC(s). Does your machine have a valid MP Table or an APIC table in its > acpidump? Many UP machine BIOSes don't include those tables. > I think you are right. There is no valid APIC table in the acpidump. The only place where APIC is mentioned in the acpidump(8) is in following: Scope (\_SB) { Name (APIC, 0x00) Method (_PIC, 1, NotSerialized) { Store (Arg0, APIC) } } And I suppose APIC is disabled in the BIOS too. Is there a way to enable APIC using software, without changing the BIOS, since I dont have access to the BIOS, as it is a remote machine (with root access) ? Thanks vaibhave From owner-freebsd-acpi@FreeBSD.ORG Sun Nov 6 22:45:03 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 C351E16A41F; Sun, 6 Nov 2005 22:45:03 +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 C231E43D6A; Sun, 6 Nov 2005 22:44:58 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.5.50] (ppp-71-139-0-107.dsl.snfc21.pacbell.net [71.139.0.107]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id jA6MiUxq018172 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 6 Nov 2005 14:44:31 -0800 Message-ID: <436E874E.4010305@root.org> Date: Sun, 06 Nov 2005 14:44:30 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vaibhave Agarwal References: <20051027233636.GA39380@dmw.hopto.org> <200511061012.57212.jhb@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@FreeBSD.org, freebsd-acpi@FreeBSD.org, chris@gnome.co.uk, current@FreeBSD.org, John Baldwin Subject: Re: Freebsd 6.0 doesnt detect local APIC on a Pentium 3 machine 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, 06 Nov 2005 22:45:04 -0000 Vaibhave Agarwal wrote: > On Sun, 6 Nov 2005, John Baldwin wrote: > > >>We don't detect the local APIC via MSR's or the APIC bit in cpu_features, but >>rely on a working MP Table or MADT table to setup both the local APIC(s) and >>I/O APIC(s). Does your machine have a valid MP Table or an APIC table in its >>acpidump? Many UP machine BIOSes don't include those tables. >> > > > I think you are right. > There is no valid APIC table in the acpidump. > The only place where APIC is mentioned in the acpidump(8) is in following: > > Scope (\_SB) > { > Name (APIC, 0x00) > Method (_PIC, 1, NotSerialized) > { > Store (Arg0, APIC) > } > } > > > And I suppose APIC is disabled in the BIOS too. > Is there a way to enable APIC using software, without changing the BIOS, > since I dont have access to the BIOS, as it is a remote machine (with > root access) ? The above references to APIC just store a value in a convenience variable. If there's nothing else in the AML that references the \_SB.APIC variable, then it has no effect on the system. In that case, the only way to get APIC support on that machine is to implement another way of enumerating it. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 7 11:01:58 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 4676816A421 for ; Mon, 7 Nov 2005 11:01:58 +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 0E2EF43D48 for ; Mon, 7 Nov 2005 11:01:58 +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 jA7B1v7P049739 for ; Mon, 7 Nov 2005 11:01:57 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jA7B1vQj049733 for freebsd-acpi@freebsd.org; Mon, 7 Nov 2005 11:01:57 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 7 Nov 2005 11:01:57 GMT Message-Id: <200511071101.jA7B1vQj049733@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, 07 Nov 2005 11:01:58 -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 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 10 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/03/17] kern/64365 acpi ACPI problems o [2004/05/28] kern/67309 acpi zzz reboot computer (ACPI S3) 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 [feature request] acpi / power-on by time 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 8 problems total. From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 7 16:18:59 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 B882916A420; Mon, 7 Nov 2005 16:18:59 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail5.speedfactory.net [66.23.216.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAA5A43D86; Mon, 7 Nov 2005 16:18:42 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 1523317 for multiple; Mon, 07 Nov 2005 11:20:40 -0500 Received: from localhost.baldwin.cx (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jA7GIXrN011431; Mon, 7 Nov 2005 11:18:33 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-acpi@freebsd.org Date: Mon, 7 Nov 2005 11:05:56 -0500 User-Agent: KMail/1.8.2 References: <20051027233636.GA39380@dmw.hopto.org> <436E874E.4010305@root.org> In-Reply-To: <436E874E.4010305@root.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511071105.58729.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=100 Cc: freebsd-net@freebsd.org, current@freebsd.org, chris@gnome.co.uk Subject: Re: Freebsd 6.0 doesnt detect local APIC on a Pentium 3 machine 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, 07 Nov 2005 16:18:59 -0000 On Sunday 06 November 2005 05:44 pm, Nate Lawson wrote: > Vaibhave Agarwal wrote: > > On Sun, 6 Nov 2005, John Baldwin wrote: > >>We don't detect the local APIC via MSR's or the APIC bit in cpu_features, > >> but rely on a working MP Table or MADT table to setup both the local > >> APIC(s) and I/O APIC(s). Does your machine have a valid MP Table or an > >> APIC table in its acpidump? Many UP machine BIOSes don't include those > >> tables. > > > > I think you are right. > > There is no valid APIC table in the acpidump. > > The only place where APIC is mentioned in the acpidump(8) is in > > following: > > > > Scope (\_SB) > > { > > Name (APIC, 0x00) > > Method (_PIC, 1, NotSerialized) > > { > > Store (Arg0, APIC) > > } > > } > > > > > > And I suppose APIC is disabled in the BIOS too. > > Is there a way to enable APIC using software, without changing the BIOS, > > since I dont have access to the BIOS, as it is a remote machine (with > > root access) ? > > The above references to APIC just store a value in a convenience > variable. If there's nothing else in the AML that references the > \_SB.APIC variable, then it has no effect on the system. In that case, > the only way to get APIC support on that machine is to implement another > way of enumerating it. And even then it can't be used for any device interrupts since there aren't any I/O APICs. On a UP machine without I/O APICs, it's actually probably more optimal to just use irq0 and irq8 for clocks rather than the lapic timer anyway. The only real possible gain is the ability to use the profiling interrupt from the local APIC. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 8 01:38:02 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 8F5AF16A420; Tue, 8 Nov 2005 01:38:02 +0000 (GMT) (envelope-from vaibhave@cs.utah.edu) Received: from mail-svr1.cs.utah.edu (mail-svr1.cs.utah.edu [155.98.64.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id AAFD043D55; Tue, 8 Nov 2005 01:38:01 +0000 (GMT) (envelope-from vaibhave@cs.utah.edu) Received: from localhost (localhost [127.0.0.1]) by mail-svr1.cs.utah.edu (Postfix) with ESMTP id DA366346E0; Mon, 7 Nov 2005 18:38:00 -0700 (MST) Received: from mail-svr1.cs.utah.edu ([127.0.0.1]) by localhost (mail-svr1.cs.utah.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 15215-09; Mon, 7 Nov 2005 18:38:00 -0700 (MST) Received: from trust.cs.utah.edu (trust.cs.utah.edu [155.98.65.28]) by mail-svr1.cs.utah.edu (Postfix) with ESMTP id 816B034692; Mon, 7 Nov 2005 18:38:00 -0700 (MST) Received: by trust.cs.utah.edu (Postfix, from userid 4969) id 754343F71; Mon, 7 Nov 2005 18:38:00 -0700 (MST) Received: from localhost (localhost [127.0.0.1]) by trust.cs.utah.edu (Postfix) with ESMTP id 726BC3F6C; Mon, 7 Nov 2005 18:38:00 -0700 (MST) Date: Mon, 7 Nov 2005 18:38:00 -0700 (MST) From: Vaibhave Agarwal To: John Baldwin In-Reply-To: <200511071105.58729.jhb@freebsd.org> Message-ID: References: <20051027233636.GA39380@dmw.hopto.org> <436E874E.4010305@root.org> <200511071105.58729.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: amavisd-new at cs.utah.edu Cc: freebsd-net@freebsd.org, freebsd-acpi@freebsd.org, current@freebsd.org Subject: Re: Freebsd 6.0 doesnt detect local APIC on a Pentium 3 machine 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, 08 Nov 2005 01:38:02 -0000 On Mon, 7 Nov 2005, John Baldwin wrote: > And even then it can't be used for any device interrupts since there aren't > any I/O APICs. On a UP machine without I/O APICs, it's actually probably > more optimal to just use irq0 and irq8 for clocks rather than the lapic timer > anyway. The only real possible gain is the ability to use the profiling > interrupt from the local APIC. I got access to the BIOS of the Pentium 3 machine I am using, but it has no option to enable/disable the local APIC. Joseph Koshy is right, Linux enables the local APIC timer while booting up. I got the following in the bootup log of Linux 2.4 kernel on the same machine. ------------------------- Local APIC disabled by BIOS -- reenabling. Found and enabled local APIC! Using local APIC timer interrupts. calibrating APIC timer ... ------------------------- Though there is no I/O apic in the UP machines, but I only wanted to use local APIC timer in the lapic_timer_oneshot() mode to schedule few timers accurately. thanks vaibhave From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 8 08:21: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 86CFF16A41F for ; Tue, 8 Nov 2005 08:21:15 +0000 (GMT) (envelope-from q@galgenberg.net) Received: from wrzx28.rz.uni-wuerzburg.de (wrzx28.rz.uni-wuerzburg.de [132.187.3.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6191143D49 for ; Tue, 8 Nov 2005 08:21:01 +0000 (GMT) (envelope-from q@galgenberg.net) Received: from wrzx30.rz.uni-wuerzburg.de (wrzx30.rz.uni-wuerzburg.de [132.187.1.30]) by wrzx28.rz.uni-wuerzburg.de (Postfix) with ESMTP id 1D6E513F1A3 for ; Tue, 8 Nov 2005 09:21:01 +0100 (CET) Received: from virusscan (localhost [127.0.0.1]) by wrzx30.rz.uni-wuerzburg.de (Postfix) with ESMTP id DC7F09F1DF for ; Tue, 8 Nov 2005 09:21:00 +0100 (CET) Received: from wrzx28.rz.uni-wuerzburg.de (wrzx28.rz.uni-wuerzburg.de [132.187.3.28]) by wrzx30.rz.uni-wuerzburg.de (Postfix) with ESMTP id B1D8E9F1CA for ; Tue, 8 Nov 2005 09:21:00 +0100 (CET) Received: from frodo.galgenberg.net (wwsx14.win-screen.uni-wuerzburg.de [132.187.253.14]) by wrzx28.rz.uni-wuerzburg.de (Postfix) with ESMTP id 73E7513F213 for ; Tue, 8 Nov 2005 09:21:00 +0100 (CET) Received: from coyote.q.local (gb-21-237.galgenberg.net [172.16.21.237]) by frodo.galgenberg.net (8.13.1/8.13.1) with ESMTP id jA88L0LZ022874 for ; Tue, 8 Nov 2005 09:21:00 +0100 (CET) (envelope-from q@galgenberg.net) Received: from roadrunner.q.local (roadrunner.q.local [192.168.0.148]) by coyote.q.local (8.13.4/8.13.4) with ESMTP id jA88L09X085363 for ; Tue, 8 Nov 2005 09:21:00 +0100 (CET) (envelope-from q@galgenberg.net) Received: from roadrunner.q.local (localhost [127.0.0.1]) by roadrunner.q.local (8.13.4/8.13.4) with ESMTP id jA88L0vx011813 for ; Tue, 8 Nov 2005 09:21:00 +0100 (CET) (envelope-from q@galgenberg.net) Received: (from q@localhost) by roadrunner.q.local (8.13.4/8.13.4/Submit) id jA88KvMr011812 for acpi@freebsd.org; Tue, 8 Nov 2005 09:20:57 +0100 (CET) (envelope-from q@galgenberg.net) Date: Tue, 8 Nov 2005 09:20:57 +0100 From: Ulrich Spoerlein To: acpi@freebsd.org Message-ID: <20051108082057.GB1067@galgenberg.net> Mail-Followup-To: acpi@freebsd.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7iMSBzlTiPOCCT2k" Content-Disposition: inline X-Virus-Scanned: by amavisd-new (Rechenzentrum Universitaet Wuerzburg) Cc: Subject: Battery woes since going 6.0-BETA3 -> 6.0-STABLE 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, 08 Nov 2005 08:21:15 -0000 --7iMSBzlTiPOCCT2k Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Good morning everyone, I updated my system yesterday from BETA3 to the current RELENG_6. Booting my system this morning, I found it in a rather unusable state. First of all, there were problems with BETA3 before. When charging the battery (only when charging!) wmbsdbatt would periodically freeze the system which made MP3 playback impossible. Ok, I first thought wmbsdbatt is calling sysctl to get the values and sysctl is under Giant. So no problem. Funny thing is, it only occurred when charging, not when running on batteries or without them. Now updating to the current RELENG_6 I get the system freezes whenever running wmbsdbatt. This goes as far as the USB devices losing contact (!!). I thought my kbd/mouse went wacko, and found the following in messages Nov 8 08:57:22 roadrunner kernel: ukbd0: at uhub4 port 1 (addr 3) disconne= cted Nov 8 08:57:22 roadrunner kernel: ukbd0: detached Nov 8 08:57:22 roadrunner kernel: ums0: at uhub4 port 1 (addr 3) disconnec= ted Nov 8 08:57:22 roadrunner kernel: ums0: detached Nov 8 08:57:22 roadrunner moused: unable to open /dev/ums0: No such file o= r directory Nov 8 08:57:22 roadrunner kernel: ukbd0: CHESEN PS2 to USB Converter, rev = 1.10/0.10, addr 3, iclass 3/1 Nov 8 08:57:22 roadrunner kernel: kbd1 at ukbd0 Nov 8 08:57:22 roadrunner kernel: ums0: CHESEN PS2 to USB Converter, rev 1= =2E10/0.10, addr 3, iclass 3/1 Nov 8 08:57:22 roadrunner kernel: ums0: 5 buttons and Z dir. Nov 8 08:58:39 roadrunner kernel: ukbd0: at uhub4 port 1 (addr 3) disconne= cted Nov 8 08:58:39 roadrunner kernel: ukbd0: detached Nov 8 08:58:39 roadrunner kernel: ums0: at uhub4 port 1 (addr 3) disconnec= ted Nov 8 08:58:39 roadrunner kernel: ums0: detached Nov 8 08:58:39 roadrunner moused: unable to open /dev/ums0: No such file o= r directory Nov 8 08:58:40 roadrunner kernel: ukbd0: CHESEN PS2 to USB Converter, rev = 1.10/0.10, addr 3, iclass 3/1 Nov 8 08:58:40 roadrunner kernel: kbd1 at ukbd0 Nov 8 08:58:40 roadrunner kernel: ums0: CHESEN PS2 to USB Converter, rev 1= =2E10/0.10, addr 3, iclass 3/1 Nov 8 08:58:40 roadrunner kernel: ums0: 5 buttons and Z dir. Nov 8 08:58:50 roadrunner kernel: ukbd0: at uhub4 port 1 (addr 3) disconne= cted Nov 8 08:58:50 roadrunner kernel: ukbd0: detached Nov 8 08:58:50 roadrunner kernel: ums0: at uhub4 port 1 (addr 3) disconnec= ted Nov 8 08:58:50 roadrunner kernel: ums0: detached Nov 8 08:58:50 roadrunner moused: unable to open /dev/ums0: No such file o= r directory Nov 8 08:58:51 roadrunner kernel: ukbd0: CHESEN PS2 to USB Converter, rev = 1.10/0.10, addr 3, iclass 3/1 Nov 8 08:58:51 roadrunner kernel: kbd1 at ukbd0 Nov 8 08:58:51 roadrunner kernel: ums0: CHESEN PS2 to USB Converter, rev 1= =2E10/0.10, addr 3, iclass 3/1 Nov 8 08:58:51 roadrunner kernel: ums0: 5 buttons and Z dir. Nov 8 08:59:23 roadrunner kernel: ukbd0: at uhub4 port 1 (addr 3) disconne= cted Nov 8 08:59:23 roadrunner kernel: ukbd0: detached Nov 8 08:59:23 roadrunner kernel: ums0: at uhub4 port 1 (addr 3) disconnec= ted Nov 8 08:59:23 roadrunner kernel: ums0: detached Nov 8 08:59:23 roadrunner moused: unable to open /dev/ums0: No such file o= r directory Nov 8 08:59:24 roadrunner kernel: ukbd0: CHESEN PS2 to USB Converter, rev = 1.10/0.10, addr 3, iclass 3/1 Nov 8 08:59:24 roadrunner kernel: kbd1 at ukbd0 Nov 8 08:59:24 roadrunner kernel: ums0: CHESEN PS2 to USB Converter, rev 1= =2E10/0.10, addr 3, iclass 3/1 Nov 8 08:59:24 roadrunner kernel: ums0: 5 buttons and Z dir. This is because wmbsdbatt is polling the battery (which right now, is not even present, as I'm running on AC). I'm running a Dell Inspiron 8600, these are the relevant acpi lines from dmesg acpi0: on motherboard pci_link0: irq 11 on acpi0 pci_link1: irq 11 on acpi0 pci_link2: irq 11 on acpi0 pci_link3: irq 11 on acpi0 pci_link4: on acpi0 pci_link5: irq 11 on acpi0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 est0: on cpu0 p4tcc0: on cpu0 acpi_acad0: on acpi0 battery0: on acpi0 battery1: on acpi0 acpi_lid0: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 I will revert 6.0-RELEASE for now, I guess the smart battery support is causing problems for me. Running acpiconf -i 0 in a loop makes the hiccups clearly visible, it Will running for several seconds with no pause, then it pauses shortly % while true; do \time acpiconf -i 0 >/dev/null;done 2>&1 | uniq 0.92 real 0.00 user 0.91 sys 0.00 real 0.00 user 0.00 sys 0.13 real 0.00 user 0.00 sys 0.00 real 0.00 user 0.00 sys 0.76 real 0.00 user 0.76 sys 0.00 real 0.00 user 0.00 sys 0.13 real 0.00 user 0.00 sys 0.00 real 0.00 user 0.00 sys 0.38 real 0.00 user 0.37 sys 0.00 real 0.00 user 0.00 sys 0.38 real 0.05 user 0.33 sys 0.00 real 0.00 user 0.00 sys 0.13 real 0.00 user 0.00 sys 0.00 real 0.00 user 0.00 sys 0.13 real 0.00 user 0.00 sys 0.00 real 0.00 user 0.00 sys 0.13 real 0.00 user 0.00 sys 0.00 real 0.00 user 0.00 sys 0.13 real 0.00 user 0.00 sys 0.00 real 0.00 user 0.00 sys Ulrich Spoerlein --=20 PGP Key ID: F0DB9F44 Encrypted mail welcome! Fingerprint: F1CE D062 0CA9 ADE3 349B 2FE8 980A C6B5 F0DB 9F44 Ok, which part of "Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn." didn't you understand? --7iMSBzlTiPOCCT2k Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDcF/pmArGtfDbn0QRAhFfAJ9NenSpm2Dkta7XW4hYu8gx1jUTCwCg5kHz +BsSqWJcZe8UEMww0WQgnLM= =qdgd -----END PGP SIGNATURE----- --7iMSBzlTiPOCCT2k-- From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 8 16:11:09 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 4389516A420; Tue, 8 Nov 2005 16:11:09 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail5.speedfactory.net [66.23.216.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A41143D53; Tue, 8 Nov 2005 16:10:59 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 1586401 for multiple; Tue, 08 Nov 2005 11:13:00 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jA8GAjf5027042; Tue, 8 Nov 2005 11:10:52 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Vaibhave Agarwal Date: Tue, 8 Nov 2005 10:18:51 -0500 User-Agent: KMail/1.8.2 References: <20051027233636.GA39380@dmw.hopto.org> <200511071105.58729.jhb@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511081018.53452.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: freebsd-net@freebsd.org, freebsd-acpi@freebsd.org, current@freebsd.org Subject: Re: Freebsd 6.0 doesnt detect local APIC on a Pentium 3 machine 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, 08 Nov 2005 16:11:09 -0000 On Monday 07 November 2005 08:38 pm, Vaibhave Agarwal wrote: > On Mon, 7 Nov 2005, John Baldwin wrote: > > And even then it can't be used for any device interrupts since there > > aren't any I/O APICs. On a UP machine without I/O APICs, it's actually > > probably more optimal to just use irq0 and irq8 for clocks rather than > > the lapic timer anyway. The only real possible gain is the ability to > > use the profiling interrupt from the local APIC. > > I got access to the BIOS of the Pentium 3 machine I am using, but it has > no option to enable/disable the local APIC. Yes, I've not seen any BIOSen that do. > Joseph Koshy is right, Linux enables the local APIC timer while booting > up. I got the following in the bootup log of Linux 2.4 kernel on the same > machine. > > ------------------------- > Local APIC disabled by BIOS -- reenabling. > Found and enabled local APIC! > > Using local APIC timer interrupts. > calibrating APIC timer ... > ------------------------- Just because Linux does for UP doesn't mean it is more optimal for FreeBSD. :) On FreeBSD with the lapic timer you have 2 * hz interrupts per second. With the irq0/irq8 combo you have hz + stathz interrupts per second. The difference is 2000 vs 1128. Granted, the lapic timer interrupt handler doesn't have to talk to hardware out on the LPC bus.. > Though there is no I/O apic in the UP machines, but I only wanted to use > local APIC timer in the lapic_timer_oneshot() mode to schedule few timers > accurately. You can increase the rate of the rtc timer. We run it at profhz (1024) when profiling is enabled for example. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 9 04:39: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 1AEB916A41F for ; Wed, 9 Nov 2005 04:39:38 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD17D43D45 for ; Wed, 9 Nov 2005 04:39:37 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id jA94bWIl030646 for ; Tue, 8 Nov 2005 21:37:32 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Tue, 08 Nov 2005 21:38:04 -0700 (MST) Message-Id: <20051108.213804.102936607.imp@bsdimp.com> To: acpi@freebsd.org From: "M. Warner Losh" X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Tue, 08 Nov 2005 21:37:32 -0700 (MST) Cc: Subject: acpi_perf 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: Wed, 09 Nov 2005 04:39:38 -0000 A long time ago I disabled acpi_perf because it was causing a double free panic. I'd forgotten that I'd done this until recently when I noticed in the /boot/loader.conf file. I renabled it and now I see: cpu0: on acpi0 acpi_perf0: on cpu0 acpi_perf0: failed in PERF_STATUS attach device_attach: acpi_perf0 attach returned 6 acpi_perf0: on cpu0 acpi_perf0: failed in PERF_STATUS attach device_attach: acpi_perf0 attach returned 6 acpi_throttle0: on cpu0 acpi_lid0: on acpi0 I don't know if this happened before or not, but I was wondering what people think the next step would be. Warner From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 9 05:07:25 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 8CBE316A41F for ; Wed, 9 Nov 2005 05:07:25 +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 42B0F43D49 for ; Wed, 9 Nov 2005 05:07:25 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.250] (ppp-71-139-0-107.dsl.snfc21.pacbell.net [71.139.0.107]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id jA957BDI016206 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 8 Nov 2005 21:07:14 -0800 Message-ID: <437183FA.80804@root.org> Date: Tue, 08 Nov 2005 21:07:06 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "M. Warner Losh" References: <20051108.213804.102936607.imp@bsdimp.com> In-Reply-To: <20051108.213804.102936607.imp@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: acpi@freebsd.org Subject: Re: acpi_perf 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: Wed, 09 Nov 2005 05:07:25 -0000 M. Warner Losh wrote: > A long time ago I disabled acpi_perf because it was causing a double > free panic. I'd forgotten that I'd done this until recently when I > noticed in the /boot/loader.conf file. I renabled it and now I see: > > cpu0: on acpi0 > acpi_perf0: on cpu0 > acpi_perf0: failed in PERF_STATUS attach > device_attach: acpi_perf0 attach returned 6 > acpi_perf0: on cpu0 > acpi_perf0: failed in PERF_STATUS attach > device_attach: acpi_perf0 attach returned 6 > acpi_throttle0: on cpu0 > acpi_lid0: on acpi0 > > I don't know if this happened before or not, but I was wondering what > people think the next step would be. Dump your ASL and look for what the _PCT method returns under your Processor object. It will reference two registers, the control and status regs. Post that ASL and we'll see why register setup is failing. It could be a collision with someone else who has grabbed the SMI port or it is not an IO or Memory-based register. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 9 05:27:57 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 EDDA316A41F for ; Wed, 9 Nov 2005 05:27:57 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C95143D46 for ; Wed, 9 Nov 2005 05:27:57 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id jA95RFYh030987; Tue, 8 Nov 2005 22:27:15 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Tue, 08 Nov 2005 22:27:47 -0700 (MST) Message-Id: <20051108.222747.63047404.imp@bsdimp.com> To: nate@root.org From: "M. Warner Losh" In-Reply-To: <4367BCA6.5050609@root.org> References: <78F7D8FC-B5AA-4723-8336-E60F873D9414@club-internet.fr> <4367BCA6.5050609@root.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Tue, 08 Nov 2005 22:27:18 -0700 (MST) Cc: freebsd-acpi@freebsd.org Subject: Re: ACPI and 3.0 specification 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: Wed, 09 Nov 2005 05:27:58 -0000 In message: <4367BCA6.5050609@root.org> Nate Lawson writes: : acpi 3.0 adds very little useful stuff unless you're interested in large : NUMA machines. We'd be better off implementing more support for those : systems in the main kernel and then acpi, not the other way around. PCIE and SATA sounds useful, and Ambient Light Sensor and User Presense device sounds both cool and ominous :-) I agree with you about numa. Warner From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 9 05:49:03 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 C514E16A41F for ; Wed, 9 Nov 2005 05:49:03 +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 75E9343D4C for ; Wed, 9 Nov 2005 05:49:03 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.250] (ppp-71-139-0-107.dsl.snfc21.pacbell.net [71.139.0.107]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id jA95mrDI016458 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 8 Nov 2005 21:48:53 -0800 Message-ID: <43718DBF.40302@root.org> Date: Tue, 08 Nov 2005 21:48:47 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "M. Warner Losh" References: <78F7D8FC-B5AA-4723-8336-E60F873D9414@club-internet.fr> <4367BCA6.5050609@root.org> <20051108.222747.63047404.imp@bsdimp.com> In-Reply-To: <20051108.222747.63047404.imp@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: ACPI and 3.0 specification 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: Wed, 09 Nov 2005 05:49:03 -0000 M. Warner Losh wrote: > In message: <4367BCA6.5050609@root.org> > Nate Lawson writes: > : acpi 3.0 adds very little useful stuff unless you're interested in large > : NUMA machines. We'd be better off implementing more support for those > : systems in the main kernel and then acpi, not the other way around. > > PCIE and SATA sounds useful, and Ambient Light Sensor and User > Presense device sounds both cool and ominous :-) I agree with you > about numa. The best next move is probably for the maintainers of those subsystems to integrate acpi to begin with. PCIe support appears to be underway. I'm not sure about ATA but a good first step would be to associate an ACPI handle with each ATA bus (PRI, SEC, etc.) -- Nate From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 9 18:03:32 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 4042D16A41F for ; Wed, 9 Nov 2005 18:03:32 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB8E843D46 for ; Wed, 9 Nov 2005 18:03:31 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id jA9I3NWP029088; Wed, 9 Nov 2005 10:03:23 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id jA9I3NXH029087; Wed, 9 Nov 2005 10:03:23 -0800 Date: Wed, 9 Nov 2005 10:03:23 -0800 From: Brooks Davis To: Nate Lawson Message-ID: <20051109180323.GA12837@odin.ac.hmc.edu> References: <78F7D8FC-B5AA-4723-8336-E60F873D9414@club-internet.fr> <4367BCA6.5050609@root.org> <20051108.222747.63047404.imp@bsdimp.com> <43718DBF.40302@root.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YiEDa0DAkWCtVeE4" Content-Disposition: inline In-Reply-To: <43718DBF.40302@root.org> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Cc: freebsd-acpi@freebsd.org Subject: Re: ACPI and 3.0 specification 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: Wed, 09 Nov 2005 18:03:32 -0000 --YiEDa0DAkWCtVeE4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 08, 2005 at 09:48:47PM -0800, Nate Lawson wrote: > M. Warner Losh wrote: > >In message: <4367BCA6.5050609@root.org> > > Nate Lawson writes: > >: acpi 3.0 adds very little useful stuff unless you're interested in lar= ge=20 > >: NUMA machines. We'd be better off implementing more support for those= =20 > >: systems in the main kernel and then acpi, not the other way around. > > > >PCIE and SATA sounds useful, and Ambient Light Sensor and User > >Presense device sounds both cool and ominous :-) I agree with you > >about numa. >=20 > The best next move is probably for the maintainers of those subsystems=20 > to integrate acpi to begin with. PCIe support appears to be underway.= =20 > I'm not sure about ATA but a good first step would be to associate an=20 > ACPI handle with each ATA bus (PRI, SEC, etc.) ATA support would be nice since I think it's needed to fix the Thinkpad docking problem correctly. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --YiEDa0DAkWCtVeE4 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDcjnqXY6L6fI4GtQRAplPAKC+moK0P+jiFut+USBv+dvdahX7gQCfSj2n /ERKNzXjDHkP2Nc6yPzunW8= =6pTe -----END PGP SIGNATURE----- --YiEDa0DAkWCtVeE4-- From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 9 19:11:59 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 26B6916A41F for ; Wed, 9 Nov 2005 19:11:59 +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 12DA743D4C for ; Wed, 9 Nov 2005 19:11:57 +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 jA9JBVDI028087 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 9 Nov 2005 11:11:47 -0800 Message-ID: <437249E2.8050406@root.org> Date: Wed, 09 Nov 2005 11:11:30 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brooks Davis References: <78F7D8FC-B5AA-4723-8336-E60F873D9414@club-internet.fr> <4367BCA6.5050609@root.org> <20051108.222747.63047404.imp@bsdimp.com> <43718DBF.40302@root.org> <20051109180323.GA12837@odin.ac.hmc.edu> In-Reply-To: <20051109180323.GA12837@odin.ac.hmc.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: ACPI and 3.0 specification 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: Wed, 09 Nov 2005 19:11:59 -0000 Brooks Davis wrote: > On Tue, Nov 08, 2005 at 09:48:47PM -0800, Nate Lawson wrote: > >>M. Warner Losh wrote: >> >>>In message: <4367BCA6.5050609@root.org> >>> Nate Lawson writes: >>>: acpi 3.0 adds very little useful stuff unless you're interested in large >>>: NUMA machines. We'd be better off implementing more support for those >>>: systems in the main kernel and then acpi, not the other way around. >>> >>>PCIE and SATA sounds useful, and Ambient Light Sensor and User >>>Presense device sounds both cool and ominous :-) I agree with you >>>about numa. >> >>The best next move is probably for the maintainers of those subsystems >>to integrate acpi to begin with. PCIe support appears to be underway. >> I'm not sure about ATA but a good first step would be to associate an >>ACPI handle with each ATA bus (PRI, SEC, etc.) > > > ATA support would be nice since I think it's needed to fix the Thinkpad > docking problem correctly. I'm happy to explain how to do this to anyone writing the code. The PCI code does this already (see sys/dev/acpica/acpi_pci.c, acpi_pci_save_handle) and ATA could be adapted to do this pretty easily since it now has newbus support. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Fri Nov 11 00:06:18 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 18A9916A41F for ; Fri, 11 Nov 2005 00:06:18 +0000 (GMT) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCDCE43D53 for ; Fri, 11 Nov 2005 00:06:17 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.200] ([10.0.0.200]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id jAB06HpU038245 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 10 Nov 2005 16:06:17 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <4373E06A.9070902@errno.com> Date: Thu, 10 Nov 2005 16:06:02 -0800 From: Sam Leffler User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050927) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-acpi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: thermal trip on hp nx6125 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, 11 Nov 2005 00:06:18 -0000 I've got an nx6125 running amd64 current. When I take the laptop off ac I get an immediate thermal shutdown from zone 2 going critical. I traced temp readings and see the following: acpi_tz0: newflags 0, temp 56.0 @ ticks 10080 acpi_tz1: newflags 0, temp 49.0 @ ticks 10081 acpi_tz2: newflags 0, temp 26.6 @ ticks 10088 acpi_tz0: newflags 0, temp 53.0 @ ticks 20096 acpi_tz1: newflags 0, temp 49.0 @ ticks 20105 acpi_tz2: newflags 0, temp 26.6 @ ticks 20114 acpi_tz0: newflags 0, temp 52.0 @ ticks 30123 acpi_tz1: newflags 0, temp 49.0 @ ticks 30132 acpi_tz2: newflags 0, temp 26.6 @ ticks 30141 acpi_tz0: newflags 0, temp 51.0 @ ticks 35148 acpi_tz0: newflags 0, temp 51.0 @ ticks 35185 acpi_tz1: newflags 0, temp 49.0 @ ticks 35194 acpi_tz1: newflags 0, temp 49.0 @ ticks 35209 acpi_tz2: newflags 0, temp 26.6 @ ticks 35219 acpi_tz0: newflags 0, temp 51.0 @ ticks 45229 acpi_tz1: newflags 0, temp 48.0 @ ticks 45238 acpi_tz2: newflags 9, temp 152.1 @ ticks 45247 acpi_tz0: newflags 0, temp 50.0 @ ticks 55256 acpi_tz1: newflags 0, temp 48.0 @ ticks 55265 acpi_tz2: newflags 9, temp 152.1 @ ticks 55273 acpi_tz0: newflags 0, temp 50.0 @ ticks 65283 acpi_tz1: newflags 0, temp 48.0 @ ticks 65293 acpi_tz2: newflags 9, temp 152.1 @ ticks 65301 acpi_tz2: WARNING - current temperature (152.1C) exceeds safe limits This condition persists if I disable the shutdown call in acpi_thermal.c. Once returned to ac the zone immediately returns to <30C. I felt around for a hotspot but cannot find one so figure this may be an acpi issue? I checked the mailing list archives and found almost an identical complaint for an nc6230: http://monkey.org/freebsd/archive/freebsd-acpi/200509/msg00071.html I've stuck dmesg (w/ debug printfs) and output from acpidump -t -d on the web: http://people.freebsd.org/~sam/nx6125.dmesg http://people.freebsd.org/~sam/nx6125.acpidump Any suggestions on what to look for? FWIW the fan in zone 0 does seem to kick in a fair amount even when the system is idle. Sam From owner-freebsd-acpi@FreeBSD.ORG Fri Nov 11 15:30:59 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 51B6F16A41F for ; Fri, 11 Nov 2005 15:30:59 +0000 (GMT) (envelope-from bmiele@ipnstock.com) Received: from ms-smtp-04.nyroc.rr.com (ms-smtp-04.nyroc.rr.com [24.24.2.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id C76A543D45 for ; Fri, 11 Nov 2005 15:30:56 +0000 (GMT) (envelope-from bmiele@ipnstock.com) Received: from [10.0.0.154] (cpe-72-224-239-165.maine.res.rr.com [72.224.239.165]) by ms-smtp-04.nyroc.rr.com (8.12.10/8.12.10) with ESMTP id jABFUoV3004940; Fri, 11 Nov 2005 10:30:51 -0500 (EST) Date: Fri, 11 Nov 2005 10:30:50 -0500 (EST) From: bmiele@ipnstock.com To: Sam Leffler In-Reply-To: <4373E06A.9070902@errno.com> Message-ID: <20051111102622.K1185@localhost> References: <4373E06A.9070902@errno.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: freebsd-acpi@freebsd.org Subject: Re: thermal trip on hp nx6125 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, 11 Nov 2005 15:30:59 -0000 Don't know if this is any use in debugging, but a recent adventure in trying to cvsup to 6.0-stable (story for another day) left me doing a iso install back to 5.4. I noticed that the 5.4 install from the original 5.4 release cd did not have this problem. It was only after i CVSUpped from the 5.4 cd install to the most recent 5.x that the problem reappeared. Don't know what changes happened in acpi through the life of 5.4, but it may be of some value. Interested in solving this also. apm allows me to keep the laptop on battery, but i get: apm: can't open /dev/apm: No such file or directory on any usage. regards, Brad On Thu, 10 Nov 2005, Sam Leffler wrote: > I've got an nx6125 running amd64 current. When I take the laptop off ac I > get an immediate thermal shutdown from zone 2 going critical. I traced temp > readings and see the following: > > acpi_tz0: newflags 0, temp 56.0 @ ticks 10080 > acpi_tz1: newflags 0, temp 49.0 @ ticks 10081 > acpi_tz2: newflags 0, temp 26.6 @ ticks 10088 > acpi_tz0: newflags 0, temp 53.0 @ ticks 20096 > acpi_tz1: newflags 0, temp 49.0 @ ticks 20105 > acpi_tz2: newflags 0, temp 26.6 @ ticks 20114 > acpi_tz0: newflags 0, temp 52.0 @ ticks 30123 > acpi_tz1: newflags 0, temp 49.0 @ ticks 30132 > acpi_tz2: newflags 0, temp 26.6 @ ticks 30141 > acpi_tz0: newflags 0, temp 51.0 @ ticks 35148 > acpi_tz0: newflags 0, temp 51.0 @ ticks 35185 > acpi_tz1: newflags 0, temp 49.0 @ ticks 35194 > acpi_tz1: newflags 0, temp 49.0 @ ticks 35209 > acpi_tz2: newflags 0, temp 26.6 @ ticks 35219 > acpi_tz0: newflags 0, temp 51.0 @ ticks 45229 > acpi_tz1: newflags 0, temp 48.0 @ ticks 45238 > acpi_tz2: newflags 9, temp 152.1 @ ticks 45247 > acpi_tz0: newflags 0, temp 50.0 @ ticks 55256 > acpi_tz1: newflags 0, temp 48.0 @ ticks 55265 > acpi_tz2: newflags 9, temp 152.1 @ ticks 55273 > acpi_tz0: newflags 0, temp 50.0 @ ticks 65283 > acpi_tz1: newflags 0, temp 48.0 @ ticks 65293 > acpi_tz2: newflags 9, temp 152.1 @ ticks 65301 > acpi_tz2: WARNING - current temperature (152.1C) exceeds safe limits > > This condition persists if I disable the shutdown call in acpi_thermal.c. > Once returned to ac the zone immediately returns to <30C. I felt around for > a hotspot but cannot find one so figure this may be an acpi issue? > > I checked the mailing list archives and found almost an identical complaint > for an nc6230: > > http://monkey.org/freebsd/archive/freebsd-acpi/200509/msg00071.html > > I've stuck dmesg (w/ debug printfs) and output from acpidump -t -d on the > web: > > http://people.freebsd.org/~sam/nx6125.dmesg > http://people.freebsd.org/~sam/nx6125.acpidump > > Any suggestions on what to look for? FWIW the fan in zone 0 does seem to > kick in a fair amount even when the system is idle. > > Sam > _______________________________________________ > 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 Fri Nov 11 20:42:24 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 2EAF616A41F; Fri, 11 Nov 2005 20:42:24 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id E28FD43D45; Fri, 11 Nov 2005 20:42:23 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jABKgNCJ009650; Fri, 11 Nov 2005 20:42:23 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jABKgNT5009646; Fri, 11 Nov 2005 20:42:23 GMT (envelope-from linimon) Date: Fri, 11 Nov 2005 20:42:23 GMT From: Mark Linimon Message-Id: <200511112042.jABKgNT5009646@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-acpi@FreeBSD.org Cc: Subject: Re: kern/88859: ACPI broken on Compaq DL360 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, 11 Nov 2005 20:42:24 -0000 Synopsis: ACPI broken on Compaq DL360 Responsible-Changed-From-To: freebsd-bugs->freebsd-acpi Responsible-Changed-By: linimon Responsible-Changed-When: Fri Nov 11 20:42:06 GMT 2005 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=88859 From owner-freebsd-acpi@FreeBSD.ORG Fri Nov 11 21:10: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 21C4016A420 for ; Fri, 11 Nov 2005 21:10:19 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id D10F143D4C for ; Fri, 11 Nov 2005 21:10:18 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jABLAI5Z015636 for ; Fri, 11 Nov 2005 21:10:18 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jABLAIoe015635; Fri, 11 Nov 2005 21:10:18 GMT (envelope-from gnats) Date: Fri, 11 Nov 2005 21:10:18 GMT Message-Id: <200511112110.jABLAIoe015635@freefall.freebsd.org> To: freebsd-acpi@FreeBSD.org From: John Baldwin Cc: Subject: Re: kern/88859: ACPI broken on Compaq DL360 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John Baldwin List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Nov 2005 21:10:19 -0000 The following reply was made to PR kern/88859; it has been noted by GNATS. From: John Baldwin To: bug-followup@freebsd.org, tedm@ipinc.net Cc: Subject: Re: kern/88859: ACPI broken on Compaq DL360 Date: Fri, 11 Nov 2005 16:03:08 -0500 Hmm, well, a PCI link named 'FAKE' certainly isn't a good sign. Can you post the acpidump somewhere and reply with the URL? This is probably a bug in your BIOS that might can be worked around using a custom dsdt. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Fri Nov 11 22:00:29 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 0994C16A421 for ; Fri, 11 Nov 2005 22:00:29 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADBBD43D49 for ; Fri, 11 Nov 2005 22:00:28 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jABM0S9x020301 for ; Fri, 11 Nov 2005 22:00:28 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jABM0S42020300; Fri, 11 Nov 2005 22:00:28 GMT (envelope-from gnats) Date: Fri, 11 Nov 2005 22:00:28 GMT Message-Id: <200511112200.jABM0S42020300@freefall.freebsd.org> To: freebsd-acpi@FreeBSD.org From: "Internet Partners, Inc. Tech Support" Cc: Subject: Re: kern/88859: ACPI broken on Compaq DL360 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Internet Partners, Inc. Tech Support" List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Nov 2005 22:00:29 -0000 The following reply was made to PR kern/88859; it has been noted by GNATS. From: "Internet Partners, Inc. Tech Support" To: , "Ted Mittelstaedt" Cc: Subject: Re: kern/88859: ACPI broken on Compaq DL360 Date: Fri, 11 Nov 2005 13:53:42 -0800 The output of the following command: acpidump -t -d -o dl360.dsdt > dl360.asl can be found here: http://www.freebsd-corp-net-guide.com/dl360/dl360.dsdt http://www.freebsd-corp-net-guide.com/dl360/dl360.asl