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: <ACPI CPU Frequency Control> on cpu0 > acpi_perf0: failed in PERF_STATUS attach > device_attach: acpi_perf0 attach returned 6 > acpi_perf0: <ACPI CPU Frequency Control> on cpu0 > acpi_perf0: failed in PERF_STATUS attach > device_attach: acpi_perf0 attach returned 6 > > > On 4/4/06, Angka H. K. <harikurniawan_at_gmail.com> 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 <nate_at_root.org> 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 >>> >> > -- NateReceived on Wed Apr 05 2006 - 18:11:51 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:54 UTC