![Intel SL6NQ - Xeon 2.4 GHz/533MHz/512 KB CPU Processor 2.4GHz Скачать руководство пользователя страница 34](http://html1.mh-extra.com/html/intel/sl6nq-xeon-2-4-ghz-533mhz-512-kb-cpu-processor-2-4ghz/sl6nq-xeon-2-4-ghz-533mhz-512-kb-cpu-processor-2-4ghz_specification_2071948034.webp)
34
Intel
®
Xeon
®
Processor Specification Update
Errata
corrected page tables are left in a non-accessed or non-modified state) the processor may livelock.
Intel has not been able to reproduce this erratum with commercial software.
Implication:
This erratum occurs in systems where page tables are being modified by other processors. If this
erratum is encountered, the processor will livelock resulting in a system hang or operating system
failure.
Workaround:
It is possible for the BIOS to contain a workaround for this erratum.
Status:
For the steppings affected, see the
Summary Table of Changes
.
P21
PAT index MSB may be calculated incorrectly
Problem:
When Mode B or Mode C paging support is enabled and all of the following events occur:
•
A page walk returns the page directory entry (PDE) for a large page from memory.
•
A subsequent page walk returns the page table entry (PTE) for a 4k page from memory and the
page attribute table (PAT) upper index bit in this PTE is set to 1b.
It is possible that the PAT upper index bit in the PTE is incorrectly ignored and assumed to be
0b. The result is that the memory type in the PAT that should have come from the
corresponding PAT index [4-7] incorrectly comes from PAT index [0-3].
Implication:
If an operating system has programmed the PAT in an asymmetrical fashion i.e. PAT[0-3] is
different from PAT[4-7] then an incorrect memory type may be used.
Workaround:
None at this time.
Status:
For the steppings affected, see the
Summary Table of Changes
.
P22
System bus interrupt messages without data and which receive a Hard
failure response may hang the processor
Problem:
When a system bus agent (processor or chipset) issues an interrupt transaction without data onto
the system bus and the transaction receives a HardFailure response, a potential processor hang can
occur. The processor, which generates an inter-processor interrupt (IPI) that receives the
HardFailure response, will still log the MCA error event cause as HardFailure, even if the APIC
causes a hang. Other processors, which are true targets of the IPI, will also hang on
hardfail-without-data, but will not record an MCA HardFailure event as the cause. If a HardFailure
response occurs on a system bus interrupt message with data, the APIC will complete the operation
so as not to hang the processor.
Implication:
The processor may hang.
Workaround:
None at this time.
Status:
For the steppings affected, see the
Summary Table of Changes
.
P23
SQRTPD and SQRTSD may return QNaN indefinite instead of negative zero
Problem:
When DAZ mode is enabled, and a
SQRTPD
or
SQRTSD
instruction has a negative denormal
operand, the instruction will return a QNaN indefinite when the specified response should be zero.
Implication:
When this erratum occurs, the instruction will return a QNaN indefinite when a zero is expected.
Workaround:
Ensure that negative denormals are not used as operands to the
SQRTPD
or
SQRTSD
instructions
when DAZ mode is enabled. Software could enable FTZ mode to ensure that negative denormals
are not generated by computation prior to execution of the
SQRTPD
or
SQRTSD
instructions.
Status:
For the steppings affected, see the
Summary Table of Changes
.