Date: Thu, 27 Sep 2007 16:28:51 -0700 From: Nate Lawson <nate@root.org> To: Abdullah Ibn Hamad Al-Marri <almarrie@gmail.com> Cc: freebsd-acpi@freebsd.org Subject: Re: INTEL D946GZIS acpi issues. Message-ID: <46FC3CB3.3060202@root.org> In-Reply-To: <499c70c0709271559v515d1f7ev1a88acca94b68c4c@mail.gmail.com> References: <499c70c0709271301g500d1d08gefe126bc65300d6c@mail.gmail.com> <46FC28DA.5090703@root.org> <499c70c0709271546i494a98au1a5d9dce4630a56c@mail.gmail.com> <46FC355A.1060807@root.org> <499c70c0709271559v515d1f7ev1a88acca94b68c4c@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Abdullah Ibn Hamad Al-Marri wrote: > On 9/28/07, Nate Lawson <nate@root.org> wrote: >> Abdullah Ibn Hamad Al-Marri wrote: >>> On 9/28/07, Nate Lawson <nate@root.org> wrote: >>>> Abdullah Ibn Hamad Al-Marri wrote: >>>>> Could someone tell me why I get this fail msgs, and what shall I do to >>>>> make it work? I use the latest bios from intel. >>>>> >>>>> acpi0: reservation of fed00000, 1000 (3) failed >>>>> Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 >>>>> acpi_perf0: failed in PERF_STATUS attach >>>>> device_attach: acpi_perf0 attach returned 6 >>>>> acpi_throttle0: <ACPI CPU Throttling> on cpu0 >>>>> acpi_perf0: <ACPI CPU Frequency Control> on cpu0 >>>>> acpi_perf0: failed in PERF_STATUS attach >>>>> device_attach: acpi_perf0 attach returned 6 >>>>> cpu1: <ACPI CPU> on acpi0 >>>>> acpi_perf1: <ACPI CPU Frequency Control> on cpu1 >>>>> acpi_perf1: failed in PERF_STATUS attach >>>>> device_attach: acpi_perf1 attach returned 6 >>>>> acpi_throttle1: <ACPI CPU Throttling> on cpu1 >>>>> acpi_throttle1: failed to attach P_CNT >>>>> device_attach: acpi_throttle1 attach returned 6 >>>>> acpi_perf1: <ACPI CPU Frequency Control> on cpu1 >>>>> acpi_perf1: failed in PERF_STATUS attach >>>>> device_attach: acpi_perf1 attach returned 6 >>>>> acpi_button0: <Sleep Button> on acpi0 >>>>> >>>> Try loading the cpufreq device at boot, setting in /boot/loader.conf: >>>> cpufreq_load="YES" >>>> >>>> That may give you some cpu freq control. As for the resource >>>> reservation issue, send me your ASL: >>>> >>>> acpidump -dt | gzip -9c > intel_d946gzis.asl.gz >>>> >>>> -- >>>> Nate >>> Hello Nate, >>> >>> Thanks for your fast prompt to help. >>> >>> Please get it from here. >>> >>> http://mail.wearab.net/intel_d946gzis.asl.gz >> Could you also send output of devinfo -rv? No need to post a url, just >> send directly. >> >> -- >> Nate > > Nate, > > Here is it, thanks in advance! }:) > > devinfo -rv > nexus0 > acpi0 ... > I/O memory addresses: > 0xc0000-0xdffff > 0xe0000-0xfffff > 0xf0000000-0xf7ffffff > 0xfed13000-0xfed13fff > 0xfed14000-0xfed17fff > 0xfed18000-0xfed18fff > 0xfed19000-0xfed19fff > 0xfed1c000-0xfed1ffff > 0xfed20000-0xfed9ffff > acpi_hpet0 pnpinfo unknown at unknown > I/O memory addresses: > 0xfed00000-0xfed003ff Ok, that's one problem. acpi_hpet is attaching before the system resource object. So the resources are already allocated from nexus before acpi0 can get to them. To test, set this hint at the loader prompt and the message will go away (but you won't have the HPET timer): debug.acpi.disabled="hpet" -- Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46FC3CB3.3060202>