ACPICA Exhausting objects in 'Acpi-Namespace'

Question about which tools to use, bugs, the best way to implement a function, etc should go here. Don't forget to see if your question is answered in the wiki first! When in doubt post here.
Post Reply
User avatar
thepowersgang
Member
Member
Posts: 734
Joined: Tue Dec 25, 2007 6:03 am
Libera.chat IRC: thePowersGang
Location: Perth, Western Australia
Contact:

ACPICA Exhausting objects in 'Acpi-Namespace'

Post by thepowersgang »

I've integrated ACPI into my kernel, and from what I can see my shim code is correct. However, when I call AcpiLoadTables during intialisation, AE_NO_MEMORY is returned due to all 96 objects in the 'Acpi-Namespace' cache being used.

Has anyone seen something similar, or knows why this would be happening? I'm using the 'acpica-unix-20121114.tar.gz' tarball, with minimal patching (See link below)

acpica.c - OS interface code
Externals/ACPICA

Debug output

Code: Select all

ACPI: RSDP *0xE0000 00024 (v2 VBOX  )
ACPI: XSDT *0x1FF0030 0003C (v1 VBOX   VBOXXSDT 00000001 ASL  00000061)
ACPI: FACP *0x1FF00F0 000F4 (v4 VBOX   VBOXFACP 00000001 ASL  00000061)
ACPI: DSDT *0x1FF0470 01B96 (v1 VBOX   VBOXBIOS 00000002 INTL 20100528)
ACPI: FACS *0x1FF0200 00040
ACPI: APIC *0x1FF0240 00054 (v2 VBOX   VBOXAPIC 00000001 ASL  00000061)
ACPI: SSDT *0x1FF02A0 001CC (v1 VBOX   VBOXCPUT 00000002 INTL 20100528)
00000000000500d [ACPICA  ] 0 - AcpiOsAcquireObject: All 96 objects used in 'Acpi-Namespace'
ACPI Error: [_CRS] Namespace lookup failure, AE_NO_MEMORY (20121114/dswload-436)
ACPI Exception: AE_NO_MEMORY, During name lookup/catalog (20121114/psloop-353)
ACPI Exception: AE_NO_MEMORY, While loading namespace from ACPI tables (20121114/tbxfload-161)
Kernel Development, It's the brain surgery of programming.
Acess2 OS (c) | Tifflin OS (rust) | mrustc - Rust compiler
Currently Working on: mrustc
tom9876543
Member
Member
Posts: 170
Joined: Wed Jul 18, 2007 5:51 am

Re: ACPICA Exhausting objects in 'Acpi-Namespace'

Post by tom9876543 »

I am taking a WILD guess, I haven't looked at any code.

My guess is there might be an infinite loop somewhere.
Post Reply