From owner-freebsd-current Thu Nov 13 15:19:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA01579 for current-outgoing; Thu, 13 Nov 1997 15:19:01 -0800 (PST) (envelope-from owner-freebsd-current) Received: from zippy.dyn.ml.org (haiti-90.ppp.hooked.net [206.169.228.90]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA01565 for ; Thu, 13 Nov 1997 15:18:55 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.7/8.8.7) with SMTP id PAA01432; Thu, 13 Nov 1997 15:19:28 -0800 (PST) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Thu, 13 Nov 1997 15:19:27 -0800 (PST) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Christopher Masto cc: freebsd-current@FreeBSD.ORG Subject: Re: Intel Pentium Bug: BSDI Releases a patch (fwd) In-Reply-To: <19971113142518.53705@netmonger.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 13 Nov 1997, Christopher Masto wrote: > I wish I knew (not that I have much Intel knowledge beyond 8086). I > 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. - alex