ACPI - Revision history

PatrickGeorgi: /* Windows Errors */

2013-02-22T19:57:58Z

‎Windows Errors

PatrickGeorgi: /* Fixed ACPI Description Table (FADT) */

2012-09-13T08:29:49Z

‎Fixed ACPI Description Table (FADT)

PatrickGeorgi: /* Windows Errors */

2012-09-06T10:57:19Z

‎Windows Errors

PatrickGeorgi: /* Fixed ACPI Description Table (FADT) */

2012-09-06T10:52:04Z

‎Fixed ACPI Description Table (FADT)

PatrickGeorgi: /* Windows Errors */ Note Windows XP setup error and its remedy, noted by Scott Duplichan

2011-05-20T06:09:37Z

‎Windows Errors: Note Windows XP setup error and its remedy, noted by Scott Duplichan

Alien: updated SVN browser paths that were broken after the v2->v4 version change

2011-01-31T19:55:34Z

updated SVN browser paths that were broken after the v2->v4 version change

Ranma: /* STOP 0xa5 */ Add improper aml code as reason, checked builds hint

2010-11-11T13:30:46Z

‎STOP 0xa5: Add improper aml code as reason, checked builds hint

PatrickGeorgi: /* STOP 0xa5 */

2010-11-04T08:05:47Z

‎STOP 0xa5

Jakllsch: s/APCI/ACPI/g

2010-09-18T13:35:35Z

s/APCI/ACPI/g

Stepan: /* Further Resources */

2010-05-13T20:17:42Z

‎Further Resources

@@ Line 240: / Line 240: @@
 = Potential Issues =
 == Windows Errors ==
 === STOP 0xa5 ===
 A Blue Screen Of Death with STOP code 0x000000A5 is ACPI related, and it seems that Microsoft is very strict when it comes to ACPI compliance. http://support.microsoft.com/kb/314830/en explains some of the error codes, but not all of them.

← Older revision		Revision as of 08:29, 13 September 2012
Line 30:		Line 30:

	If Linux complains about "IRQ 9 nobody cared", recheck these values. The gpeX_blk must span both status and enable bits (which is easy to get wrong given the unclear documentation on this). If GPE0_STS is 64bit, you have to configure 16 bytes (or 128 bits in the x_* variant).		If Linux complains about "IRQ 9 nobody cared", recheck these values. The gpeX_blk must span both status and enable bits (which is easy to get wrong given the unclear documentation on this). If GPE0_STS is 64bit, you have to configure 16 bytes (or 128 bits in the x_* variant).
		+
		+	ACPI spec says to set only one of FIRMWARE_CTRL and X_FIRMWARE_CTRL, which is different to how other x_* values are handled. Set firmware_ctrl if located at <4GB, x_firmware_ctrl if located at >=4GB, and set the other value to 0. It's generally more useful to set firmware_ctrl (to support 32bit operating systems).

	== Differentiated System Description Table (DSDT) ==		== Differentiated System Description Table (DSDT) ==

@@ Line 268: / Line 268: @@
 === Other errors ===
 * Quoting [http://support.microsoft.com/?scid=kb%3Ben-us%3B935806&x=14&y=18 MSDN]: A "Stop: 0x0000007E" error message or a "Stop: 0x0000008E" error message typically means that a kernel mode component, such as a driver, encountered an error that could not be handled by the built-in Windows error handler.
 == Linux Errors ==

← Older revision		Revision as of 10:52, 6 September 2012
Line 28:		Line 28:

	In this example the ACPI IRQ is 9, and the '''PM1A event block''' starts at VT8237R_ACPI_IO_BASE. You may obtain some values from '''cat /proc/ioport''' if running with the proprietary BIOS. Not all blocks are necessary—usually only PM1A PMTMR and GPE0 are used. Please note that this table has the I/O port information stored twice using different formats. Please consult the ACPI specification for details. Most settings in '''fadt.c''' can use their default values.		In this example the ACPI IRQ is 9, and the '''PM1A event block''' starts at VT8237R_ACPI_IO_BASE. You may obtain some values from '''cat /proc/ioport''' if running with the proprietary BIOS. Not all blocks are necessary—usually only PM1A PMTMR and GPE0 are used. Please note that this table has the I/O port information stored twice using different formats. Please consult the ACPI specification for details. Most settings in '''fadt.c''' can use their default values.
		+
		+	If Linux complains about "IRQ 9 nobody cared", recheck these values. The gpeX_blk must span both status and enable bits (which is easy to get wrong given the unclear documentation on this). If GPE0_STS is 64bit, you have to configure 16 bytes (or 128 bits in the x_* variant).

	== Differentiated System Description Table (DSDT) ==		== Differentiated System Description Table (DSDT) ==

@@ Line 248: / Line 248: @@
 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 ===
 * Quoting [http://support.microsoft.com/?scid=kb%3Ben-us%3B935806&x=14&y=18 MSDN]: A "Stop: 0x0000007E" error message or a "Stop: 0x0000008E" error message typically means that a kernel mode component, such as a driver, encountered an error that could not be handled by the built-in Windows error handler.
 == Linux Errors ==
 === ACPI 2.0/3.0 without XSDT ===

@@ Line 3: / Line 3: @@
 = ACPI setup HOWTO =
-Please have a look at the files in [http://tracker.coreboot.org/trac/coreboot/browser/trunk/coreboot-v2/src/mainboard/asus/a8v-e_se src/mainboard/asus/a8v-e_se]. Please also check out http://acpi.info, which contains the ACPI specification.
+Please have a look at the files in [http://tracker.coreboot.org/trac/coreboot/browser/trunk/src/mainboard/asus/a8v-e_se src/mainboard/asus/a8v-e_se]. Please also check out http://acpi.info, which contains the ACPI specification.
 == Set up hardware ==
@@ Line 35: / Line 35: @@
 ==== Generic part of DSDT ====
-A very generic DSDT table would look similar to the ASUS A8V-E/ASUS M2V-MX SE [http://tracker.coreboot.org/trac/coreboot/browser/trunk/coreboot-v2/src/mainboard/asus/a8v-e_se/dsdt.asl src/mainboard/asus/a8v-e_se/dsdt.asl] file.
+A very generic DSDT table would look similar to the ASUS A8V-E/ASUS M2V-MX SE [http://tracker.coreboot.org/trac/coreboot/browser/trunk/src/mainboard/asus/a8v-e_se/dsdt.asl src/mainboard/asus/a8v-e_se/dsdt.asl] file.
 <pre>

@@ Line 243: / Line 243: @@
 * 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)
-** 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))
 The documentation of windbg has more detailed information about STOP 0xa5 than the MSDN article.
 === Other errors ===

@@ Line 241: / Line 241: @@
 * Parameter1 == 0x0000000D means that some _ADR or _HID Symbol is missing in the dsdt.asl.
-* Parameter1 == 0x00000011 is "something in the ACPI init". This can be improper object names, like an object "\._PR_foo" inside the "\._PR" scope (it should be just "foo" instead, or the surrounding scope killed)
+* Parameter1 == 0x00000011 is "something in the ACPI init". This can be (among other things)
 The documentation of windbg has more detailed information about STOP 0xa5 than the MSDN article.

@@ Line 95: / Line 95: @@
 === CPU Power Management ===
-The CPU power management is hardware specific. It is described in APCI specs and also in AMD BIOS and Kernel Developer guide. The rest of this section describes the AMD specific part. AMD needs ACPI objects which describe the similar info as the legacy PowerNow table. Check the BKDG for details.
+The CPU power management is hardware specific. It is described in ACPI specs and also in AMD BIOS and Kernel Developer guide. The rest of this section describes the AMD specific part. AMD needs ACPI objects which describe the similar info as the legacy PowerNow table. Check the BKDG for details.
 The content of the tables must be generated at runtime, which is a bit of a problem, because the AML code must be generated or DSDT patched. There is an '''acpigen''' infrastructure to generate the AML code.
@@ Line 126: / Line 126: @@
   * Store (42, Debug)
-Second method is userspace interpretation of DSDT table. This can be achieved with APCI CA Unix package. It is located in '''acpica-unix-20081204/tools/acpiexec'''. You can eval the objects and run the methods, like _CRS for example.
+Second method is userspace interpretation of DSDT table. This can be achieved with ACPI CA Unix package. It is located in '''acpica-unix-20081204/tools/acpiexec'''. You can eval the objects and run the methods, like _CRS for example.
 If you receive a BSOD with '''STOP code 0xa5''', check this: http://support.microsoft.com/kb/314830.

← Older revision		Revision as of 20:17, 13 May 2010
Line 285:		Line 285:
	* [http://en.opensuse.org/S2ram Suspend to RAM utility]		* [http://en.opensuse.org/S2ram Suspend to RAM utility]
	* [http://download.microsoft.com/download/5/b/9/5b97017b-e28a-4bae-ba48-174cf47d23cd/CPA002_WH06.ppt Windows Vista ACPI information, incl. advice on common problems in ACPI implementations]		* [http://download.microsoft.com/download/5/b/9/5b97017b-e28a-4bae-ba48-174cf47d23cd/CPA002_WH06.ppt Windows Vista ACPI information, incl. advice on common problems in ACPI implementations]
		+	* [http://smackerelofopinion.blogspot.com/2010/03/debugging-acpi-using-acpiexec.html Debugging ACPI using acpiexec]