Manualshelf

Intel Celeron Processor in the 478-Pin Package Specification Update

ManualsBrandsIntel ManualsOtherIntel Celeron Processor 566 MHz, 128K Cache, 66 MHz FSB
31323334353637383940
Errata
R
Intel
®
Celeron
®
Processor in the 478-Pin Package Specification Update 39
AC53. PWRGOOD and TAP Signals Maximum Input Hysteresis Higher Than
Specified
Problem: The maximum input hysteresis for the PWRGOOD and TAP input signals is specified at 350 mV.
The actual value could be as high as 800 mV.
Implication: The PWRGOOD and TAP inputs may switch at different levels than previously documented
specifications. Intel has not observed any issues in validation or simulation as a result of this
erratum.
Workaround: None identified.
Status: For the steppings affected, see the Summary Tables of Changes.
AC54. Incorrect Debug Exception (#DB) May Occur When a Data Breakpoint Is Set
on an FP Instruction
Problem: The default Microcode Floating Point Event Handler routine executes a series of loads to obtain
data about the FP instruction that is causing the FP event. If a data breakpoint is set on the
instruction causing the FP event, the load in the microcode routine will trigger the data breakpoint
resulting in a Debug Exception.
Implication: An incorrect Debug Exception (#DB) may occur if data breakpoint is placed on an FP instruction.
Intel has not observed this erratum with any commercially available software or system.
Workaround: None identified.
Status: For the steppings affected, see the Summary Tables of Changes.
AC55. xAPIC May Not Report Some Illegal Vector Errors
Problem: The local xAPIC has an Error Status Register, which records all errors. The bit 6 (the Receive
Illegal Vector bit) of this register, is set when the local xAPIC detects an illegal vector in a
received message. When an illegal vector error is received on the same internal clock that the
error status register is being written (due to a previous error), bit 6 does not get set and illegal
vector errors are not flagged.
Workaround: The xAPIC may not report some Illegal Vector errors when they occur at approximately the same
time as other xAPIC errors. The other xAPIC errors will continue to be reported
.
Workaround: None identified.
Status: For the steppings affected, see the Summary Tables of Changes.