27.10.2015 Views

Advanced Configuration and Power Interface Specification

ACPI_6.0

ACPI_6.0

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Advanced</strong> <strong>Configuration</strong> <strong>and</strong> <strong>Power</strong> <strong>Interface</strong> <strong>Specification</strong><br />

Data Length 4 12 Length in bytes of the generic error data.<br />

Error Severity 4 16 Identifies the error severity of the reported error:<br />

0 – Recoverable<br />

1 – Fatal<br />

2 – Corrected<br />

3 – None<br />

Note: This is the error severity of the entire event. Each Generic<br />

Error Data Entry also includes its own Error Severity field.<br />

Generic Error Data<br />

Entries<br />

Data<br />

Length<br />

20 The information contained in this field is a collection of zero or<br />

more Generic Error Data Entries (see Table 18-331).<br />

One or more Generic Error Data Entry structures may be recorded in the Generic Error Data<br />

Entries field of the Generic Error Status Block structure. This allows the platform to accumulate<br />

information for multiple hardware components related to a given error event. For example, if the<br />

generic error source represents an error that occurs on a device on the secondary side of a PCI<br />

Express / PCI-X Bridge, it is useful to record error information from the PCI Express Bridge <strong>and</strong><br />

from the PCI-X device. Utilizing two Generic Error Data Entry structures enables this. Table 18-<br />

331 defines the layout of a Generic Error Data Entry.<br />

For details of some of the fields defined in Table 18-331. See also Table 3 in section N2.2 of<br />

Appendix N of the UEFI 2.1 specification.<br />

Table 18-331 Generic Error Data Entry<br />

Field<br />

Byte<br />

Length<br />

Byte<br />

Offset<br />

Description<br />

Section Type 16 0 Identifies the type of error data in this entry.<br />

See the Section Type field of the Section Descriptor in the UEFI<br />

2.1 specification.<br />

Error Severity 4 16 Identifies the severity of the reported error.<br />

0 – Recoverable<br />

1 – Fatal<br />

2 – Corrected<br />

3 – None<br />

Revision 2 20 The revision number of the error data. The revision number is<br />

0x0201.<br />

See the Revision field of the Section Descriptor in the UEFI 2.1<br />

specification.<br />

Validation Bits 1 22 Identifies whether certain fields are populated with valid data.<br />

See the Validation Bits field of the Section Descriptor in the UEFI<br />

2.1 specification.<br />

Flags 1 23 Flags describing the error data.<br />

See the Flags field of the Section Descriptor in the UEFI 2.1<br />

specification.<br />

Error Data Length 4 24 Length in bytes of the generic error data. It is valid to have a Data<br />

Length of zero. This would be used for instance in firmware-first<br />

error h<strong>and</strong>ling where the platform reports errors to the OSPM<br />

using NMI.<br />

726 April, 2015 Version 6.0

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!