From owner-freebsd-security Tue Nov 18 01:55:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA09071 for security-outgoing; Tue, 18 Nov 1997 01:55:10 -0800 (PST) (envelope-from owner-freebsd-security) Received: from itesec.hsc.fr (root@itesec.hsc.fr [192.70.106.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA09042 for ; Tue, 18 Nov 1997 01:54:36 -0800 (PST) (envelope-from pb@hsc.fr) Received: from mars.hsc.fr (pb@mars.hsc.fr [192.70.106.44]) by itesec.hsc.fr (8.8.8/8.8.5/itesec-1.10-nospam) with ESMTP id KAA09027 for ; Tue, 18 Nov 1997 10:54:18 +0100 (MET) Received: (from pb@localhost) by mars.hsc.fr (8.8.5/8.8.5/pb-19970301) id KAA13057; Tue, 18 Nov 1997 10:54:18 +0100 (MET) Message-ID: <19971118105417.FC32400@mars.hsc.fr> Date: Tue, 18 Nov 1997 10:54:17 +0100 From: Pierre.Beyssac@hsc.fr (Pierre Beyssac) To: freebsd-security@freebsd.org Subject: now a Cyrix processor bug X-Mailer: Mutt 0.59.1e Mime-Version: 1.0 Sender: owner-freebsd-security@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has anynone seen this? There seems to be a bug on the Cyrix, similar but not identical to the Pentium's. However the workaround on the Cyrix is apparently much simpler (you only need to disable LOCK mode in the CCR, if I understood the fix right). -----Forwarded message from troy@dakota.net (Troy)----- From: "Troy" Date: Fri, 14 Nov 1997 01:09:32 -0600 Message-Id: <01bcf0cc$4177dbe0$0201a8c0@odin.mountaintop.org> To: best-of-security@cyber.com.au Luckily, there is a fix for the Cyrix lockup bug: http://www.tux.org/~balsa/linux/cyrix/p11.html ------- Forwarded Message Follows ------ Date: Thu, 13 Nov 1997 20:34:32 -0500 (EST) To: web-consultants@just4u.com From: Rainmaker Reply-to: web-consultants@just4u.com Subject: WC:>: More chip problems BUGS GALORE: INTEL, CYRIX FIGHT GLITCHES IN THEIR CHIPS http://www.news.com/News/Item/0%2C4%2C16312%2C00.html?nd (Intel) http://www.news.com/News/Item/0%2C4%2C16347%2C00.html?nd (Cyrix) This week, the chip world seems to have more bugs than Starship Troopers. Intel has posted a bug fix for Linux servers for its "FO" bug, and a chip from Cyrix may have a bug similar to Intel's --------------------- Linux - Where do you want to go tomorrow? http://www.debian.org t r o y @ d a k o t a . n e t http://www.dakota.net/~troy -----End of forwarded message----- -- Pierre.Beyssac@hsc.fr