Intel SL3QA - Pentium III 550 MHz Processor Specification page 83

Specification update
Table of Contents

Advertisement

Errata
clear any unexpected interrupts that may occur.
spurious vector does not generate an EOI, therefore the spurious vector should not
be used when writing the LVT
Status:
For the steppings affected, see the Summary Tables of Changes.
E97.
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 Tables of Changes.
E98.
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.
E99.
Using 2M/4M Pages When A20M# Is Asserted May Result in
Incorrect Address Translations
Problem:
An external A20M# pin if enabled forces address bit 20 to be masked (forced to zero)
to emulates real-address mode address wraparound at 1 megabyte. However, if all of
the following conditions are met, address bit 20 may not be masked.
paging is enabled
a linear address has bit 20 set
the address references a large page
A20M# is enabled
Specification Update
The ISR associated with the
83

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents