Specification Update

Errata
30 Specification Update
AN38. BTS Message May Be Lost When the STPCLK# Signal Is Active
Problem: STPCLK# is asserted to enable the processor to enter a low-power state. Under some
circumstances, when STPCLK# becomes active, a pending BTS (Branch Trace Store)
message may be either lost and not written or written with corrupted branch address
to the Debug Store area.
Implication: BTS messages may be lost in the presence of STPCLK# assertions.
Workaround: None identified.
Status: For the steppings affected, see the Summary Tables of Changes
.
AN39. Certain Performance Monitoring Counters Related to Bus, L2 Cache
and Power Management Are Inaccurate
Problem: All Performance Monitoring Counters in the ranges 21H-3DH and 60H-7FH may have
inaccurate results up to ±7.
Implication: There may be a small error in the affected counts.
Workaround: None identified.
Status: For the steppings affected, see the Summary Tables of Changes
.
AN40. A Write to an APIC Register Sometimes May Appear to Have Not
Occurred
Problem: With respect to the retirement of instructions, stores to the uncacheable memory-
based APIC register space are handled in a non-synchronized way. For example if an
instruction that masks the interrupt flag, e.g., CLI, is executed soon after an
uncacheable write to the Task Priority Register (TPR) that lowers the APIC priority, the
interrupt masking operation may take effect before the actual priority has been
lowered. This may cause interrupts whose priority is lower than the initial TPR, but
higher than the final TPR, to not be serviced until the interrupt enabled flag is finally
set, i.e., by STI instruction. Interrupts will remain pending and are not lost.
Implication: In this example the processor may allow interrupts to be accepted but may delay their
service.
Workaround: This non-synchronization can be avoided by issuing an APIC register read after the
APIC register write. This will force the store to the APIC register before any
subsequent instructions are executed. No commercial operating system is known to be
impacted by this erratum.
Status: For the steppings affected, see the Summary Tables of Changes
.