Pentium F00F bug explained

The invalid operand with locked CMPXCHG8B instruction bug, commonly referred to as the Pentium F00F bug (as shorthand for f0 0f c7 c8, the hexadecimal encoding of one offending instruction),[1] is a design flaw in the majority of Intel Pentium, Pentium MMX, and Pentium OverDrive processors (all in the P5 microarchitecture).[2]

Description

The instruction represents:

lock cmpxchg8b eax

The operand could be a register other than eax. The cmpxchg8b instruction is used to compare the value in the edx and eax registers with an 8-byte value at some memory location. In this example a 4-byte register is used as the destination operand, which is not big enough to store the 8-byte result.

Under normal circumstances, this instruction would simply result in an exception; however, when used with the lock prefix (normally used to prevent two processors from interfering with the same memory location), the exception handler is never called, the processor stops servicing interrupts and the CPU must be reset to recover.

The instruction does not require any special privileges and, due to the proliferation of Intel microprocessors, was considered a serious issue at the time. Operating system vendors responded by implementing workarounds that detected the condition and prevented the crash.

Although technically not an example of either, the f00f instruction is often considered an HCF instruction or a killer poke. Since the f00f bug has become common knowledge, the term is sometimes used to describe similar hardware design flaws such as the Cyrix coma bug.

No permanent hardware damage would result from executing the f00f instruction on a vulnerable system. Depending on the file system, operating system, and other circumstances, it is possible for data loss to occur if the disk buffers have not been flushed, if drives were interrupted during a write operation, or if some other non-atomic operation was interrupted.

No Intel processors since the introduction of the Pentium Pro have been affected by the bug. The myB2 stepping fixed this issue.[2]

Information about this bug first appeared on the Internet on or around 7 November 1997.[3]

See also

External links

Notes and References

  1. Web site: The Pentium F00F Bug: Workarounds for a nasty problem. Collins, Robert R.. May 1, 1998. Dr. Dobb's Journal.
  2. Book: Pentium Processor Specification Update. Intel Corporation. 1999-01. 51 - 52. PDF. 2006-11-02. order number 242480-041.
  3. Web site: Nieuwe Intel Pentium BUG. 2008-07-07.