Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!cpk-news-hub1.bbnplanet.com!news.bbnplanet.com!su-news-hub1.bbnplanet.com!www.nntp.primenet.com!nntp.primenet.com!howland.erols.net!agate!not-for-mail
From: mconst@soda.CSUA.Berkeley.EDU (Michael Constant)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Cyrix 387 error reporting broken
Date: 7 Dec 1996 10:31:44 -0800
Organization: Society for the Prevention of Cruelty to Vegetables, UC Berkeley
Lines: 14
Message-ID: <58cd6g$c9m@soda.CSUA.Berkeley.EDU>
NNTP-Posting-Host: soda.csua.berkeley.edu
I have a 386 with a Cyrix 387 chip. With all versions of FreeBSD I've
used (2.0.5 to 2.1.6) it reports
npx0: error reporting broken; using 387 emulator
The emulator works fine, but I'm curious if this is some known bug with
older-revision 387s. I didn't see any mention in npx.c of a known bug,
and in fact it mentions that the npx code was tested on a Cyrix 387 (and
presumably worked).
My 387 passes all the tests on the demo diskette which came with it, for
what that's worth.
--
Michael Constant (mconst@soda.csua.berkeley.edu)