Intel CORE I7-900 DEKSTOP - SPECIFICATION Specification page 41

Errata
7. A general-protection exception (#GP) due to an attempt to decode an instruction
whose length is greater than 15 bytes.
Implication: Unexpected behavior may occur due to the incorrect value of the
RIP on the stack. Specifically, return from the event handler via IRET may
encounter an unexpected page fault or may begin fetching from an
unexpected code address.
Workaround: It is possible for the BIOS to contain a workaround for this erratum.
For the steppings affected, see the Summary Table of Changes.
Status:
AAJ67. The Combination of a Bus Lock and a Data Access That is Split Across
Page Boundaries May Lead to Processor Livelock
Under certain complex micro-architectural conditions, the coincidence of a bus
Problem:
lock initiated by one logical processor of a Hyper-threading enabled processor
core and data accesses that are split across page boundaries, initiated on the
other logical processor on the same core, may lead to processor livelock.
Implication: Due to this erratum, a livelock may occur that can only be
terminated by a processor reset. Intel has not observed this erratum with any
commercially available software.
Workaround: None identified.
For the steppings affected, see the Summary Table of Changes.
Status:
AAJ68. CPUID Instruction Returns Incorrect Brand String
When a CPUID instruction is executed with EAX = 80000002H, 80000003H
Problem:
and 80000004H, the return values contain the brand string Intel(R) Core(TM)
CPU when it should have Intel(R) Core(TM) i7 CPU. In addition, the processor
number will be incorrect. The return value will be will have have an additional
zero between the processor number and the @ symbol (for example: Intel(R)
Core(TM) CPU nnn0 @ x.xx GHz where nnn is a processor number and x.xx is
the frequency).
Implication: When this erratum occurs, the processor will report the incorrect
brand string.
Workaround: None identified.
For the steppings affected, see the Summary Tables of Changes.
Status:
AAJ69. An Unexpected Page Fault May Occur Following the Unmapping and
Re-mapping of a Page
An unexpected page fault (#PF) may occur for a page under the following
Problem:
conditions:
• The paging structures initially specify a valid translation for the page.
®
Intel Core™ i7 processor
Specification Update
41