From owner-freebsd-current@FreeBSD.ORG Wed Apr 5 20:11:51 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A432D16A420 for ; Wed, 5 Apr 2006 20:11:51 +0000 (UTC) (envelope-from nate@root.org) Received: from ylpvm01.prodigy.net (ylpvm01-ext.prodigy.net [207.115.57.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9EDAD43D6D for ; Wed, 5 Apr 2006 20:11:49 +0000 (GMT) (envelope-from nate@root.org) Received: from pimout6-ext.prodigy.net (pimout6-int.prodigy.net [207.115.4.22]) by ylpvm01.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id k35KBjag027849 for ; Wed, 5 Apr 2006 16:11:46 -0400 X-ORBL: [71.139.116.48] Received: from [10.0.5.51] (ppp-71-139-116-48.dsl.snfc21.pacbell.net [71.139.116.48]) by pimout6-ext.prodigy.net (8.13.4 outbound domainkey aix/8.13.4) with ESMTP id k35KBe9k176386; Wed, 5 Apr 2006 16:11:40 -0400 Message-ID: <44342454.8000207@root.org> Date: Wed, 05 Apr 2006 13:11:00 -0700 From: Nate Lawson User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: "Angka H. K." References: <4c40c4e70604051146y48cc35fal1680d5121f73ab29@mail.gmail.com> In-Reply-To: <4c40c4e70604051146y48cc35fal1680d5121f73ab29@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Alexander Leidinger , current@freebsd.org Subject: Re: ACPI Error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Apr 2006 20:11:51 -0000 It can't attach your acpi_perf device (cpu frequency). Try also loading cpufreq.ko, it may work. Or, try adding to loader.conf: debug.acpi.disabled="sysres" Something might be claiming the status port. Angka H. K. wrote: > Great the error is gone now thanks. > > I have other question about ACPI. My dmesg showing like below and I know > nothing about ACPI. What does it mean and can it be fix ? > > acpi_perf0: on cpu0 > acpi_perf0: failed in PERF_STATUS attach > device_attach: acpi_perf0 attach returned 6 > acpi_perf0: on cpu0 > acpi_perf0: failed in PERF_STATUS attach > device_attach: acpi_perf0 attach returned 6 > > > On 4/4/06, Angka H. K. wrote: >> Thanks a lot, you really dedicate your time to FreeBSD >> Sorry I still don't have good connection to do cvsup, may be tomorrow. >> >> Ah.. hard time to finish my job sorry can't help :( >> >> >> On 4/4/06, Nate Lawson wrote: >> >>> Angka H. K. wrote: >>>> Thanks for the replay >>>> I am updating my source now and planing to rebuild it again, but I >>> don't see >>>> any changes on ACPI code. >>>> >>>> I was mistype on the val that return by kernel, the error should be >>> "acpi: >>>> bad write to port 0x073(8) val 20", I am sorry. >>>> Hope it'll be fixed soon. >>> Ok, I fixed the range check on ports so 0x73 should not trigger it. If >>> you have some other write to a port that IS in the blacklist, you'll >>> still get the warning. >>> >>> Ultimately, I intend to emulate what Windows does which is block all >>> writes to the PIC, and block all writes on XP or newer BIOSen. >>> >>> -- >>> Nate >>> >> > -- Nate