From owner-freebsd-current  Thu Nov 13 20:16:16 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id UAA22140
          for current-outgoing; Thu, 13 Nov 1997 20:16:16 -0800 (PST)
          (envelope-from owner-freebsd-current)
Received: from luke.cpl.net (luke.cpl.net [207.67.172.194])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA22135
          for <freebsd-current@FreeBSD.ORG>; Thu, 13 Nov 1997 20:16:11 -0800 (PST)
          (envelope-from shawn@luke.cpl.net)
Received: from localhost (shawn@localhost) by luke.cpl.net (8.8.7/8.6.12) with SMTP id UAA22658; Thu, 13 Nov 1997 20:17:03 -0800 (PST)
Date: Thu, 13 Nov 1997 20:17:02 -0800 (PST)
From: Shawn Ramsey <shawn@luke.cpl.net>
To: Alex <garbanzo@hooked.net>
cc: Christopher Masto <chris@netmonger.net>, freebsd-current@FreeBSD.ORG
Subject: Re: Intel Pentium Bug: BSDI Releases a patch (fwd)
In-Reply-To: <Pine.BSF.3.96.971113151830.275D-100000@zippy.dyn.ml.org>
Message-ID: <Pine.BSF.3.95.971113201546.22079C-100000@luke.cpl.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> > do know that I'm glad we didn't cancel our K6 order upon seeing that
> > there appears to be an emerging software workaround.  Two things still
> > make me nervous (both "seen on the net" but unconfirmed): someone said
> > that BSDI's patch is now listed as "unavailable", and someone else
> > said that their Linux system still locked up after applying the patch.
> > Maybe it doesn't work in all cases.  :-/
> 
> If it locks up computers, that's probably why they decided to pull the
> patch, which may or may not be available on uu.net's mirror.  However
> there's still one sure fire fix that will work, and that is to disable the
> L1 cache.  Sure it'll run slow as heck, but that should grant you some
> immunity.

If your gonna do that, might as well switch your CPU to a non-intel P5
compatible chip...