Intel Celeron D Processor 300 Sequence on 90 nm Process

Errata
Specification Update 39
continual sequence of UC fetch, implicit writeback, and Request for Ownership (RFO)
retries
Implication: This erratum has not been observed in any commercially available operating system
or application. The aliasing of memory regions, a condition necessary for this
erratum to occur, is documented as being unsupported in the
IA-32 Intel® Architecture
Software Developer's Manual, Volume 3,
section 10.12.4, Programming the PAT. However, if
this erratum occurs the system may hang
Workaround: The pages should not be mapped as either UC or WC and WB at the same time
Status: For the steppings affected, see the Summary Tables of Changes
L31. Interactions Between the Instruction Translation Lookaside Buffer
(ITLB) and the Instruction Streaming Buffer May Cause
Unpredictable Software Behavior
Problem: Complex interactions within the instruction fetch / decode unit may make it possible
for the processor to execute instructions from an internal streaming buffer containing
stale or incorrect information
Implication: When this erratum occurs, an incorrect instruction stream may be executed resulting
in unpredictable software behavior
Workaround: It is possible for the BIOS to contain a workaround for this erratum
Status: For the steppings affected, see the Summary Tables of Changes
L32. Changes to CR3 Register Do Not Fence Pending Instruction Page
Walks
Problem: When software writes to the CR3 register, it is expected that all previous/outstanding
code, data accesses and page walks are completed using the previous value in CR3
register. Due to this erratum, it is possible that a pending instruction page walk is still
in progress, resulting in an access (to the PDE portion of the page table) that may be
directed to an incorrect memory address
Implication: The results of the access to the PDE will not be consumed by the processor so the
return of incorrect data is benign. However, the system may hang if the access to the
PDE does not complete with data (e.g. infinite number of retries)
Workaround: None identified at this time
Status: For the steppings affected, see the Summary Tables of Changes
L33. The State of the Resume Flag (RF Flag) in a Task-State Segment
(TSS) May Be Incorrect