Difference between revisions of "ACPI"

From coreboot
Jump to navigation Jump to search
(→‎STOP 0xa5: Add improper aml code as reason, checked builds hint)
Line 243: Line 243:
* Parameter1 == 0x00000011 is "something in the ACPI init". This can be (among other things)
* Parameter1 == 0x00000011 is "something in the ACPI init". This can be (among other things)
** improper object names, like an object "\._PR_foo" inside the "\._PR" scope (it should be just "foo" instead, or the surrounding scope killed)
** improper object names, like an object "\._PR_foo" inside the "\._PR" scope (it should be just "foo" instead, or the surrounding scope killed)
** the use of qwords, which XP doesn't like (known error code tuple in this case: (0x11, 0x8, address of SSDT, unknown value)
** the use of qwords, which XP doesn't like (known error code tuple in this case: (0x11, 0x8, address of SSDT, unknown value))
** improper aml code, acpica as used by Linux is very lenient. (Wrong length field encoding in new acpigen code led to (0x11, 0x8, address of SSDT, unknown value))


The documentation of windbg has more detailed information about STOP 0xa5 than the MSDN article.
The documentation of windbg has more detailed information about STOP 0xa5 than the MSDN article.
STOP 0xa5 can be debugged by using checked builds of ntoskrnl and hal.dll and a second machine connected with a null-modem cable and windbg as kernel debugger.


=== Other errors ===
=== Other errors ===

Revision as of 13:30, 11 November 2010