Report

4BErrata and Contingencies Intel® Server System SR2520SAXSR
Applicable error message
(Type N/A if the error message
or failing text is excessive or if
there is no text)
Assertion 4BA8F23A-6BB1-48EE-88D8-ED1A3ECD34B9 SSVID
register of the Subsystem ID and Subsystem Vendor ID Capability
table must be read-only . Assertion 6B0F606E-DBB3-4B8C-8879-
32B302412EB8 SSID register of the Subsystem ID and Subsystem
Vendor ID Capability table must be read-only . Assertion
B576282C-5C66-4253-A275-257F5D49EFEF SSVID register of the
Subsystem ID and Subsystem Vendor ID Capability table cannot
have a value of 0h. These are valid failures but are not a
requirement till January 2009. A filter is being created for the
above assertions for this particular device. Added failure: Assertion
7A5587BC-5646-4DC4-9A5D-22F85AB2204E PCI Express ports
and bridges must implement Subsystem ID and Subsystem Vendor
ID Capability.
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 x64 Errata 1078
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)
The Bit 5 (Surprise Down Error Severity) in the Uncorrectable Error
Severity register (offset Ch) in the Advanced Error Reporting
Capability table must be read-only and always return 1 if the Bit 5
(Surprise Down Error Mask) in the Uncorrectable Error Mask
Register in the Advanced Errror Reporting Capability table is not
implemented
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 x64 Errata 1080
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 test causes the system to hang after testing Power
Management capability of the graphics devices. This occurs after
the device are put into various D-states and then recovered to D0
state. Cause: The AMD/ATI graphics devices require that the
VBIOS be re-posted after transition to various D-states and
recovery to D0 state which the PCIHCT doesn't do.
Additional information
(for example, test system in a
multiple system configuration)
18 Mar 9, 2008