
Errata
Intel®Core™ i7 processor
Specification Update
Status: For the steppings affected, see the Summary Table of Changes.
AAJ4. Corruption of CS Segment Register During RSM While Transitioning
From Real Mode to Protected Mode
Problem: During the transition from real mode to protected mode, if an SMI (System
Management Interrupt) occurs between the MOV to CR0 that sets PE
(Protection Enable, bit 0) and the first FAR JMP, the subsequent RSM (Resume
from System Management Mode) may cause the lower two bits of CS segment
register to be corrupted.
Implication: The corruption of the bottom two bits of the CS segment register
will have no impact unless software explicitly examines the CS segment
register between enabling protected mode and the first FAR JMP. Intel® 64
and IA-32 Architectures Software Developer’s Manual Volume 3A: System
Programming Guide, Part 1, in the section titled "Switching to Protected
Mode" recommends the FAR JMP immediately follows the write to CR0 to
enable protected mode. Intel has not observed this erratum with any
commercially available software.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
AAJ5. The Processor May Report a #TS Instead of a #GP Fault
Problem: A jump to a busy TSS (Task-State Segment) may cause a #TS (invalid TSS
exception) instead of a #GP fault (general protection exception).
Implication: Operation systems that access a busy TSS may get invalid TSS
fault instead of a #GP fault. Intel has not observed this erratum with any
commercially available software.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
AAJ6. REP MOVS/STOS Executing with Fast Strings Enabled and Crossing
Page Boundaries with Inconsistent Memory Types may use an
Incorrect Data Size or Lead to Memory-Ordering Violations
Problem: Under certain conditions as described in the Software Developers Manual
section "Out-of-Order Stores For String Operations in Pentium 4, Intel Xeon,
and P6 Family Processors" the processor performs REP MOVS or REP STOS as
fast strings. Due to this erratum fast string REP MOVS/REP STOS instructions
that cross page boundaries from WB/WC memory types to UC/WP/WT
memory types, may start using an incorrect data size or may observe
memory ordering violations.
Implication: Upon crossing the page boundary the following may occur,
dependent on the new page memory type: