Справочник Пользователя для Intel Celeron Mobile 585 LF80537NF0481M
Модели
LF80537NF0481M
R
16
Specification Update
V3.
Transaction Is Not Retried after BINIT#
Problem:
If the first transaction of a locked sequence receives a HITM# and DEFER# during the snoop phase it
should be retried and the locked sequence restarted. However, if BINIT# is also asserted during this
transaction, it will not be retried.
should be retried and the locked sequence restarted. However, if BINIT# is also asserted during this
transaction, it will not be retried.
Implication: When this erratum occurs, locked transactions will unexpectedly not be retried.
Workaround: None identified
Status:
For the steppings affected, see the Summary Tables of Changes.
V4.
Invalid Opcode 0FFFh Requires a ModRM Byte
Problem:
Some invalid opcodes require a ModRM byte (or other following bytes), while others do not. The
invalid opcode 0FFFh did not require a ModRM byte in previous generation Intel architecture
processors, but does in the Intel
invalid opcode 0FFFh did not require a ModRM byte in previous generation Intel architecture
processors, but does in the Intel
®
Pentium
®
4 processor.
Implication: The use of an invalid opcode 0FFFh without the ModRM byte may result in a page or limit fault on the
Intel
®
Pentium
®
4 processor.
Workaround: Use a ModRM byte with invalid 0FFFh opcode.
Status:
For the steppings affected, see the Summary Tables of Changes.
V5.
FSW May Not Be Completely Restored after Page Fault on FRSTOR or FLDENV
Instructions
Instructions
Problem:
If the FPU operating environment or FPU state (operating environment and register stack) being loaded
by an FLDENV or FRSTOR instruction wraps around a 64Kbyte or 4Gbyte boundary and a page fault
(#PF) or segment limit fault (#GP or #SS) occurs on the instruction near the wrap boundary, the upper
byte of the FPU status word (FSW) might not be restored. If the fault handler does not restart program
execution at the faulting instruction, stale data may exist in the FSW.
by an FLDENV or FRSTOR instruction wraps around a 64Kbyte or 4Gbyte boundary and a page fault
(#PF) or segment limit fault (#GP or #SS) occurs on the instruction near the wrap boundary, the upper
byte of the FPU status word (FSW) might not be restored. If the fault handler does not restart program
execution at the faulting instruction, stale data may exist in the FSW.
Implication: When this erratum occurs, stale data will exist in the FSW.
Workaround: Ensure that the FPU operating environment and FPU state do not cross 64Kbyte or 4Gbyte boundaries.
Alternately, ensure that the page fault handler restarts program execution at the faulting instruction after
correcting the paging problem.
correcting the paging problem.
Status:
For the steppings affected, see the Summary Tables of Changes.