INTEL D946GZIS acpi issues.
Nate Lawson
nate at root.org
Sun Sep 30 16:51:50 PDT 2007
Abdullah Ibn Hamad Al-Marri wrote:
> On 9/30/07, Nate Lawson <nate at root.org> wrote:
>> Nate Lawson wrote:
>>>> 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"
>> Please try the attached patch for 7-current. You should not see the
>> message any more but will still have an acpi_hpet0 device. Please send
>> me dmesg and devinfo -rv output after testing.
>
> Do I still need to apply the patch?
Yes, this won't fix cpufreq (need to figure out new Intel tables to make
that happen), but it will fix the "unable to allocate" error in dmesg
you first reported.
--
Nate
More information about the freebsd-acpi
mailing list