Report

Intel® Server System SR2500ALLXR 4BErrata and Contingencies
Applicable error message
(Type N/A if the error message
or failing text is excessive or if
there is no text)
According to the PCI Express Base Specification, Rev 2.0 Section
7.8.8, this bit field is undefined when the link is not up. If there is
not PCIe device behind the bridge, then the link can NOT be up
and therefore the field is undefined. Bit 13 in the same register
(Link Status) can be used to determine if the link is active (up).
The PCIHCT uses the Presence Detect State bit of the Slot Status
register to determine whether a child device is present. However,
the Presence Detect State bit only returns valid data if the Slot
Implemented bit is set (bit 8 of PCIe capabilities register). If the
PCIe root port or downstream port will never have a device behind
it, the Slot Implemented bit is cleared to 0. Per the spec, PDS will
always be 1 when the Slot Implemented bit is clear. Therefore PDS
can not be used to determine device presence when the SI bit is
clear.
Additional information
(for example, test system in a
multiple system configuration)
Operating system
(Windows XP, Windows 2000, etc.)
Failure type
(Contingency, Errata, Incident)
ID number
Windows Server 2008 Errata 1166
Failing test name
PCI Hardware Compliance Test
Applicable error message
(Type N/A if the error message
or failing text is excessive or if
there is no text)
PCI Compliance - Bit 20 (Data Link Layer Link Active Reporting
Capable) in the Link Capabilities register (offset Ch) in the PCI
Express Capability table must be read-only. RESOLUTION: The
following PCI Compliance test assertion failure is allowed
ABC66DC4-D88C-496E-845D-63B7F9A05176.
Additional information
(for example, test system in a
multiple system configuration)
Operating system
(Windows XP, Windows 2000, etc.)
Failure type
(Contingency, Errata, Incident)
ID number
Windows Server 2008 Errata 1110
Failing test name
BitLocker Drive Encryption BIOS Interface Logo Test
Applicable error message
(Type N/A if the error message
or failing text is excessive or if
there is no text)
For platforms without Trusted Platform Modules (TPM), the WLK
1.1 kit has an issue which randomly causes the BitLocker Drive
Encryption BIOS Interface Logo Test to fail.
Additional information
(for example, test system in a
multiple system configuration)
May 13, 2008 15