#5449: ACPI: AcpiInitializeTables fails on Acer Aspire One AOA110 --------------------------+------------------------------------------------- Reporter: vegardw | Owner: nobody Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/ACPI | Version: R1/Development Keywords: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by bonefish): Analyzing #1925 I encountered a general problem in the boot loader. Physical address ranges between usable RAM ranges can later in the kernel erroneously become allocatable memory (at least if they aren't claimed during the VM setup). r34933 changes how physical pages are freed. Since that revision they are enqueued at the front, so they are reused as quickly as possible (thus being more cache friendly). For aforementioned non-RAM ranges, that means they are likely already allocated during the boot process, so that the negative effects can be observed earlier than before (where that would only happen after a full cycle through the free list). I'm currently working on fixing the problem, but unexpectedly the actually rather easy fix seems to cause the boot process to hang later (double fault without entering KDL). Investigating... -- Ticket URL: <http://dev.haiku-os.org/ticket/5449#comment:31> Haiku <http://dev.haiku-os.org> Haiku - the operating system.