From nobody  Thu Jan 28 09:06:47 1999
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA11926;
          Thu, 28 Jan 1999 09:06:47 -0800 (PST)
          (envelope-from nobody)
Message-Id: <199901281706.JAA11926@hub.freebsd.org>
Date: Thu, 28 Jan 1999 09:06:47 -0800 (PST)
From: patrick@cyberdinges.demon.nl
To: freebsd-gnats-submit@freebsd.org
Subject: fatal signal: floating point exception + fatal signal: bus error
X-Send-Pr-Version: www-1.0

>Number:         9755
>Category:       i386
>Synopsis:       fatal signal: floating point exception + fatal signal: bus error
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Jan 28 09:10:00 PST 1999
>Closed-Date:    Thu Mar 11 03:55:02 PST 1999
>Last-Modified:  Thu Mar 11 03:55:23 PST 1999
>Originator:     Patrick Kessen
>Release:        FreeBSD 3.0 (Walnut Creek CD)
>Organization:
>Environment:
>Description:
FreeBSD v3 installs fine, after installation after kernel configuration 
with -c, v theb screen goes black several times during the boot-stage, 
then the screen displays some flashy colored characters, then I see 
the normal screen again and then I see :
init: fatal signal: Floating point exception
init: fatal signal: Floating point exception
init: fatal signal: Bus Error
last message repeated 3 times
init: fatal signal: Bus Error
last message repeated 2 times
init: fatal signal: Bus Error
last message repeated 5 times
last message repeated 12 times

FreeBSD 2.2.2 has worked great on this machine for several months.
The machine is an Intel Xpress LX server (Pentium 90) with 192Mb RAM
an on-board WD 512Kb videochip and dual channel EISA Adaptec SCSI.

FreeBSD 2.2.8 gives the same problems as 3.0

Sometimes (at random) I am able to log-on, after some time the console 
locks-up and only a hardware-reset gets me out again.
>How-To-Repeat:
just reboot

>Fix:

>Release-Note:
>Audit-Trail:

From: Patrick <patrick@cyberdinges.demon.nl>
To: freebsd-gnats-submit@freebsd.org, patrick@cyberdinges.demon.nl
Cc:  
Subject: Re: i386/9755: fatal signal: floating point exception + fatal signal: 
 bus error
Date: Thu, 28 Jan 1999 20:50:29 +0100

 Hi,
 
 removing 128Mb RAM leaving 64Mb RAM in the system solves the problem on
 2.2.8 and 3.0
 
 The RAM is not bad and the mainboard can address more then 64Mb RAM.
 Linux 2.1.132, 2.2.0-pre9, OS/2 Warp v4 and Windows NT WS  v4
 work great with the 192Mb RAM and use it too (provided I use enough to
 fill up the RAM;))
 
 Why can't I use more then 64Mb RAM with 2.2.8 and 3.0?
 
 
 

From: Patrick <patrick@cyberdinges.demon.nl>
To: freebsd-gnats-submit@freebsd.org, patrick@cyberdinges.demon.nl
Cc:  
Subject: Re: i386/9755: fatal signal: floating point exception + fatal signal: 
 bus error
Date: Fri, 29 Jan 1999 19:42:45 +0100

 Ok,
 
 after I got the machine running stable with 64Mb RAM I decided to give a
 chance to
 compiling  a new kernel. I set the MAXMEM option to (192*1024), built
 the kernel, installe dit and rebooted after placing the full 192Mb RAM
 and it works
 stable as a concrete block.
 This is with 2.2.8, now I have 2.2.8 running I realle have no need to
 try 3.0, I'll wait form 3.1 or 4.0 whatever the next version is called
 and I'll give it a try again.
 
 Still I'd like to see a fix for this problem so I don't have to take
 apart my servers every time I install a new FreeBSD version from now on.
 
 Any ideas as to what might cause this problem? If you need more details
 on my setup (hardware/software) I'll be glad to help.
 
 
State-Changed-From-To: open->closed 
State-Changed-By: sheldonh 
State-Changed-When: Thu Mar 11 03:55:02 PST 1999 
State-Changed-Why:  
The comments about MAXMEM in LINT are quite detailed. The speculative 
memory probe is probably failing. Use MAXMEM to circumvent it. 
>Unformatted:
