From owner-freebsd-hackers  Fri Nov  7 16:36:31 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id QAA04591
          for hackers-outgoing; Fri, 7 Nov 1997 16:36:31 -0800 (PST)
          (envelope-from owner-freebsd-hackers)
Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [206.14.52.27])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA04584
          for <hackers@FreeBSD.ORG>; Fri, 7 Nov 1997 16:36:27 -0800 (PST)
          (envelope-from jas@flyingfox.com)
Received: (from jas@localhost)
	by biggusdiskus.flyingfox.com (8.8.5/8.8.5) id QAA28594;
	Fri, 7 Nov 1997 16:35:58 -0800 (PST)
Date: Fri, 7 Nov 1997 16:35:58 -0800 (PST)
From: Jim Shankland <jas@flyingfox.com>
Message-Id: <199711080035.QAA28594@biggusdiskus.flyingfox.com>
To: afuchs@totum.plaut.de, julian@whistle.com
Subject: Re: Newest Pentium bug (fatal)
Cc: hackers@FreeBSD.ORG
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Does anyone know if Intel has responded to this problem?  Sorry to
be repeating myself, but to my mind this is a far more severe bug
than the obscure floating point bug several years ago that knocked
billions off Intel's market cap.  If they did, in fact, quietly fix
the bug at some stepping without telling anyone, that would appear to
be a return to the modus operandi that they so publicly abandoned
after the FP brouhaha.

Jim Shankland
Flying Fox Computer Systems, Inc.