From owner-freebsd-security Tue Nov 18 03:35:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA14995 for security-outgoing; Tue, 18 Nov 1997 03:35:19 -0800 (PST) (envelope-from owner-freebsd-security) Received: from norden1.com (norden1.com [192.153.35.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA14984 for ; Tue, 18 Nov 1997 03:35:15 -0800 (PST) (envelope-from hometeam@techpower.net) Received: from techpower.net (hometeam@techpower.net [206.244.73.241]) by norden1.com (8.8.8/8.8.8) with ESMTP id GAA10927; Tue, 18 Nov 1997 06:36:03 -0500 (EST) Received: from localhost (hometeam@localhost) by techpower.net (8.8.8/8.8.5) with SMTP id GAA09710; Tue, 18 Nov 1997 06:39:21 GMT Date: Tue, 18 Nov 1997 06:39:21 +0000 (GMT) From: homey To: KATO Takenori cc: Pierre.Beyssac@hsc.fr, freebsd-security@freebsd.org Subject: Re: now a Cyrix processor bug In-Reply-To: <199711181030.TAA06758@gneiss.eps.nagoya-u.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Would this be added to the config file in the kernel or can this be added to rc.local also? CPU_CYRIX_NO_LOCK Also is there any info on the options for cyrix in freebsd? hometeam@techpower.net --We cannot all be masters, nor all masters Cannot be truly follow'd-- -----BEGIN PGP MESSAGE----- Version: 2.6.2 owEBqwBU/4kAlQMFADRCxNWhsddKSTR+6QEBelED/jzeC3btZfqSdIfrNoCgwUJJ iNQ33UQoMyJ2ygkfl72xP5J79yml/F4P73GnNaDVbaMOmOG2NNAi5ElE73wRh54U 17kH+n5XnYeqekV8T2TG2Q6ex3UotXPyZ1vvrCrSxapOz6a4hh0GQeA55rcwLy2W ROHwxfvaVsrX5iVOkRoerBFiC21lc3NhZ2UudHh0AAAAAA== =jCvF -----END PGP MESSAGE----- On Tue, 18 Nov 1997, KATO Takenori wrote: > > 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). > > 3.0-current and RELENG_2_2 (including 2.2.5) have following option: > > CPU_CYRIX_NO_LOCK > > which enables weak locking. Because I didn't know of the Coma bug, > and recomended setting of NO_LOCK bit is 0 in the BIOS writer's guide, > NO_LOCK bit is not modified when above option is not set. Because SMP > of FreeBSD doesn't support non-Intel chipsets, CPU_CYRIX_NO_LOCK > options may have no harmful effect. > > Also, another fix via special registers is propsed. But, Cyrix > doesn't disclose the meanings of such registers. When Cyrix discloses > the meaning of registers, I will implement latter fix. > > ---- > KATO Takenori > Dept. Earth Planet. Sci., Nagoya Univ., Nagoya, 464-01, Japan > PGP public key: finger kato@eclogite.eps.nagoya-u.ac.jp > ------------------- Powered by FreeBSD(98) ------------------- >