From owner-freebsd-questions  Fri May 12 18:33:14 1995
Return-Path: questions-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id SAA16474
          for questions-outgoing; Fri, 12 May 1995 18:33:14 -0700
Received: from dtr.com (dtr.rain.com [204.119.8.19])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id SAA16467
          for <questions@freebsd.org>; Fri, 12 May 1995 18:33:12 -0700
From: bmk@dtr.com
Received: (from bmk@localhost) by dtr.com (8.6.11/8.6.9) id SAA26419 for questions@freebsd.org; Fri, 12 May 1995 18:21:39 -0700
Message-Id: <199505130121.SAA26419@dtr.com>
Subject: SIGFPE on most binaries on 386dx
To: questions@FreeBSD.org
Date: Fri, 12 May 1995 18:21:38 -0700 (PDT)
Reply-To: bmk@dtr.com
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 1060      
Sender: questions-owner@FreeBSD.org
Precedence: bulk

I'm in the process of loading SNAP-0322 on a 386DX (33MHz).  I've loaded
the boot and cpio disks as well as bin- and secure- distributions.

Everything went well up to this point - so I went to boot to multi-user.
It failed to boot all of the way - getty reported SIGFPE continuously.
So I hit the big red switch, booted it to single-user, and fscked the
filesystems.

At this point, practically everything results in a SIGFPE and a lovely
core file. :(  It seems that everything out of /bin and /sbin run fine,
but anything out of /usr/bin and /usr/sbin result in a SIGFPE.

I thought it might have something to do with the Cyrix coprocessor (no 
flames, I bought the system used at a very good price) so I pulled it.  
Same thing.

Just for grins, I'm going to compile a new kernel using the GPL math
emulation, but I doubt that's going to fix the problem.

Any clues?

Hardware config is as follows:

	i386DX-33 w/SiS chipset, AMI BIOS, 8MB RAM
	Cyrix CX-83D87-33-GP
	WD-1007SE2 ISA ESDI controller
	WD (?) 16 bit ethernet card
	Monochrome display adapter