From owner-freebsd-acpi@FreeBSD.ORG Mon Sep 25 09:08:09 2006 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 D08E616A494; Mon, 25 Sep 2006 09:08:09 +0000 (UTC) (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 518BD43D4C; Mon, 25 Sep 2006 09:08:09 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k8P989aS078235; Mon, 25 Sep 2006 09:08:09 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k8P98958078231; Mon, 25 Sep 2006 09:08:09 GMT (envelope-from linimon) Date: Mon, 25 Sep 2006 09:08:09 GMT From: Mark Linimon Message-Id: <200609250908.k8P98958078231@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-acpi@FreeBSD.org Cc: Subject: Re: kern/103365: [acpi] acpi poweroff doesn't work with geli device attached X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Sep 2006 09:08:09 -0000 Old Synopsis: acpi poweroff doesn't work with geli device attached New Synopsis: [acpi] acpi poweroff doesn't work with geli device attached Responsible-Changed-From-To: freebsd-bugs->freebsd-acpi Responsible-Changed-By: linimon Responsible-Changed-When: Mon Sep 25 09:07:32 UTC 2006 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=103365 From owner-freebsd-acpi@FreeBSD.ORG Mon Sep 25 11:08:24 2006 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 29BBF16A407 for ; Mon, 25 Sep 2006 11:08:24 +0000 (UTC) (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 1AF4243D7B for ; Mon, 25 Sep 2006 11:08:11 +0000 (GMT) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k8PB85To090453 for ; Mon, 25 Sep 2006 11:08:05 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k8PB84eD090449 for freebsd-acpi@FreeBSD.org; Mon, 25 Sep 2006 11:08:04 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 25 Sep 2006 11:08:04 GMT Message-Id: <200609251108.k8PB84eD090449@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: linimon set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-acpi@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Sep 2006 11:08:24 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o i386/54756 acpi ACPI suspend/resume problem on CF-W2 laptop o i386/55661 acpi ACPI suspend/resume problem on ARMADA M700 o kern/55822 acpi No ACPI power off with SMP kernel o kern/56024 acpi ACPI suspend drains battery while in S3 o i386/64002 acpi acpi problem o i386/67273 acpi [hang] system hangs with acpi and Xfree o i386/72566 acpi ACPI, FreeBSD disables fan on Compaq Armada 1750 o i386/79080 acpi acpi thermal changes freezes HP nx6110 o i386/79081 acpi ACPI suspend/resume not working on HP nx6110 o i386/80426 acpi [APIC] [panic] 5.4-RC3 still panic when boot on ASUS P o i386/87568 acpi [ACPI] [REGRESSION] 6.0-STABLE needs ACPI disabled but 11 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/67309 acpi zzz reboot computer (ACPI S3) o i386/69750 acpi Boot without ACPI failed on ASUS L5 o i386/73822 acpi [request] add thermal support to ACPI o kern/73823 acpi [feature request] acpi / power-on by timer support f kern/74030 acpi Unplugging AC causes battery % to stay locked at 98% f kern/90871 acpi ACPI problems with ASUS A8N-VM-CSM o kern/97383 acpi Volume buttons on IBM Thinkpad crash system with ACPI o kern/98171 acpi [acpi] ACPI 1304 / 0501 errors on Acer 5024WLMi Laptop o kern/103365 acpi [acpi] acpi poweroff doesn't work with geli device att 9 problems total. From owner-freebsd-acpi@FreeBSD.ORG Mon Sep 25 13:29:42 2006 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 5E0E116A40F for ; Mon, 25 Sep 2006 13:29:42 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2CAE43D4C for ; Mon, 25 Sep 2006 13:29:41 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k8PDTTVt049901; Mon, 25 Sep 2006 08:29:29 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <4517D9B9.3080401@centtech.com> Date: Mon, 25 Sep 2006 08:29:29 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5.0.7 (X11/20060923) MIME-Version: 1.0 To: David Wolfskill References: <20060916234642.GC698@bunrab.catwhisker.org> <20060922140804.GA12665@bunrab.catwhisker.org> In-Reply-To: <20060922140804.GA12665@bunrab.catwhisker.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1942/Mon Sep 25 04:36:21 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: acpi@freebsd.org Subject: Re: Avoiding "WARNING: system temperature too high, shutting down soon!"? X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Sep 2006 13:29:42 -0000 On 09/22/06 09:08, David Wolfskill wrote: > On Sat, Sep 16, 2006 at 04:46:42PM -0700, David Wolfskill wrote: >> I could use some help: I seem to overheat my laptop; I'd like to get >> some idea of how to avoid the overheating, preferably while still >> getting the work done. >> ... > > I received several useful suggestions, and I have the problem mitigated > while I await word from places that advertise that they will do laptop > repairs. [..snip..] > Alexandre "Sunny" Kovalenko discussed the issues at some length, and > provided a patch to powerd(8) to cap the CPU frequency at or above a > certain temperature. As with the "passive cooling," I have not yet > needed that, so I haven't tested it. > > If there's interest in the patch to powerd(8), I could test it & submit > a PR -- but I'd rather not if there's not much interest. I think is interesting - it would be nice to have something like that, at least as an option to powerd. I think linux does something like this. Another thing I just thought of, was to have two debug.cpufreq.lowest settings, like debug.cpufreq.lowest.battery and debug.cpufreq.lowest.ac so that one could have a cooler quieter system while plugged in, but still get fast enough performance, yet have a lower speed setting for battery usage. If that sounds useful to others, maybe I'll write a patch. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-acpi@FreeBSD.ORG Mon Sep 25 17:43:09 2006 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 12DD616A570; Mon, 25 Sep 2006 17:43:09 +0000 (UTC) (envelope-from nate@root.org) Received: from ylpvm15.prodigy.net (ylpvm15-ext.prodigy.net [207.115.57.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 21C9043D67; Mon, 25 Sep 2006 17:43:08 +0000 (GMT) (envelope-from nate@root.org) X-ORBL: [71.139.46.150] Received: from [10.0.5.50] (ppp-71-139-46-150.dsl.snfc21.pacbell.net [71.139.46.150]) by ylpvm15.prodigy.net (8.13.8 out.dk.spool/8.13.8) with ESMTP id k8PHh68i014753; Mon, 25 Sep 2006 13:43:07 -0400 Message-ID: <45181526.3030302@root.org> Date: Mon, 25 Sep 2006 10:43:02 -0700 From: Nate Lawson User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Mark Linimon References: <200609250908.k8P98958078231@freefall.freebsd.org> In-Reply-To: <200609250908.k8P98958078231@freefall.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@FreeBSD.org, Pawel Jakub Dawidek Subject: Re: kern/103365: [acpi] acpi poweroff doesn't work with geli device attached X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Sep 2006 17:43:09 -0000 Mark Linimon wrote: > Old Synopsis: acpi poweroff doesn't work with geli device attached > New Synopsis: [acpi] acpi poweroff doesn't work with geli device attached > > http://www.freebsd.org/cgi/query-pr.cgi?pr=103365 I think this is a geli or geom bug, not acpi. It sounds like the vnode syncer gets hung up if a geom provider does not release its refcount to 0. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Mon Sep 25 17:47:31 2006 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 964C916A416 for ; Mon, 25 Sep 2006 17:47:31 +0000 (UTC) (envelope-from nate@root.org) Received: from ylpvm43.prodigy.net (ylpvm43-ext.prodigy.net [207.115.57.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F5BF43D62 for ; Mon, 25 Sep 2006 17:47:30 +0000 (GMT) (envelope-from nate@root.org) X-ORBL: [71.139.46.150] Received: from [10.0.5.50] (ppp-71-139-46-150.dsl.snfc21.pacbell.net [71.139.46.150]) by ylpvm43.prodigy.net (8.13.8 out.dk.spool/8.13.8) with ESMTP id k8PHkdL7032520; Mon, 25 Sep 2006 13:46:40 -0400 Message-ID: <451815FC.1050103@root.org> Date: Mon, 25 Sep 2006 10:46:36 -0700 From: Nate Lawson User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Eric Anderson References: <20060916234642.GC698@bunrab.catwhisker.org> <20060922140804.GA12665@bunrab.catwhisker.org> <4517D9B9.3080401@centtech.com> In-Reply-To: <4517D9B9.3080401@centtech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: acpi@freebsd.org, David Wolfskill Subject: Re: Avoiding "WARNING: system temperature too high, shutting down soon!"? X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Sep 2006 17:47:31 -0000 Eric Anderson wrote: > On 09/22/06 09:08, David Wolfskill wrote: >> On Sat, Sep 16, 2006 at 04:46:42PM -0700, David Wolfskill wrote: >>> I could use some help: I seem to overheat my laptop; I'd like to get >>> some idea of how to avoid the overheating, preferably while still >>> getting the work done. >>> ... >> >> I received several useful suggestions, and I have the problem mitigated >> while I await word from places that advertise that they will do laptop >> repairs. > > [..snip..] > >> Alexandre "Sunny" Kovalenko discussed the issues at some length, and >> provided a patch to powerd(8) to cap the CPU frequency at or above a >> certain temperature. As with the "passive cooling," I have not yet >> needed that, so I haven't tested it. >> >> If there's interest in the patch to powerd(8), I could test it & submit >> a PR -- but I'd rather not if there's not much interest. > > I think is interesting - it would be nice to have something like that, > at least as an option to powerd. I think linux does something like this. > > Another thing I just thought of, was to have two debug.cpufreq.lowest > settings, like debug.cpufreq.lowest.battery and debug.cpufreq.lowest.ac > so that one could have a cooler quieter system while plugged in, but > still get fast enough performance, yet have a lower speed setting for > battery usage. > > If that sounds useful to others, maybe I'll write a patch. Sure, if you mean implementing general profiles in powerd. You can get AC line events from devd (/var/run/devd.pipe) and then just allow a user to specify a profile associated with each setting. This could have a CPU freqs usable section, ataidle parameters, etc. If you mean implementing more profiles in the kernel, I don't think the kernel should be managing policy. It's up to userland to specify policy and the kernel to do its best to meet it (only when speed/reliability matters to the task of following the policy). -- Nate From owner-freebsd-acpi@FreeBSD.ORG Mon Sep 25 18:12:43 2006 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 D7D3116A407 for ; Mon, 25 Sep 2006 18:12:43 +0000 (UTC) (envelope-from SysAdmin@Rainbow-IT.net) Received: from venus.rainbow-it.net (venus.rainbow-it.net [212.50.178.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 94BF043D53 for ; Mon, 25 Sep 2006 18:12:42 +0000 (GMT) (envelope-from SysAdmin@Rainbow-IT.net) Received: from localhost (localhost.rainbow-it.net [127.0.0.1]) by venus.rainbow-it.net (Postfix) with ESMTP id 569811153F for ; Mon, 25 Sep 2006 19:12:38 +0100 (BST) X-Virus-Scanned: by amavisd-new, using ClamAV, at Venus.Rainbow-IT.net Received: from venus.rainbow-it.net ([127.0.0.1]) by localhost (Venus.Rainbow-IT.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dJwcNqyZddgW for ; Mon, 25 Sep 2006 19:12:35 +0100 (BST) Received: from [172.16.1.7] (82-33-97-136.cable.ubr10.azte.blueyonder.co.uk [82.33.97.136]) by venus.rainbow-it.net (Postfix) with ESMTP id 968801153E for ; Mon, 25 Sep 2006 19:12:33 +0100 (BST) Message-ID: <45181C0E.2040501@Rainbow-IT.net> Date: Mon, 25 Sep 2006 19:12:30 +0100 From: Christopher J Phillips Organization: Rainbow IT Consultancy User-Agent: Thunderbird 1.5.0.5 (X11/20060905) MIME-Version: 1.0 To: FreeBSD ACPI References: <44F8D836.2040608@Rainbow-IT.net> In-Reply-To: <44F8D836.2040608@Rainbow-IT.net> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: ACPI causing problems on acer Aspire 7100 series laptop X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Sep 2006 18:12:44 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello again, I've not been able to come up with anything that might make things better for my system, though I did wonder... Does anyone think I might be able to use some more specific entries in /boot/loader.conf that would enable me to have at least some ACPI functionality? Or, is there anything that you can suggest I can do to help myself out toward a more stable/functional ACPI system? Kind Regards, - -- ChrisP Christopher J Phillips wrote: > Hi FreeBSD-ACPI, > > I hope I'm OK to mail you with this. I'm reading > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/acpi-debug.html > and it looks like section 11.16.4 applies to me, but I'd like some > confirmation/direction from those in the know. > > I'll be trying to find out more about the problem and maybe fix it, but > here's what I've got so far (as per section 11.16.1): - > > I'm unsure of my BIOS level... > > > o Description of the buggy behavior > > This is a brand new laptop, backed up the Windoze OS and is now running > FreeBSD 6.1 STABLE > > # uname -a > FreeBSD Hathor.HQ.Rainbow-IT.net 6.1-STABLE FreeBSD 6.1-STABLE #3: Sun > Aug 27 13:59:44 BST 2006 > chrisp@hathor.hq.rainbow-it.net:/usr/src/sys/i386/compile/HATHOR i386 > > The ACPI problem was apparent immediately after install. > > The boot screen is flooded with messages like this: - > > Sep 1 11:52:14 Hathor kernel: ACPI-0501: *** Error: Handler for > [EmbeddedControl] returned AE_NO_HARDWARE_RESPONSE > Sep 1 11:52:14 Hathor kernel: ACPI-1304: *** Error: Method execution > failed [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731580), > AE_NO_HARDWARE_RESPONSE > Sep 1 11:52:14 Hathor kernel: ACPI-0239: *** Error: Method execution > failed [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731580), > AE_NO_HARDWARE_RESPONSE > Sep 1 11:52:14 Hathor kernel: ACPI-0501: *** Error: Handler for > [EmbeddedControl] returned AE_NO_HARDWARE_RESPONSE > Sep 1 11:52:14 Hathor kernel: ACPI-1304: *** Error: Method execution > failed [\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc5731680), > AE_NO_HARDWARE_RESPONSE > Sep 1 11:52:14 Hathor kernel: ACPI-1304: *** Error: Method execution > failed [\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc5731540), > AE_NO_HARDWARE_RESPONSE > Sep 1 11:52:14 Hathor kernel: ACPI-0501: *** Error: Handler for > [EmbeddedControl] returned AE_NO_HARDWARE_RESPONSE > Sep 1 11:52:14 Hathor kernel: ACPI-1304: *** Error: Method execution > failed [\_SB_.PCI0.LPCB.EC0_.GBIF] (Node 0xc57316a0), > AE_NO_HARDWARE_RESPONSE > Sep 1 11:52:14 Hathor kernel: ACPI-1304: *** Error: Method execution > failed [\_SB_.PCI0.LPCB.EC0_.BAT0._BIF] (Node 0xc5731560), > AE_NO_HARDWARE_RESPONSE > Sep 1 11:52:53 Hathor kernel: ACPI-0501: *** Error: Handler for > [EmbeddedControl] returned AE_NO_HARDWARE_RESPONSE > Sep 1 11:52:53 Hathor kernel: ACPI-1304: *** Error: Method execution > failed [\_TZ_.TZS0._TMP] (Node 0xc572d100), AE_NO_HARDWARE_RESPONSE > > and these messages continue after boot and I am not able to log in and I > do not get a prompt and can not switch to another vtty, so have to cycle > the power and boot up with ACPI disabled. > > I have temporarily added the following line to /boot/loader.conf: - > > hint.acpi.0.disabled="1" > > Instead of that I would prefer to spend some time learning how to > diagnose my problems and if at all possible, help the FreeBSD community > fix them... > > > o The dmesg(8) output after boot -v > > I have had to grab this stuff from /var/log/messages as there appears to > be too many messages and I think they're pushing the first ones out of > the dmesg buffer, before they can be recorded in /var/run/dmesg.boot. > Even when grabbing the stuff directly from the messages log itself, I > don't see the California bit anywhere, when I've booted up wth ACPI enabled. > > Sep 2 00:41:27 Hathor syslogd: kernel boot file is /boot/kernel/kernel > intpin 20 (PCI IRQ 20) to vector 54 > rl0: [MPSAFE] > cbb0: mem 0xb8003000-0xb8003fff irq 22 at device 9.0 on pci6 > cbb0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xb8003000 > cardbus0: on cbb0 > pccard0: <16-bit PCCard bus> on cbb0 > ioapic0: routing intpin 22 (PCI IRQ 22) to vector 55 > cbb0: [MPSAFE] > cbb0: PCI Configuration space: > 0x00: 0x14101524 0x02100107 0x06070001 0x00025108 > 0x10: 0xb8003000 0x020000a0 0x24070706 0xfffff000 > 0x20: 0x00000000 0xfffff000 0x00000000 0xfffffffc > 0x30: 0x00000000 0xfffffffc 0x00000000 0x07440116 > 0x40: 0x01001025 0x00000001 0x00000000 0x00000000 > 0x50: 0x00000000 0x00000000 0x00000000 0x00000000 > 0x60: 0x00000000 0x00000000 0x00000000 0x00000000 > 0x70: 0x00000000 0x00000000 0x00000000 0x00000000 > 0x80: 0x08405021 0x00000000 0x00000000 0x00001022 > 0x90: 0x604402c0 0x00000000 0x00000000 0x00000000 > 0xa0: 0xfe010001 0x00c00000 0x00008000 0x0000001f > 0xb0: 0x00000000 0x00000000 0x00000000 0x00000000 > 0xc0: 0x00001000 0x00800080 0x06080600 0x00000000 > 0xd0: 0x00000000 0x00000000 0x00000000 0x00000000 > 0xe0: 0x00000000 0x00000000 0x00000000 0x00000000 > 0xf0: 0x00000000 0x00000000 0x00000000 0x00000000 > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1810-0x181f at > device 31.2 on pci0 > atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0x1810 > atapci0: failed to enable memory mapping! > ata0: on atapci0 > atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 > atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 > ata0: reset tp1 mask=03 ostat0=50 ostat1=10 > ata0: stat0=0x90 err=0x90 lsb=0x90 msb=0x90 > ata0: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 > ata0: stat1=0x10 err=0x01 lsb=0x14 msb=0xeb > ata0: reset tp2 stat0=50 stat1=10 devices=0x9 > ioapic0: routing intpin 14 (ISA IRQ 14) to vector 56 > ata0: [MPSAFE] > ata1: on atapci0 > atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 > atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 > ata1: reset tp1 mask=03 ostat0=7f ostat1=7f > ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff > Sep 2 00:41:27 Hathor last message repeated 21 times > ata1: stat1=0x7f err=0xff lsb=0xff msb=0xff > ata1: reset tp2 stat0=ff stat1=ff devices=0x0 > ioapic0: routing intpin 15 (ISA IRQ 15) to vector 57 > ata1: [MPSAFE] > pci0: at device 31.3 (no driver attached) > acpi_tz0: on acpi0 > acpi_tz1: on acpi0 > atkbdc0: port 0x60,0x64 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > atkbd: the current kbd controller command byte 0047 > atkbd: keyboard ID 0x41ab (2) > kbd0 at atkbd0 > kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 > ioapic0: routing intpin 1 (ISA IRQ 1) to vector 58 > atkbd0: [GIANT-LOCKED] > psm0: unable to allocate IRQ > psmcpnp0: irq 12 on acpi0 > psm0: current command byte:0047 > psm0: irq 12 on atkbdc0 > ioapic0: routing intpin 12 (ISA IRQ 12) to vector 59 > psm0: [GIANT-LOCKED] > psm0: model Generic PS/2 mouse, device ID 0-00, 2 buttons > psm0: config:00000000, flags:00000008, packet size:3 > psm0: syncmask:c0, syncbits:00 > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > battery0: on acpi0 > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > acpi_acad0: on acpi0 > ata: ata0 already exists; skipping it > ata: ata1 already exists; skipping it > atkbdc: atkbdc0 already exists; skipping it > sc: sc0 already exists; skipping it > vga: vga0 already exists; skipping it > vt: vt0 already exists; skipping it > pnp_identify: Trying Read_Port at 203 > pnp_identify: Trying Read_Port at 243 > pnp_identify: Trying Read_Port at 283 > pnp_identify: Trying Read_Port at 2c3 > pnp_identify: Trying Read_Port at 303 > pnp_identify: Trying Read_Port at 343 > pnp_identify: Trying Read_Port at 383 > pnp_identify: Trying Read_Port at 3c3 > PNP Identify complete > isa_probe_children: disabling PnP devices > isa_probe_children: probing non-PnP devices > pmtimer0 on isa0 > orm0: at iomem 0xcf800-0xd07ff,0xdc000-0xdffff,0xe0000-0xe17ff on isa0 > vt0: at port 0x3b0-0x3df iomem 0-0x7fff on isa0 > vt0: generic VGA, 80 columns, color, 8 screens, unknown keyboard > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > sc0: fb0, kbd1, terminal emulator: sc (syscons terminal) > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > adv0: not probed (disabled) > aha0: not probed (disabled) > aic0: not probed (disabled) > bt0: not probed (disabled) > cs0: not probed (disabled) > ed0: not probed (disabled) > fdc0 failed to probe at port 0x3f0 irq 6 drq 2 on isa0 > fe0: not probed (disabled) > ie0: not probed (disabled) > lnc0: not probed (disabled) > ppc0 failed to probe at irq 7 on isa0 > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0: port may not be enabled > sio0: irq maps: 0x4e01 0x4e01 0x4e01 0x4e01 > sio0: probe failed test(s): 0 1 2 4 6 7 9 > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 8250 or not responding > ioapic0: routing intpin 4 (ISA IRQ 4) to vector 60 > sio1: configured irq 3 not in bitmap of probed irqs 0 > sio1: port may not be enabled > sio1: irq maps: 0x4e01 0x4e01 0x4e01 0x4e01 > sio1: probe failed test(s): 0 1 2 4 6 7 9 > sio1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0 > sio2: not probed (disabled) > sio3: not probed (disabled) > sn0: not probed (disabled) > isa_probe_children: probing PnP devices > ums0: Logitech USB-PS/2 Optical Mouse, rev 2.00/21.00, addr 2, iclass 3/1 > ums0: 8 buttons and Z dir. > uaudio0: Logitech Logitech USB Headset, rev 1.10/10.13, addr 3 > uaudio0: ignored input endpoint of type adaptive > uaudio0: audio rev 1.00 > uaudio0: 6 mixer controls > pcm0: on uaudio0 > pcm0: using a default buffer size of 16384 > uaudio0: uaudio_query_formats: found a native playback channel (stereo) > fixed frequency (5 listed formats) 16bit 2bytes/subframe X 2 channels = > 4 bytes per sample > uaudio0: uaudio_query_formats: found a native playback channel (mono) > fixed frequency (5 listed formats) 16bit 2bytes/subframe X 1 channels = > 2 bytes per sample > uaudio0: play buf 0xc58fc000 > Device configuration finished. > Reducing kern.maxvnodes 101579 -> 100000 > procfs registered > lapic: Divisor 2, Frequency 49879903 hz > Timecounter "TSC" frequency 1496402665 Hz quality 800 > Timecounters tick every 1.000 msec > lo0: bpf attached > battery0: battery initialization start > acpi_acad0: acline initialization start > ata0-slave: pio=PIO4 wdma=WDMA2 udma=UDMA33 cable=40 wire > ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=80 wire > ad0: 76319MB at ata0-master UDMA100 > ad0: 156301488 sectors [155061C/16H/63S] 16 sectors/interrupt 1 depth queue > GEOM: new disk ad0 > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed [\_TZ_.TZS0._TMP] (Node > 0xc572d0e0), AE_NO_HARDWARE_RESPONSE > acpi_tz0: error fetching current temperature -- AE_NO_HARDWARE_RESPONSE > acpi_acad0: On Line > acpi_acad0: acline initialization done, tried 1 times > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ad0: Intel check1 failed > ad0: Adaptec check1 failed > ad0: LSI (v3) check1 failed > ad0: LSI (v2) check1 failed > ad0: FreeBSD check1 failed > acd0: DVDR drive at ata0 as slave > acd0: read 8115KB/s (8115KB/s) write 172KB/s, 2048KB buffer, UDMA33 > acd0: Reads: CDR, CDRW, CDDA stream, DVDROM, DVDR, DVDRAM, packet > acd0: Writes: CDR, CDRW, DVDR, DVDRAM, test write, burnproof > acd0: Audio: play, 256 volume levels > acd0: Mechanism: ejectable tray, unlocked > acd0: Medium: 120mm data disc > ATA PseudoRAID loaded > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc5731660), AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc5731520), AE_NO_HARDWARE_RESPONSE > battery0: error fetching current battery status -- AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.GBIF] (Node 0xc5731680), AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._BIF] (Node 0xc5731540), AE_NO_HARDWARE_RESPONSE > battery0: error fetching current battery info -- AE_NO_HARDWARE_RESPONSE > Trying to mount root from ufs:/dev/ad0s1a > start_init: trying /sbin/init > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc5731660), AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc5731520), AE_NO_HARDWARE_RESPONSE > battery0: error fetching current battery status -- AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc5731660), AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc5731520), AE_NO_HARDWARE_RESPONSE > battery0: error fetching current battery status -- AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc5731660), AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc5731520), AE_NO_HARDWARE_RESPONSE > battery0: error fetching current battery status -- AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc5731660), AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc5731520), AE_NO_HARDWARE_RESPONSE > battery0: error fetching current battery status -- AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc5731520), AE_NO_HARDWARE_RESPONSE > battery0: error fetching current battery status -- AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc5731660), AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc5731520), AE_NO_HARDWARE_RESPONSE > battery0: error fetching current battery status -- AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.ADP1._PSR] (Node 0xc57314a0), AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed [\_TZ_.TZS0._TMP] (Node > 0xc572d0e0), AE_NO_HARDWARE_RESPONSE > acpi_tz0: error fetching current temperature -- AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.GBIF] (Node 0xc5731680), AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._BIF] (Node 0xc5731540), AE_NO_HARDWARE_RESPONSE > battery0: error fetching current battery info -- AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed [\_TZ_.TZS0._TMP] (Node > 0xc572d0e0), AE_NO_HARDWARE_RESPONSE > acpi_tz0: error fetching current temperature -- AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.GBIF] (Node 0xc5731680), AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._BIF] (Node 0xc5731540), AE_NO_HARDWARE_RESPONSE > battery0: error fetching current battery info -- AE_NO_HARDWARE_RESPONSE > Linux ELF exec handler installed > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > ACPI-0239: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc5731560), AE_NO_HARDWARE_RESPONSE > acpi_ec0: EcRead: Failed waiting for EC to send data. > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc5731660), AE_NO_HARDWARE_RESPONSE > ACPI-1304: *** Error: Method execution failed > [\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc5731520), AE_NO_HARDWARE_RESPONSE > battery0: error fetching current battery status -- AE_NO_HARDWARE_RESPONSE > Sep 2 00:41:31 Hathor ntpd[575]: ntpd 4.2.0-a Thu Aug 17 15:27:48 BST > 2006 (1) > splash: image decoder found: warp_saver > > > o The dmesg(8) output from boot -v with ACPI disabled > > Copyright (c) 1992-2006 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD 6.1-STABLE #3: Sun Aug 27 13:59:44 BST 2006 > chrisp@hathor.hq.rainbow-it.net:/usr/src/sys/i386/compile/HATHOR > Preloaded elf kernel "/boot/kernel/kernel" at 0xc0910000. > Preloaded elf module "/boot/kernel/splash_bmp.ko" at 0xc0910220. > Preloaded splash_image_data "/boot/modules/oemlogo.bmp" at 0xc09102d0. > Preloaded elf module "/boot/kernel/snd_uaudio.ko" at 0xc0910328. > Preloaded elf module "/boot/kernel/sound.ko" at 0xc09103d8. > Preloaded elf module "/boot/modules/bcmwl5_sys.ko" at 0xc0910484. > Preloaded elf module "/boot/kernel/ndis.ko" at 0xc0910534. > Preloaded elf module "/boot/kernel/if_ndis.ko" at 0xc09105e0. > APIC: Could not find any APICs. > Calibrating clock(s) ... i8254 clock: 1193214 Hz > CLK_USE_I8254_CALIBRATION not specified - using default frequency > Timecounter "i8254" frequency 1193182 Hz quality 0 > Calibrating TSC clock ... TSC clock: 1496404354 Hz > CPU: Intel(R) Celeron(R) M processor 1.50GHz (1496.40-MHz > 686-class CPU) > Origin = "GenuineIntel" Id = 0x6d8 Stepping = 8 > Features=0xafe9fbff > AMD Features=0x100000 > real memory = 1600651264 (1526 MB) > Physical memory chunk(s): > 0x0000000000001000 - 0x000000000009efff, 647168 bytes (158 pages) > 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) > 0x0000000000c25000 - 0x000000005db65fff, 1559498752 bytes (380737 pages) > avail memory = 1559384064 (1487 MB) > bios32: Found BIOS32 Service Directory header at 0xc00f7990 > bios32: Entry = 0xfd4b0 (c00fd4b0) Rev = 0 Len = 1 > pcibios: PCI BIOS entry at 0xfd4b0+0x25e > pnpbios: Found PnP BIOS data at 0xc00f7a10 > pnpbios: Entry = f0000:c07f Rev = 1.0 > Other BIOS signatures found: > wlan: <802.11 Link Layer> > ath_rate: version 1.2 > mem: > Pentium Pro MTRR support enabled > nfslock: pseudo-device > null: > io: > random: > VESA: information block > 56 45 53 41 00 03 00 01 00 01 01 00 00 00 40 00 > 00 01 7b 00 00 01 3d 01 00 01 4f 01 00 01 7d 01 > 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > VESA: 15 mode(s) found > VESA: v3.0, 7872k memory, flags:0x1, mode table:0xc07a5940 (1000040) > VESA: Intel(r)915GM/910ML/915MS Graphics Chip Accelerated VGA BIOS > VESA: Intel Corporation Intel(r)915GM/910ML/915MS Graphics Controller > Hardware Version 0.0 > kbd: new array size 4 > kbd1 at kbdmux0 > splash: image@0xc084a2e4, size:61614 > splash_bmp: beyond screen capacity (180x114, 16777216 colors) > splash_bmp: beyond screen capacity (180x114, 16777216 colors) > splash_bmp: beyond screen capacity (180x114, 16777216 colors) > splash_bmp: beyond screen capacity (180x114, 16777216 colors) > splash_bmp: beyond screen capacity (180x114, 16777216 colors) > splash_bmp: No appropriate video mode found > bmp_start(): splash_mode:-1 > module_register_init: MOD_LOAD (splash_bmp, 0xc08479e4, 0) error 19 > ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) > npx0: INT 16 interface > cpu0 on motherboard > pci_open(1): mode 1 addr port (0x0cf8) is 0x8000fa20 > pci_open(1a): mode1res=0x80000000 (0x80000000) > pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=25908086) > pcibios: BIOS version 2.10 > pcib0: pcibus 0 on motherboard > pci0: on pcib0 > pci0: physical bus=0 > found-> vendor=0x8086, dev=0x2590, revid=0x03 > bus=0, slot=0, func=0 > class=06-00-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0106, statreg=0x2090, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > found-> vendor=0x8086, dev=0x2592, revid=0x03 > bus=0, slot=2, func=0 > class=03-00-00, hdrtype=0x00, mfdev=1 > cmdreg=0x0003, statreg=0x0090, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > intpin=a, irq=10 > powerspec 2 supports D0 D3 current D0 > map[10]: type 1, range 32, base b0080000, size 19, enabled > map[14]: type 4, range 32, base 00001800, size 3, enabled > map[18]: type 3, range 32, base c0000000, size 28, enabled > map[1c]: type 1, range 32, base b0040000, size 18, enabled > found-> vendor=0x8086, dev=0x2792, revid=0x03 > bus=0, slot=2, func=1 > class=03-80-00, hdrtype=0x00, mfdev=1 > cmdreg=0x0000, statreg=0x0090, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > powerspec 2 supports D0 D3 current D0 > map[10]: type 1, range 32, base 00000000, size 19, memory disabled > found-> vendor=0x8086, dev=0x2668, revid=0x03 > bus=0, slot=27, func=0 > class=04-03-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0006, statreg=0x0010, cachelnsz=8 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > intpin=a, irq=10 > powerspec 2 supports D0 D3 current D0 > MSI supports 1 message, 64 bit > map[10]: type 1, range 64, base b0000000, size 14, enabled > found-> vendor=0x8086, dev=0x2660, revid=0x03 > bus=0, slot=28, func=0 > class=06-04-00, hdrtype=0x01, mfdev=1 > cmdreg=0x0007, statreg=0x0010, cachelnsz=8 (dwords) > lattimer=0x00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns) > intpin=a, irq=11 > found-> vendor=0x8086, dev=0x2658, revid=0x03 > bus=0, slot=29, func=0 > class=0c-03-00, hdrtype=0x00, mfdev=1 > cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > intpin=a, irq=11 > map[20]: type 4, range 32, base 00001820, size 5, enabled > found-> vendor=0x8086, dev=0x2659, revid=0x03 > bus=0, slot=29, func=1 > class=0c-03-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > intpin=b, irq=11 > map[20]: type 4, range 32, base 00001840, size 5, enabled > found-> vendor=0x8086, dev=0x265a, revid=0x03 > bus=0, slot=29, func=2 > class=0c-03-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > intpin=c, irq=11 > map[20]: type 4, range 32, base 00001860, size 5, enabled > found-> vendor=0x8086, dev=0x265b, revid=0x03 > bus=0, slot=29, func=3 > class=0c-03-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > intpin=d, irq=11 > map[20]: type 4, range 32, base 00001880, size 5, enabled > found-> vendor=0x8086, dev=0x265c, revid=0x03 > bus=0, slot=29, func=7 > class=0c-03-20, hdrtype=0x00, mfdev=0 > cmdreg=0x0106, statreg=0x0290, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > intpin=a, irq=11 > powerspec 2 supports D0 D3 current D0 > map[10]: type 1, range 32, base b0004000, size 10, enabled > found-> vendor=0x8086, dev=0x2448, revid=0xd3 > bus=0, slot=30, func=0 > class=06-04-01, hdrtype=0x01, mfdev=0 > cmdreg=0x0107, statreg=0x0010, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns) > found-> vendor=0x8086, dev=0x2641, revid=0x03 > bus=0, slot=31, func=0 > class=06-01-00, hdrtype=0x00, mfdev=1 > cmdreg=0x0007, statreg=0x0200, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > found-> vendor=0x8086, dev=0x2653, revid=0x03 > bus=0, slot=31, func=2 > class=01-01-80, hdrtype=0x00, mfdev=0 > cmdreg=0x0005, statreg=0x02b0, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > intpin=b, irq=255 > powerspec 2 supports D0 D3 current D0 > map[20]: type 4, range 32, base 00001810, size 4, enabled > found-> vendor=0x8086, dev=0x266a, revid=0x03 > bus=0, slot=31, func=3 > class=0c-05-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0101, statreg=0x0280, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > intpin=b, irq=11 > map[20]: type 4, range 32, base 000018c0, size 5, enabled > agp0: port 0x1800-0x1807 mem > 0xb0080000-0xb00fffff,0xc0000000-0xcfffffff,0xb0040000-0xb007ffff irq 10 > at device 2.0 on pci0 > agp0: Reserved 0x80000 bytes for rid 0x10 type 3 at 0xb0080000 > agp0: Reserved 0x80000 bytes for rid 0x10 type 3 at 0xb0080000 > agp0: Reserved 0x40000 bytes for rid 0x1c type 3 at 0xb0040000 > agp0: detected 7932k stolen memory > agp0: aperture size is 256M > pci0: at device 2.1 (no driver attached) > pci0: at device 27.0 (no driver attached) > pcib1: irq 11 at device 28.0 on pci0 > pcib1: secondary bus 2 > pcib1: subordinate bus 2 > pcib1: I/O decode 0x2000-0x2fff > pcib1: memory decode 0xb4000000-0xb7ffffff > pcib1: prefetched decode 0xd0000000-0xd3ffffff > pci2: on pcib1 > pci2: physical bus=2 > uhci0: port 0x1820-0x183f irq 11 at device 29.0 on pci0 > uhci0: Reserved 0x20 bytes for rid 0x20 type 4 at 0x1820 > uhci0: [GIANT-LOCKED] > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > uhci1: port 0x1840-0x185f irq 11 at device 29.1 on pci0 > uhci1: Reserved 0x20 bytes for rid 0x20 type 4 at 0x1840 > uhci1: [GIANT-LOCKED] > usb1: on uhci1 > usb1: USB revision 1.0 > uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub1: 2 ports with 2 removable, self powered > uhci2: port 0x1860-0x187f irq 11 at device 29.2 on pci0 > uhci2: Reserved 0x20 bytes for rid 0x20 type 4 at 0x1860 > uhci2: [GIANT-LOCKED] > usb2: on uhci2 > usb2: USB revision 1.0 > uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub2: 2 ports with 2 removable, self powered > uhci3: port 0x1880-0x189f irq 11 at device 29.3 on pci0 > uhci3: Reserved 0x20 bytes for rid 0x20 type 4 at 0x1880 > uhci3: [GIANT-LOCKED] > usb3: on uhci3 > usb3: USB revision 1.0 > uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub3: 2 ports with 2 removable, self powered > ehci0: mem 0xb0004000-0xb00043ff irq 11 at device 29.7 on pci0 > ehci0: Reserved 0x400 bytes for rid 0x10 type 3 at 0xb0004000 > ehci0: [GIANT-LOCKED] > usb4: EHCI version 1.0 > usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 > usb4: on ehci0 > usb4: USB revision 2.0 > uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 > uhub4: 8 ports with 8 removable, self powered > pcib2: at device 30.0 on pci0 > pcib2: secondary bus 6 > pcib2: subordinate bus 7 > pcib2: I/O decode 0x3000-0x3fff > pcib2: memory decode 0xb8000000-0xb80fffff > pcib2: prefetched decode 0xfff00000-0xfffff > pcib2: Subtractively decoded bridge. > pci6: on pcib2 > pci6: physical bus=6 > found-> vendor=0x14e4, dev=0x4318, revid=0x02 > bus=6, slot=5, func=0 > class=02-80-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0102, statreg=0x0000, cachelnsz=0 (dwords) > lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > intpin=a, irq=10 > map[10]: type 1, range 32, base b8000000, size 13, enabled > pcib2: (null) requested memory range 0xb8000000-0xb8001fff: good > found-> vendor=0x10ec, dev=0x8139, revid=0x10 > bus=6, slot=7, func=0 > class=02-00-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0107, statreg=0x0290, cachelnsz=0 (dwords) > lattimer=0x20 (960 ns), mingnt=0x20 (8000 ns), maxlat=0x40 (16000 ns) > intpin=a, irq=10 > powerspec 2 supports D0 D1 D2 D3 current D0 > map[10]: type 4, range 32, base 00003000, size 8, enabled > pcib2: (null) requested I/O range 0x3000-0x30ff: in range > map[14]: type 1, range 32, base b8002000, size 8, enabled > pcib2: (null) requested memory range 0xb8002000-0xb80020ff: good > found-> vendor=0x1524, dev=0x1410, revid=0x01 > bus=6, slot=9, func=0 > class=06-07-00, hdrtype=0x02, mfdev=0 > cmdreg=0x0107, statreg=0x0210, cachelnsz=8 (dwords) > lattimer=0x51 (2430 ns), mingnt=0xc4 (49000 ns), maxlat=0x07 (1750 ns) > intpin=a, irq=10 > powerspec 1 supports D0 D1 D2 D3 current D0 > map[10]: type 1, range 32, base b8003000, size 12, enabled > pcib2: (null) requested memory range 0xb8003000-0xb8003fff: good > ndis0: mem 0xb8000000-0xb8001fff irq 10 at device 5.0 on pci6 > ndis0: Reserved 0x2000 bytes for rid 0x10 type 3 at 0xb8000000 > ndis0: [MPSAFE] > ndis0: NDIS API version: 5.1 > ndis0: bpf attached > ndis0: Ethernet address: 00:16:ce:2c:6f:11 > ndis0: bpf attached > rl0: Reserved 0x100 bytes for rid 0x10 type 4 at 0x3000 > pcib2: rl0 requested I/O range 0x3000-0x30ff: in range > rl0: port 0x3000-0x30ff mem 0xb8002000-0xb80020ff irq 10 at device 7.0 > on pci6 > pcib2: rl0 requested I/O range 0x3000-0x30ff: in range > miibus0: on rl0 > rlphy0: on miibus0 > rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > rl0: bpf attached > rl0: Ethernet address: 00:0a:e4:f9:c7:85 > rl0: [MPSAFE] > cbb0: mem 0xb8003000-0xb8003fff irq 10 at device 9.0 on pci6 > cbb0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xb8003000 > cardbus0: on cbb0 > pccard0: <16-bit PCCard bus> on cbb0 > cbb0: [MPSAFE] > cbb0: PCI Configuration space: > 0x00: 0x14101524 0x02100107 0x06070001 0x00025108 > 0x10: 0xb8003000 0x020000a0 0x24070706 0xfffff000 > 0x20: 0x00000000 0xfffff000 0x00000000 0xfffffffc > 0x30: 0x00000000 0xfffffffc 0x00000000 0x0744010a > 0x40: 0x01001025 0x00000001 0x00000000 0x00000000 > 0x50: 0x00000000 0x00000000 0x00000000 0x00000000 > 0x60: 0x00000000 0x00000000 0x00000000 0x00000000 > 0x70: 0x00000000 0x00000000 0x00000000 0x00000000 > 0x80: 0x08405021 0x00000000 0x00000000 0x00001022 > 0x90: 0x604402c0 0x00000000 0x00000000 0x00000000 > 0xa0: 0xfe010001 0x00c00000 0x00008000 0x0000001f > 0xb0: 0x00000000 0x00000000 0x00000000 0x00000000 > 0xc0: 0x00001000 0x00800080 0x06080600 0x00000000 > 0xd0: 0x00000000 0x00000000 0x00000000 0x00000000 > 0xe0: 0x00000000 0x00000000 0x00000000 0x00000000 > 0xf0: 0x00000000 0x00000000 0x00000000 0x00000000 > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1810-0x181f at > device 31.2 on pci0 > atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0x1810 > atapci0: failed to enable memory mapping! > ata0: on atapci0 > atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 > atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 > ata0: reset tp1 mask=03 ostat0=50 ostat1=10 > ata0: stat0=0x90 err=0x90 lsb=0x90 msb=0x90 > ata0: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 > ata0: stat1=0x10 err=0x01 lsb=0x14 msb=0xeb > ata0: reset tp2 stat0=50 stat1=10 devices=0x9 > ata0: [MPSAFE] > ata1: on atapci0 > atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 > atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 > ata1: reset tp1 mask=03 ostat0=7f ostat1=7f > ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff > ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff > ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff > ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff > ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff > ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff > ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff > ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff > ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff > ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff > ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff > ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff > ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff > ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff > ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff > ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff > ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff > ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff > ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff > ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff > ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff > ata1: stat0=0x7f err=0xff lsb=0xff msb=0xff > ata1: stat1=0x7f err=0xff lsb=0xff msb=0xff > ata1: reset tp2 stat0=ff stat1=ff devices=0x0 > ata1: [MPSAFE] > pci0: at device 31.3 (no driver attached) > ata: ata0 already exists; skipping it > ata: ata1 already exists; skipping it > pnp_identify: Trying Read_Port at 203 > pnp_identify: Trying Read_Port at 243 > pnp_identify: Trying Read_Port at 283 > pnp_identify: Trying Read_Port at 2c3 > pnp_identify: Trying Read_Port at 303 > pnp_identify: Trying Read_Port at 343 > pnp_identify: Trying Read_Port at 383 > pnp_identify: Trying Read_Port at 3c3 > PNP Identify complete > pnpbios: 16 devices, largest 290 bytes > PNP0c02: adding io range 0x4d0-0x4d1, size=0x2, align=0x1 > PNP0c02: adding io range 0x1000-0x105f, size=0x60, align=0x1 > PNP0c02: adding io range 0x1060-0x107f, size=0x20, align=0x1 > PNP0c02: adding io range 0x1180-0x11bf, size=0x40, align=0x1 > PNP0c02: adding fixed memory32 range 0xfec10000-0xfec17fff, size=0x8000 > PNP0c02: adding fixed memory32 range 0xfec18000-0xfec1ffff, size=0x8000 > PNP0c02: adding fixed memory32 range 0xfec20000-0xfec27fff, size=0x8000 > PNP0c02: adding fixed memory32 range 0xfec28000-0xfec2ffff, size=0x8000 > PNP0c02: adding fixed memory32 range 0xfed00000-0xfed033ff, size=0x3400 > PNP0c02: adding fixed memory32 range 0xfed20000-0xfed8ffff, size=0x70000 > PNP0c02: adding fixed memory32 range 0xf0008000-0xf000bfff, size=0x4000 > pnpbios: handle 0 device ID PNP0c02 (020cd041) > PNP0c02: adding io range 0x10-0x1f, size=0x10, align=0x1 > PNP0c02: adding io range 0x24-0x25, size=0x2, align=0x1 > PNP0c02: adding io range 0x28-0x29, size=0x2, align=0x1 > PNP0c02: adding io range 0x2c-0x2d, size=0x2, align=0x1 > PNP0c02: adding io range 0x30-0x31, size=0x2, align=0x1 > PNP0c02: adding io range 0x34-0x35, size=0x2, align=0x1 > PNP0c02: adding io range 0x38-0x39, size=0x2, align=0x1 > PNP0c02: adding io range 0x3c-0x3d, size=0x2, align=0x1 > PNP0c02: adding io range 0x50-0x53, size=0x4, align=0x1 > PNP0c02: adding io range 0x62-0x62, size=0x1, align=0x1 > PNP0c02: adding io range 0x66-0x66, size=0x1, align=0x1 > PNP0c02: adding io range 0x72-0x73, size=0x2, align=0x1 > PNP0c02: adding io range 0x74-0x75, size=0x2, align=0x1 > PNP0c02: adding io range 0x76-0x77, size=0x2, align=0x1 > PNP0c02: adding io range 0x80-0x80, size=0x1, align=0x1 > PNP0c02: adding io range 0x90-0x91, size=0x2, align=0x1 > PNP0c02: adding io range 0x92-0x92, size=0x1, align=0x1 > PNP0c02: adding io range 0x93-0x9f, size=0xd, align=0x1 > PNP0c02: adding io range 0xa4-0xa5, size=0x2, align=0x1 > PNP0c02: adding io range 0xa8-0xa9, size=0x2, align=0x1 > PNP0c02: adding io range 0xac-0xad, size=0x2, align=0x1 > PNP0c02: adding io range 0xb0-0xb1, size=0x2, align=0x1 > PNP0c02: adding io range 0xb2-0xb3, size=0x2, align=0x1 > PNP0c02: adding io range 0xb4-0xb5, size=0x2, align=0x1 > PNP0c02: adding io range 0xb8-0xb9, size=0x2, align=0x1 > PNP0c02: adding io range 0xbc-0xbd, size=0x2, align=0x1 > PNP0c02: adding io range 0x1200-0x1200, size=0x1, align=0x1 > PNP0c02: adding io range 0x1204-0x1204, size=0x1, align=0x1 > PNP0c02: adding fixed memory32 range 0xe0000000-0xefffffff, size=0x10000000 > PNP0c02: adding fixed memory32 range 0xf0000000-0xf0003fff, size=0x4000 > PNP0c02: adding fixed memory32 range 0xf0004000-0xf0004fff, size=0x1000 > PNP0c02: adding fixed memory32 range 0xf0005000-0xf0005fff, size=0x1000 > pnpbios: handle 1 device ID PNP0c02 (020cd041) > PNP0c01: adding fixed memory32 range 0xe8000-0xfffff, size=0x18000 > PNP0c01: adding fixed memory32 range 0x100000-0x5f6fffff, size=0x5f600000 > pnpbios: handle 2 device ID PNP0c01 (010cd041) > PNP0200: adding io range 0-0xf, size=0x10, align=0x1 > PNP0200: adding io range 0x81-0x8f, size=0xf, align=0x1 > PNP0200: adding io range 0xc0-0xdf, size=0x20, align=0x1 > PNP0200: adding dma mask 0x10 > pnpbios: handle 3 device ID PNP0200 (0002d041) > PNP0100: adding io range 0x40-0x43, size=0x4, align=0x1 > PNP0100: adding irq mask 0x1 > pnpbios: handle 5 device ID PNP0100 (0001d041) > PNP0b00: adding io range 0x70-0x71, size=0x2, align=0x1 > PNP0b00: adding irq mask 0x100 > pnpbios: handle 6 device ID PNP0b00 (000bd041) > PNP0303: adding io range 0x60-0x60, size=0x1, align=0x1 > PNP0303: adding io range 0x64-0x64, size=0x1, align=0x1 > PNP0303: adding irq mask 0x2 > pnpbios: handle 7 device ID PNP0303 (0303d041) > PNP0c04: adding io range 0xf0-0xff, size=0x10, align=0x1 > PNP0c04: adding irq mask 0x2000 > pnpbios: handle 8 device ID PNP0c04 (040cd041) > PNP0800: adding io range 0x61-0x61, size=0x1, align=0x1 > pnpbios: handle 9 device ID PNP0800 (0008d041) > PNP0c02: adding memory32 range 0xdc000-0xdffff, size=0x4000, align=0x4000 > pnpbios: handle 10 device ID PNP0c02 (020cd041) > PNP0a03: adding io range 0xcf8-0xcff, size=0x8, align=0x1 > pnpbios: handle 11 device ID PNP0a03 (030ad041) > INT0800: adding fixed memory32 range 0xff000000-0xffffffff, size=0x1000000 > pnpbios: handle 12 device ID INT0800 (0008d425) > PNP0c02: adding fixed memory32 range 0xcf200-0xcf7ff, size=0x600 > PNP0c02: adding fixed memory32 range 0xd0800-0xd3fff, size=0x3800 > pnpbios: handle 13 device ID PNP0c02 (020cd041) > PNP0c02: adding memory32 range 0xe0000-0xe17ff, size=0x1800, align=0x1800 > pnpbios: handle 14 device ID PNP0c02 (020cd041) > PNP0f13: adding irq mask 0x1000 > pnpbios: handle 15 device ID PNP0f13 (130fd041) > vt: vt0 already exists; skipping it > sc: sc0 already exists; skipping it > vga: vga0 already exists; skipping it > isa_probe_children: disabling PnP devices > isa_probe_children: probing non-PnP devices > pmtimer0 on isa0 > orm0: at iomem 0xcf800-0xd07ff,0xdc000-0xdffff,0xe0000-0xe17ff on isa0 > adv0: not probed (disabled) > aha0: not probed (disabled) > aic0: not probed (disabled) > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: irq 1 on atkbdc0 > atkbd: the current kbd controller command byte 0047 > atkbd: keyboard ID 0x41ab (2) > kbd0 at atkbd0 > kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 > atkbd0: [GIANT-LOCKED] > psm0: current command byte:0047 > psm0: irq 12 on atkbdc0 > psm0: [GIANT-LOCKED] > psm0: model Generic PS/2 mouse, device ID 0-00, 2 buttons > psm0: config:00000000, flags:00000008, packet size:3 > psm0: syncmask:c0, syncbits:00 > bt0: not probed (disabled) > cs0: not probed (disabled) > ed0: not probed (disabled) > fdc0 failed to probe at port 0x3f0 irq 6 drq 2 on isa0 > fe0: not probed (disabled) > ie0: not probed (disabled) > lnc0: not probed (disabled) > ppc0 failed to probe at irq 7 on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > sc0: fb0, kbd1, terminal emulator: sc (syscons terminal) > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0: port may not be enabled > sio0: irq maps: 0x801 0x801 0x801 0x801 > sio0: probe failed test(s): 0 1 2 4 6 7 9 > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 8250 or not responding > sio1: configured irq 3 not in bitmap of probed irqs 0 > sio1: port may not be enabled > sio1: irq maps: 0x801 0x801 0x801 0x801 > sio1: probe failed test(s): 0 1 2 4 6 7 9 > sio1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0 > sio2: not probed (disabled) > sio3: not probed (disabled) > sn0: not probed (disabled) > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > vt0: not probed (disabled) > isa_probe_children: probing PnP devices > unknown: can't assign resources (port) > unknown: at port 0x60 on isa0 > unknown: failed to probe at port 0x61 on isa0 > unknown: can't assign resources (memory) > unknown: at iomem 0xdc000-0xdffff on isa0 > unknown: can't assign resources (memory) > unknown: on isa0 > unknown: can't assign resources (memory) > unknown: at iomem 0xe0000-0xe17ff on isa0 > unknown: can't assign resources (irq) > unknown: at irq 12 on isa0 > ums0: Logitech USB-PS/2 Optical Mouse, rev 2.00/21.00, addr 2, iclass 3/1 > ums0: 8 buttons and Z dir. > uaudio0: Logitech Logitech USB Headset, rev 1.10/10.13, addr 3 > uaudio0: ignored input endpoint of type adaptive > uaudio0: audio rev 1.00 > uaudio0: 6 mixer controls > pcm0: on uaudio0 > pcm0: using a default buffer size of 16384 > uaudio0: uaudio_query_formats: found a native playback channel (stereo) > fixed frequency (5 listed formats) 16bit 2bytes/subframe X 2 channels = > 4 bytes per sample > uaudio0: uaudio_query_formats: found a native playback channel (mono) > fixed frequency (5 listed formats) 16bit 2bytes/subframe X 1 channels = > 2 bytes per sample > uaudio0: play buf 0xc5857000 > Device configuration finished. > Reducing kern.maxvnodes 101579 -> 100000 > procfs registered > Timecounter "TSC" frequency 1496404354 Hz quality 800 > Timecounters tick every 1.000 msec > lo0: bpf attached > ata0-slave: pio=PIO4 wdma=WDMA2 udma=UDMA33 cable=40 wire > ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=80 wire > ad0: 76319MB at ata0-master UDMA100 > ad0: 156301488 sectors [155061C/16H/63S] 16 sectors/interrupt 1 depth queue > GEOM: new disk ad0 > ad0: Intel check1 failed > ad0: Adaptec check1 failed > ad0: LSI (v3) check1 failed > ad0: LSI (v2) check1 failed > ad0: FreeBSD check1 failed > acd0: DVDR drive at ata0 as slave > acd0: read 8115KB/s (8115KB/s) write 172KB/s, 2048KB buffer, UDMA33 > acd0: Reads: CDR, CDRW, CDDA stream, DVDROM, DVDR, DVDRAM, packet > acd0: Writes: CDR, CDRW, DVDR, DVDRAM, test write, burnproof > acd0: Audio: play, 256 volume levels > acd0: Mechanism: ejectable tray, unlocked > acd0: Medium: 120mm data disc > ATA PseudoRAID loaded > Trying to mount root from ufs:/dev/ad0s1a > start_init: trying /sbin/init > Linux ELF exec handler installed > > > o Output from sysctl hw.acpi > > # sysctl hw.acpi > sysctl: unknown oid 'hw.acpi' > > > o URL where my ASL can be found > > http://rainbow-it.net/chrisp-acerAspire7103WSMi.asl > > > o Additionally, I've attempted to re-compile my ASL - output below > > # iasl chrisp-acerAspire7103WSMi.asl > > Intel ACPI Component Architecture > ASL Optimizing Compiler / AML Disassembler version 20041119 [Aug 17 2006] > Copyright (C) 2000 - 2004 Intel Corporation > Supports ACPI Specification Revision 2.0c > > chrisp-acerAspire7103WSMi.asl 504: Method (_WAK, 1, NotSerialized) > Warning 2026 - Reserved method must return a value ^ (_WAK) > > chrisp-acerAspire7103WSMi.asl 929: Name (_HID, "*pnp0c14") > Error 1068 - String must be entirely alphanumeric ^ > (*pnp0c14) > > chrisp-acerAspire7103WSMi.asl 946: Name (_WDG, Buffer (0xDC) > Warning 2033 - Unknown reserved name ^ (_WDG) > > chrisp-acerAspire7103WSMi.asl 977: Method (_WED, 1, > NotSerialized) > Warning 2019 - Not all control paths return a value ^ (_WED) > > chrisp-acerAspire7103WSMi.asl 977: Method (_WED, 1, > NotSerialized) > Warning 2033 - Unknown reserved name ^ (_WED) > > chrisp-acerAspire7103WSMi.asl 1267: Method (WMCA, 3, > NotSerialized) > Warning 2019 - Not all control paths return a value ^ (WMCA) > > chrisp-acerAspire7103WSMi.asl 1369: Method (WMCB, 3, > NotSerialized) > Warning 2019 - Not all control paths return a value ^ (WMCB) > > chrisp-acerAspire7103WSMi.asl 1418: Method (WMCE, 3, > NotSerialized) > Warning 2019 - Not all control paths return a value ^ (WMCE) > > chrisp-acerAspire7103WSMi.asl 3708: Field (RAM, > AnyAcc, Lock, Preserve) > Error 1048 - Host Operation Region requires ByteAcc access ^ > > chrisp-acerAspire7103WSMi.asl 3732: Field (RAM, > AnyAcc, Lock, Preserve) > Error 1048 - Host Operation Region requires ByteAcc access ^ > > chrisp-acerAspire7103WSMi.asl 3759: Field (RAM, > AnyAcc, Lock, Preserve) > Error 1048 - Host Operation Region requires ByteAcc access ^ > > chrisp-acerAspire7103WSMi.asl 3765: Field (RAM, > AnyAcc, Lock, Preserve) > Error 1048 - Host Operation Region requires ByteAcc access ^ > > chrisp-acerAspire7103WSMi.asl 3771: Field (RAM, > AnyAcc, Lock, Preserve) > Error 1048 - Host Operation Region requires ByteAcc access ^ > > ASL Input: chrisp-acerAspire7103WSMi.asl - 6274 lines, 205163 bytes, > 2820 keywords > Compilation complete. 6 Errors, 7 Warnings, 0 Remarks, 622 Optimizations > > > Does this look like I could do something to help myself out? > > Cheers, > -- > > ChrisP > _______________________________________________ > 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" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFGBwO7z/iRu7PdWERApBHAKDGj5L8VdoklMVUSdcWn/zEIy7JyQCdFlHs SgaekiwG5W15A9IE/sZjKmM= =9n8L -----END PGP SIGNATURE----- From owner-freebsd-acpi@FreeBSD.ORG Tue Sep 26 12:18:06 2006 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 544F116A415 for ; Tue, 26 Sep 2006 12:18:06 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from gaia.nimnet.asn.au (nimbin.lnk.telstra.net [139.130.45.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35C3443D6E for ; Tue, 26 Sep 2006 12:18:02 +0000 (GMT) (envelope-from smithi@nimnet.asn.au) Received: from localhost (smithi@localhost) by gaia.nimnet.asn.au (8.8.8/8.8.8R1.4) with SMTP id WAA14996; Tue, 26 Sep 2006 22:17:43 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Tue, 26 Sep 2006 22:17:42 +1000 (EST) From: Ian Smith To: Nate Lawson In-Reply-To: <451815FC.1050103@root.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: acpi@freebsd.org, David Wolfskill Subject: Re: Avoiding "WARNING: system temperature too high, shutting down soon!"? X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Sep 2006 12:18:06 -0000 Hi Nate and crew, I'm an ACPI newbie, though I've been keeping an eye on it these 4 years while using a Compaq Armada 1500c that does APM very well, and have just installed 6.1-R on a Thinkpad T23 in good condition, a model chosen in the end due to your message on FLCL saying suspend/resume worked w/ACPI. So from a low base I've been climbing the curve on possibilities with - and trying to understand interactions between - powerd, power_profile, acpi_ibm, acpi_thermal etc, looking towards minimum power consumption with responsiveness on demand, both on battery in the field and on 'AC' which is here supplied by battery from solar-only power anyway, with a computing budget not exceeding 60 Ah/day on average, and that with the old 1500c running 24/7 headless as a server at approx 24 Ah/day. On Mon, 25 Sep 2006, Nate Lawson wrote: > Eric Anderson wrote: > > On 09/22/06 09:08, David Wolfskill wrote: > >> On Sat, Sep 16, 2006 at 04:46:42PM -0700, David Wolfskill wrote: > >>> I could use some help: I seem to overheat my laptop; I'd like to get > >>> some idea of how to avoid the overheating, preferably while still > >>> getting the work done. > >>> ... > >> > >> I received several useful suggestions, and I have the problem mitigated > >> while I await word from places that advertise that they will do laptop > >> repairs. > > > > [..snip..] > > > >> Alexandre "Sunny" Kovalenko discussed the issues at some length, and > >> provided a patch to powerd(8) to cap the CPU frequency at or above a > >> certain temperature. As with the "passive cooling," I have not yet > >> needed that, so I haven't tested it. > >> > >> If there's interest in the patch to powerd(8), I could test it & submit > >> a PR -- but I'd rather not if there's not much interest. One more hand up for interest, David, for even a pointer to the patch. > > I think is interesting - it would be nice to have something like that, > > at least as an option to powerd. I think linux does something like this. What I've noticed so far is that powerd works great here with default values for adaptive speed shifting, but doesn't do anything with CX states like power_profile, which in turn seems to require settings of "NONE" for {performance,economy}_cpu_freq to not mess with powerd. I've yet to explore acpi_thermal settings beyond watching with sysctl, but powerd being able to respond to _PSV, _HOT and _CRT notifications sounds like a really good integrated idea. [As an aside, on machines with no working S4, it'd be 'cool' if "hw.acpi.thermal.tz%d._HOT Temperature to start critical suspend to disk (S4)." could use S3 instead, before a big S5 lose-all-your-work _CRT shutdown?] > > Another thing I just thought of, was to have two debug.cpufreq.lowest > > settings, like debug.cpufreq.lowest.battery and debug.cpufreq.lowest.ac > > so that one could have a cooler quieter system while plugged in, but > > still get fast enough performance, yet have a lower speed setting for > > battery usage. > > > > If that sounds useful to others, maybe I'll write a patch. > > Sure, if you mean implementing general profiles in powerd. You can get > AC line events from devd (/var/run/devd.pipe) and then just allow a user Do you mean instead of polling ACPI or APM states as in powerd.c now? I see advantages with maintaining ability to work with APM, or will acpi now simulate APM notifications such as line state and battery events? > to specify a profile associated with each setting. This could have a > CPU freqs usable section, ataidle parameters, etc. CX states too, maybe? I expect to be playing with ataidle soon, and hope to get blanking to switch LCD off (good power savings) as it does on the 1500c with apm_saver (which won't run under acpi). My T23 has ancient BIOS + EC and I've neither a USB floppy nor windows installed, so I have to figure out how to upgrade those before really seeing what this beastie can do; currently getting a bunch of ACPI-0356 and -1304 errors/warnings in dmesg, though most things seem to work fine anyway. Anyway hello, I'll likely bothering you guys a bit for a while .. Cheers, Ian > If you mean implementing more profiles in the kernel, I don't think the > kernel should be managing policy. It's up to userland to specify policy > and the kernel to do its best to meet it (only when speed/reliability > matters to the task of following the policy). > > -- > Nate From owner-freebsd-acpi@FreeBSD.ORG Thu Sep 28 14:34:53 2006 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 43B5716A40F for ; Thu, 28 Sep 2006 14:34:53 +0000 (UTC) (envelope-from pvizeli@yahoo.de) Received: from web27806.mail.ukl.yahoo.com (web27806.mail.ukl.yahoo.com [217.146.182.11]) by mx1.FreeBSD.org (Postfix) with SMTP id 0BBE643D70 for ; Thu, 28 Sep 2006 14:34:51 +0000 (GMT) (envelope-from pvizeli@yahoo.de) Received: (qmail 62647 invoked by uid 60001); 28 Sep 2006 14:34:50 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.de; h=Message-ID:Received:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=fg0aVxMnCOutfHipIEdhzlU6k7cSXCNFxnDDmzeHZmPEOeB3f6k+eMDuNhgZ89cU7yuJ+S1DnW8LTtQCVIG3H7lOMDM2BKyHdIvkqCQ09TD9nHfH/n+53YOF3eh6QnOtL+4lpM+gq+LzJJAj5eUUVXZ/yQFgWEVIaxUKGMR1GaY= ; Message-ID: <20060928143450.62645.qmail@web27806.mail.ukl.yahoo.com> Received: from [213.213.171.12] by web27806.mail.ukl.yahoo.com via HTTP; Thu, 28 Sep 2006 14:34:50 GMT Date: Thu, 28 Sep 2006 14:34:50 +0000 (GMT) From: Vizeli Pascal To: freebsd-acpi@freebsd.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="0-1560165627-1159454090=:59546" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Acer Aspire 3620 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Vizeli Pascal List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Sep 2006 14:34:53 -0000 --0-1560165627-1159454090=:59546 Content-Type: text/plain; charset=us-ascii Hello, I have problems with Apsire 3620 ACPI. ARCH: i386 OS: FreeBSD 6.1 KERNEL MODUL ACPI: current (I have update with cvsup an recompile the acpi moduls) BIOS VERSION: 1.06 Problem: You can show on dmesg, 1) Mousepad doesn't work 2) Wlan und Bluetooth also doesn't work I send a acpidump with bios version 1.04 and the new one (1.06) with diff. A dmesg with acpi and without acpi is aktive. What I do? How I can update that? --0-1560165627-1159454090=:59546-- From owner-freebsd-acpi@FreeBSD.ORG Thu Sep 28 14:41:16 2006 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 ADAA416A40F for ; Thu, 28 Sep 2006 14:41:16 +0000 (UTC) (envelope-from pvizeli@yahoo.de) Received: from web27802.mail.ukl.yahoo.com (web27802.mail.ukl.yahoo.com [217.146.182.7]) by mx1.FreeBSD.org (Postfix) with SMTP id 1B4E743D92 for ; Thu, 28 Sep 2006 14:41:10 +0000 (GMT) (envelope-from pvizeli@yahoo.de) Received: (qmail 51752 invoked by uid 60001); 28 Sep 2006 14:41:09 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.de; h=Message-ID:Received:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=yZmSEEXoffu4h1DPfcKwrf40WRHE82ha5CJC1YX0DJZ4CX/hlM5n1bYakXt2t++lTNDrGt92zHFU7bP8QQEkXmK5VqJD5ooLh7/C27ZgyPNkpxXgvbTpasMaTp1064+5cQTc5WbYsRONzDjjkGMWwJ8oJDWx98om1pBD/yjVcIo= ; Message-ID: <20060928144109.51750.qmail@web27802.mail.ukl.yahoo.com> Received: from [213.213.171.12] by web27802.mail.ukl.yahoo.com via HTTP; Thu, 28 Sep 2006 14:41:09 GMT Date: Thu, 28 Sep 2006 14:41:09 +0000 (GMT) From: Vizeli Pascal To: freebsd-acpi@freebsd.org In-Reply-To: <20060928143450.62645.qmail@web27806.mail.ukl.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Subject: AW: Acer Aspire 3620 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Vizeli Pascal List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Sep 2006 14:41:16 -0000 Oh, I have forget that file... sorry ----- Urspr=FCngliche Mail ---- Von: Vizeli Pascal An: freebsd-acpi@freebsd.org Gesendet: Donnerstag, den 28. September 2006, 16:34:50 Uhr Betreff: Acer Aspire 3620 Hello, I have problems with Apsire 3620 ACPI. ARCH: i386 OS: FreeBSD 6.1 KERNEL MODUL ACPI: current (I have update with cvsup an recompile the acpi = moduls) BIOS VERSION: 1.06 Problem: You can show on dmesg, 1) Mousepad doesn't work 2) Wlan und Bluetooth also doesn't work I send a acpidump with bios version 1.04 and the new one (1.06) with diff. A dmesg with acpi and without acpi is aktive. What I do? How I can update that? _______________________________________________ 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 Thu Sep 28 14:44:33 2006 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 3EC6016A4CE for ; Thu, 28 Sep 2006 14:44:33 +0000 (UTC) (envelope-from pvizeli@yahoo.de) Received: from web27812.mail.ukl.yahoo.com (web27812.mail.ukl.yahoo.com [217.146.182.17]) by mx1.FreeBSD.org (Postfix) with SMTP id 830B343D88 for ; Thu, 28 Sep 2006 14:43:58 +0000 (GMT) (envelope-from pvizeli@yahoo.de) Received: (qmail 78037 invoked by uid 60001); 28 Sep 2006 14:43:55 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.de; h=Message-ID:Received:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=uG3YZhgeAYF0PcgZqKyX6RAusX/HxgEer5vWJHZIJHpghuorQb7BEuzAhFWJpjqgXJ1kQ+22iSeMtNaZX7RN4A+9gTUOThKZ0nigVU2rdlqAtjx7Q3ELRoOqEl00Hzyt0kLP0Adj7zgLFjW1TB9F+Ngi8IJ5N9yJqVMZMyRxYwc= ; Message-ID: <20060928144355.78035.qmail@web27812.mail.ukl.yahoo.com> Received: from [213.213.171.12] by web27812.mail.ukl.yahoo.com via HTTP; Thu, 28 Sep 2006 14:43:55 GMT Date: Thu, 28 Sep 2006 14:43:55 +0000 (GMT) From: Vizeli Pascal To: Vizeli Pascal , freebsd-acpi@freebsd.org In-Reply-To: <20060928144109.51750.qmail@web27802.mail.ukl.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="0-1630914340-1159454635=:76314" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: AW: Acer Aspire 3620 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Vizeli Pascal List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Sep 2006 14:44:33 -0000 --0-1630914340-1159454635=:76314 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable so :) my mailprogram had problems... I send the sysctl log. ----- Urspr=FCngliche Mail ---- Von: Vizeli Pascal An: freebsd-acpi@freebsd.org Gesendet: Donnerstag, den 28. September 2006, 16:41:09 Uhr Betreff: AW: Acer Aspire 3620 Oh, I have forget that file... sorry ----- Urspr=FCngliche Mail ---- Von: Vizeli Pascal An: freebsd-acpi@freebsd.org Gesendet: Donnerstag, den 28. September 2006, 16:34:50 Uhr Betreff: Acer Aspire 3620 Hello, I have problems with Apsire 3620 ACPI. ARCH: i386 OS: FreeBSD 6.1 KERNEL MODUL ACPI: current (I have update with cvsup an recompile the acpi = moduls) BIOS VERSION: 1.06 Problem: You can show on dmesg, 1) Mousepad doesn't work 2) Wlan und Bluetooth also doesn't work I send a acpidump with bios version 1.04 and the new one (1.06) with diff. A dmesg with acpi and without acpi is aktive. What I do? How I can update that? _______________________________________________ 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" _______________________________________________ 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" --0-1630914340-1159454635=:76314-- From owner-freebsd-acpi@FreeBSD.ORG Fri Sep 29 12:46:15 2006 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 7AA6E16A403 for ; Fri, 29 Sep 2006 12:46:15 +0000 (UTC) (envelope-from ducrot@poupinou.org) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0718643D4C for ; Fri, 29 Sep 2006 12:46:15 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1GTHkq-0006MI-00; Fri, 29 Sep 2006 14:46:12 +0200 Date: Fri, 29 Sep 2006 14:46:12 +0200 To: Vizeli Pascal Message-ID: <20060929124612.GC4945@poupinou.org> References: <20060928144109.51750.qmail@web27802.mail.ukl.yahoo.com> <20060928144355.78035.qmail@web27812.mail.ukl.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060928144355.78035.qmail@web27812.mail.ukl.yahoo.com> User-Agent: Mutt/1.5.9i From: Bruno Ducrot Cc: freebsd-acpi@freebsd.org Subject: Re: Acer Aspire 3620 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Sep 2006 12:46:15 -0000 I just uploaded the files Pascal send to me here: http://www.poupinou.org/acer-aspire3620/ if someone want to take a look at them. On Thu, Sep 28, 2006 at 02:43:55PM +0000, Vizeli Pascal wrote: > so :) > my mailprogram had problems... > I send the sysctl log. > > ----- Urspr?ngliche Mail ---- > Von: Vizeli Pascal > An: freebsd-acpi@freebsd.org > Gesendet: Donnerstag, den 28. September 2006, 16:41:09 Uhr > Betreff: AW: Acer Aspire 3620 > > Oh, I have forget that file... sorry > > ----- Urspr?ngliche Mail ---- > Von: Vizeli Pascal > An: freebsd-acpi@freebsd.org > Gesendet: Donnerstag, den 28. September 2006, 16:34:50 Uhr > Betreff: Acer Aspire 3620 > > Hello, > > I have problems with Apsire 3620 ACPI. > > ARCH: i386 > OS: FreeBSD 6.1 > KERNEL MODUL ACPI: current (I have update with cvsup an recompile the acpi moduls) > BIOS VERSION: 1.06 > > Problem: > You can show on dmesg, > 1) Mousepad doesn't work > 2) Wlan und Bluetooth also doesn't work > > I send a acpidump with bios version 1.04 and the new one (1.06) with diff. > A dmesg with acpi and without acpi is aktive. > > What I do? > How I can update that? > > > _______________________________________________ > 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" > > > > _______________________________________________ > 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" > > > _______________________________________________ > 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" -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care. From owner-freebsd-acpi@FreeBSD.ORG Fri Sep 29 13:44:54 2006 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 B660F16A492 for ; Fri, 29 Sep 2006 13:44:54 +0000 (UTC) (envelope-from pvizeli@yahoo.de) Received: from web27814.mail.ukl.yahoo.com (web27814.mail.ukl.yahoo.com [217.146.182.19]) by mx1.FreeBSD.org (Postfix) with SMTP id C772F43E2E for ; Fri, 29 Sep 2006 13:38:02 +0000 (GMT) (envelope-from pvizeli@yahoo.de) Received: (qmail 78187 invoked by uid 60001); 29 Sep 2006 13:37:47 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.de; h=Message-ID:Received:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=AR57MkiOFczQgIUg7Ygmq3kiA+9p9+rOwReL2MLGuGf22cl79oztssz4cWnZMdc3grzWeN3jJo8bmoc2RZx4Q4fG7gH7PE6Vy2fWQZ01Hi/hm/UEaldMZi9/NStbrPhl3xiXC0ZTEZWe4oaD3AfHGrcI3o68fRd7qqI3e1TxRNg= ; Message-ID: <20060929133747.78185.qmail@web27814.mail.ukl.yahoo.com> Received: from [213.213.171.7] by web27814.mail.ukl.yahoo.com via HTTP; Fri, 29 Sep 2006 13:37:47 GMT Date: Fri, 29 Sep 2006 13:37:47 +0000 (GMT) From: Vizeli Pascal To: Bruno Ducrot In-Reply-To: <20060929124612.GC4945@poupinou.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-acpi@freebsd.org Subject: AW: Acer Aspire 3620 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Vizeli Pascal List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Sep 2006 13:44:54 -0000 The manual from Aspire 3620 write: "ACPI 1.0b" greet, pascal ----- Urspr=FCngliche Mail ---- Von: Bruno Ducrot An: Vizeli Pascal CC: freebsd-acpi@freebsd.org Gesendet: Freitag, den 29. September 2006, 14:46:12 Uhr Betreff: Re: Acer Aspire 3620 I just uploaded the files Pascal send to me here: http://www.poupinou.org/acer-aspire3620/ if someone want to take a look at them. On Thu, Sep 28, 2006 at 02:43:55PM +0000, Vizeli Pascal wrote: > so :) > my mailprogram had problems... > I send the sysctl log. >=20 > ----- Urspr?ngliche Mail ---- > Von: Vizeli Pascal > An: freebsd-acpi@freebsd.org > Gesendet: Donnerstag, den 28. September 2006, 16:41:09 Uhr > Betreff: AW: Acer Aspire 3620 >=20 > Oh, I have forget that file... sorry >=20 > ----- Urspr?ngliche Mail ---- > Von: Vizeli Pascal > An: freebsd-acpi@freebsd.org > Gesendet: Donnerstag, den 28. September 2006, 16:34:50 Uhr > Betreff: Acer Aspire 3620 >=20 > Hello, >=20 > I have problems with Apsire 3620 ACPI. >=20 > ARCH: i386 > OS: FreeBSD 6.1 > KERNEL MODUL ACPI: current (I have update with cvsup an recompile the acp= i moduls) > BIOS VERSION: 1.06 >=20 > Problem: > You can show on dmesg, > 1) Mousepad doesn't work > 2) Wlan und Bluetooth also doesn't work >=20 > I send a acpidump with bios version 1.04 and the new one (1.06) with diff= . > A dmesg with acpi and without acpi is aktive. >=20 > What I do? > How I can update that? >=20 >=20 > _______________________________________________ > 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" >=20 >=20 >=20 > _______________________________________________ > 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" >=20 >=20 > _______________________________________________ > 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" --=20 Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care. From owner-freebsd-acpi@FreeBSD.ORG Fri Sep 29 15:17:22 2006 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 A3CD816A47B for ; Fri, 29 Sep 2006 15:17:22 +0000 (UTC) (envelope-from ducrot@poupinou.org) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id EDB5443D49 for ; Fri, 29 Sep 2006 15:17:07 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1GTK6q-0006bd-00; Fri, 29 Sep 2006 17:17:04 +0200 Date: Fri, 29 Sep 2006 17:17:04 +0200 To: Vizeli Pascal Message-ID: <20060929151704.GD4945@poupinou.org> References: <20060929124612.GC4945@poupinou.org> <20060929133747.78185.qmail@web27814.mail.ukl.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060929133747.78185.qmail@web27814.mail.ukl.yahoo.com> User-Agent: Mutt/1.5.9i From: Bruno Ducrot Cc: freebsd-acpi@freebsd.org Subject: Re: Acer Aspire 3620 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Sep 2006 15:17:22 -0000 On Fri, Sep 29, 2006 at 01:37:47PM +0000, Vizeli Pascal wrote: > The manual from Aspire 3620 write: "ACPI 1.0b" > > greet, > pascal > > ----- Urspr?ngliche Mail ---- > Von: Bruno Ducrot > An: Vizeli Pascal > CC: freebsd-acpi@freebsd.org > Gesendet: Freitag, den 29. September 2006, 14:46:12 Uhr > Betreff: Re: Acer Aspire 3620 > > I just uploaded the files Pascal send to me here: > http://www.poupinou.org/acer-aspire3620/ > if someone want to take a look at them. > > On Thu, Sep 28, 2006 at 02:43:55PM +0000, Vizeli Pascal wrote: > > so :) > > my mailprogram had problems... > > I send the sysctl log. > > > > ----- Urspr?ngliche Mail ---- > > Von: Vizeli Pascal > > An: freebsd-acpi@freebsd.org > > Gesendet: Donnerstag, den 28. September 2006, 16:41:09 Uhr > > Betreff: AW: Acer Aspire 3620 > > > > Oh, I have forget that file... sorry > > > > ----- Urspr?ngliche Mail ---- > > Von: Vizeli Pascal > > An: freebsd-acpi@freebsd.org > > Gesendet: Donnerstag, den 28. September 2006, 16:34:50 Uhr > > Betreff: Acer Aspire 3620 > > > > Hello, > > > > I have problems with Apsire 3620 ACPI. > > > > ARCH: i386 > > OS: FreeBSD 6.1 > > KERNEL MODUL ACPI: current (I have update with cvsup an recompile the acpi moduls) > > BIOS VERSION: 1.06 > > > > Problem: > > You can show on dmesg, > > 1) Mousepad doesn't work > > 2) Wlan und Bluetooth also doesn't work > > > > I send a acpidump with bios version 1.04 and the new one (1.06) with diff. > > A dmesg with acpi and without acpi is aktive. > > > > What I do? > > How I can update that? > > > > I'm a little bit annoyed by those errors: ACPI-0501: *** Error: Handler for [EmbeddedControl] returned AE_NO_HARDWARE_RESPONSE ACPI-1304: *** Error: Method execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc325fbc0), AE_NO_HARDWARE_RESPONSE ACPI-1304: *** Error: Method execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc325fa80), AE_NO_HARDWARE_RESPONSE I think this will break support for battery and maybe thermal zone and likely other stuff (though I'm not sure exacly what). -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care. From owner-freebsd-acpi@FreeBSD.ORG Fri Sep 29 15:45:48 2006 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 0C87516A416 for ; Fri, 29 Sep 2006 15:45:48 +0000 (UTC) (envelope-from ariff@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 26DF143D6D; Fri, 29 Sep 2006 15:45:47 +0000 (GMT) (envelope-from ariff@FreeBSD.org) Received: from misaki (root@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with SMTP id k8TFjiGD098018; Fri, 29 Sep 2006 15:45:45 GMT (envelope-from ariff@FreeBSD.org) Date: Fri, 29 Sep 2006 23:44:07 +0800 From: Ariff Abdullah To: Bruno Ducrot Message-Id: <20060929234407.7d41e633.ariff@FreeBSD.org> In-Reply-To: <20060929151704.GD4945@poupinou.org> References: <20060929124612.GC4945@poupinou.org> <20060929133747.78185.qmail@web27814.mail.ukl.yahoo.com> <20060929151704.GD4945@poupinou.org> Organization: FreeBSD X-Mailer: /usr/local/lib/ruby/1.8/net/smtp.rb Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA1"; boundary="Signature=_Fri__29_Sep_2006_23_44_07_+0800_+oF1X7EpVPKfezfm" Cc: freebsd-acpi@FreeBSD.org Subject: Re: Acer Aspire 3620 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Sep 2006 15:45:48 -0000 --Signature=_Fri__29_Sep_2006_23_44_07_+0800_+oF1X7EpVPKfezfm Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, 29 Sep 2006 17:17:04 +0200 Bruno Ducrot wrote: >=20 > I'm a little bit annoyed by those errors: >=20 > ACPI-0501: *** Error: Handler for [EmbeddedControl] returned > AE_NO_HARDWARE_RESPONSE ACPI-1304: *** Error: Method execution > failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc325fbc0), > AE_NO_HARDWARE_RESPONSE ACPI-1304: *** Error: Method execution > failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc325fa80), > AE_NO_HARDWARE_RESPONSE >=20 > I think this will break support for battery and maybe thermal zone > and likely other stuff (though I'm not sure exacly what). >=20 >=20 I guess kern/98171 is worth an attention. That at least fix my problem on Compaq V3000. -- Ariff Abdullah FreeBSD ... Recording in stereo is obviously too advanced and confusing for us idiot ***** users :P ........ --Signature=_Fri__29_Sep_2006_23_44_07_+0800_+oF1X7EpVPKfezfm Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFHT9Jlr+deMUwTNoRArk2AJ9duQ4iHBsdoiw6PuKVR6Mc59nelACfZ9Mg ABe5KzyL1W/jirnCKkpZAmA= =Z1D2 -----END PGP SIGNATURE----- --Signature=_Fri__29_Sep_2006_23_44_07_+0800_+oF1X7EpVPKfezfm-- From owner-freebsd-acpi@FreeBSD.ORG Sat Sep 30 12:34:31 2006 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 5CB9A16A706 for ; Sat, 30 Sep 2006 12:34:31 +0000 (UTC) (envelope-from matteo@freebsd.org) Received: from vsmtp1.tin.it (vsmtp1.tin.it [212.216.176.141]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CFCA43D6B for ; Sat, 30 Sep 2006 12:32:50 +0000 (GMT) (envelope-from matteo@freebsd.org) Received: from kaiser.sig11.org (87.2.178.234) by vsmtp1.tin.it (7.2.072.1) id 451BEB280017B632 for freebsd-acpi@freebsd.org; Sat, 30 Sep 2006 14:32:48 +0200 Received: from kaiser.sig11.org (localhost [127.0.0.1]) by kaiser.sig11.org (8.13.8/8.13.7) with ESMTP id k8UCWlPZ085306 for ; Sat, 30 Sep 2006 14:32:47 +0200 (CEST) (envelope-from matteo@freebsd.org) Received: (from rionda@localhost) by kaiser.sig11.org (8.13.8/8.13.7/Submit) id k8UCWjJF085305 for freebsd-acpi@freebsd.org; Sat, 30 Sep 2006 14:32:45 +0200 (CEST) (envelope-from matteo@freebsd.org) X-Authentication-Warning: kaiser.sig11.org: rionda set sender to matteo@freebsd.org using -f Date: Sat, 30 Sep 2006 14:32:44 +0200 From: Matteo Riondato To: freebsd-acpi@freebsd.org Message-ID: <20060930123244.GA29307@kaiser.sig11.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Bu8it7iiRSEf40bY" Content-Disposition: inline User-Agent: Mutt/1.5.12-2006-07-14 Subject: Powerd patch review X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Sep 2006 12:34:31 -0000 --Bu8it7iiRSEf40bY Content-Type: multipart/mixed; boundary="JP+T4n/bALQSJXh8" Content-Disposition: inline --JP+T4n/bALQSJXh8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi folks, I'm writing you to ask if you could be so kind to review the attached patch to src/usr.sbin/powerd/powerd.c . It should fix the problem descripted in PR bin/97198. I haven't a broken BIOS to test if it really works, but it should.=20 Thanks Best regards P.s. I'm not subscribed to the list, so please CC me. --=20 Matteo Riondato FreeBSD Committer (http://www.freebsd.org) G.U.F.I. Staff Member (http://www.gufi.org) FreeSBIE Developer (http://www.freesbie.org) --JP+T4n/bALQSJXh8 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="powerd.c.diff" Content-Transfer-Encoding: quoted-printable Index: powerd.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/rionda/branch/ncvs/src/usr.sbin/powerd/powerd.c,v retrieving revision 1.20 diff -u -r1.20 powerd.c --- powerd.c 19 Feb 2006 00:40:28 -0000 1.20 +++ powerd.c 29 Sep 2006 15:55:47 -0000 @@ -182,9 +182,22 @@ free(*power); return (-1); } + if (i > 0) { + if ((*freqs)[i] =3D=3D (*freqs)[i-1]) { + i--; + (*numfreqs)--; + } + } p =3D q + 1; } =20 + if ((*freqs =3D reallocf(*freqs, *numfreqs * sizeof(int))) =3D=3D + NULL) { + free(freqstr); + free(*power); + return (-1); + } + free(freqstr); return (0); } --JP+T4n/bALQSJXh8-- --Bu8it7iiRSEf40bY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFHmPs2Mp4pR7Fa+wRAvPQAJ99PaUkoaMgut85LV+kUDAvtDg5ZgCeNGSe 8DmQaRpiZF462VbyHRs3eTM= =bpP5 -----END PGP SIGNATURE----- --Bu8it7iiRSEf40bY-- From owner-freebsd-acpi@FreeBSD.ORG Sat Sep 30 19:26:37 2006 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 4EDBE16A597; Sat, 30 Sep 2006 19:26:37 +0000 (UTC) (envelope-from nate@root.org) Received: from ylpvm15.prodigy.net (ylpvm15-ext.prodigy.net [207.115.57.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id D545443D66; Sat, 30 Sep 2006 19:26:34 +0000 (GMT) (envelope-from nate@root.org) X-ORBL: [71.139.46.150] Received: from [10.0.5.50] (ppp-71-139-46-150.dsl.snfc21.pacbell.net [71.139.46.150]) by ylpvm15.prodigy.net (8.13.8 out.dk.spool/8.13.8) with ESMTP id k8UJQYHA007995; Sat, 30 Sep 2006 15:26:34 -0400 Message-ID: <451EC4E6.7030304@root.org> Date: Sat, 30 Sep 2006 12:26:30 -0700 From: Nate Lawson User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Matteo Riondato References: <20060930123244.GA29307@kaiser.sig11.org> In-Reply-To: <20060930123244.GA29307@kaiser.sig11.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: Powerd patch review X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Sep 2006 19:26:37 -0000 Matteo Riondato wrote: > Hi folks, > I'm writing you to ask if you could be so kind to review the > attached patch to src/usr.sbin/powerd/powerd.c . It should fix the > problem descripted in PR bin/97198. I haven't a broken BIOS to test if > it really works, but it should. > Thanks > Best regards > P.s. I'm not subscribed to the list, so please CC me. > > > ------------------------------------------------------------------------ > > Index: powerd.c I thought this was already fixed and merged in July by Bruno. In any case, the right place to fix this is in the cpufreq driver (or acpi_perf, where I think this only occurs). See rev 1.21.2.3 of acpi_perf.c. Actually, it would be important to see if this is happening in another driver. The output of "sysctl dev.cpu" will show all the child drivers and settings so we can see if he's using acpi_perf or some other cpufreq driver. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Sat Sep 30 22:18:24 2006 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 4141D16A412 for ; Sat, 30 Sep 2006 22:18:24 +0000 (UTC) (envelope-from matteo@freebsd.org) Received: from vsmtp2.tin.it (vsmtp2.tin.it [212.216.176.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id B45FC43D49 for ; Sat, 30 Sep 2006 22:18:23 +0000 (GMT) (envelope-from matteo@freebsd.org) Received: from kaiser.sig11.org (87.2.178.234) by vsmtp2.tin.it (7.2.072.1) id 451BEB8D001BB606; Sun, 1 Oct 2006 00:17:50 +0200 Received: from kaiser.sig11.org (localhost [127.0.0.1]) by kaiser.sig11.org (8.13.8/8.13.7) with ESMTP id k8UMHmH7092309; Sun, 1 Oct 2006 00:17:49 +0200 (CEST) (envelope-from matteo@freebsd.org) Received: (from rionda@localhost) by kaiser.sig11.org (8.13.8/8.13.7/Submit) id k8UMHjQM092308; Sun, 1 Oct 2006 00:17:45 +0200 (CEST) (envelope-from matteo@freebsd.org) X-Authentication-Warning: kaiser.sig11.org: rionda set sender to matteo@freebsd.org using -f Date: Sun, 1 Oct 2006 00:17:44 +0200 From: Matteo Riondato To: Nate Lawson Message-ID: <20060930221744.GB29307@kaiser.sig11.org> References: <20060930123244.GA29307@kaiser.sig11.org> <451EC4E6.7030304@root.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="hxkXGo8AKqTJ+9QI" Content-Disposition: inline In-Reply-To: <451EC4E6.7030304@root.org> User-Agent: Mutt/1.5.12-2006-07-14 Cc: freebsd-acpi@freebsd.org Subject: Re: Powerd patch review X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Sep 2006 22:18:24 -0000 --hxkXGo8AKqTJ+9QI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Sep 30, 2006 at 12:26:30PM -0700, Nate Lawson wrote: > Matteo Riondato wrote: > >Hi folks, > > I'm writing you to ask if you could be so kind to review the > >attached patch to src/usr.sbin/powerd/powerd.c . It should fix the > >problem descripted in PR bin/97198. I haven't a broken BIOS to test if > >it really works, but it should.=20 > >Thanks > >Best regards > >P.s. I'm not subscribed to the list, so please CC me. > > > > > >------------------------------------------------------------------------ > > > >Index: powerd.c >=20 > I thought this was already fixed and merged in July by Bruno. In any=20 > case, the right place to fix this is in the cpufreq driver (or=20 > acpi_perf, where I think this only occurs). See rev 1.21.2.3 of=20 > acpi_perf.c. Yes. PR was filed before that change, which, from my understanding, solves the issue. Sorry for the noise. > Actually, it would be important to see if this is happening in another=20 > driver. The output of "sysctl dev.cpu" will show all the child drivers= =20 > and settings so we can see if he's using acpi_perf or some other cpufreq= =20 > driver. I'll ask the PR submitter. Thanks. Best regards --=20 Matteo Riondato FreeBSD Committer (http://www.freebsd.org) G.U.F.I. Staff Member (http://www.gufi.org) FreeSBIE Developer (http://www.freesbie.org) --hxkXGo8AKqTJ+9QI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFHu0I2Mp4pR7Fa+wRAtOVAJwIqEx2lzsnGjzacIyw/Ca2mCBlcQCfaJph RHCoBWEtLvc/8DDegYS6psk= =C1a7 -----END PGP SIGNATURE----- --hxkXGo8AKqTJ+9QI--