From owner-freebsd-bugs  Tue Dec  9 21:14:35 1997
Return-Path: <owner-freebsd-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id VAA16202
          for bugs-outgoing; Tue, 9 Dec 1997 21:14:35 -0800 (PST)
          (envelope-from owner-freebsd-bugs)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA16197
          for <freebsd-bugs@FreeBSD.ORG>; Tue, 9 Dec 1997 21:14:30 -0800 (PST)
          (envelope-from bde@zeta.org.au)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.6.9) id PAA06829; Wed, 10 Dec 1997 15:59:02 +1100
Date: Wed, 10 Dec 1997 15:59:02 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199712100459.PAA06829@godzilla.zeta.org.au>
To: deuerl@baerle.indra.de, jkh@time.cdrom.com
Subject: Re: double fault
Cc: freebsd-bugs@FreeBSD.ORG
Sender: owner-freebsd-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>> FreeBSD 2.2.5-RELEASE #0: Wed Dec  3 20:39:19 MET 1997
>> 
>> When inserting more than 64MB in my maschine it crashes on boot up
>> with the message 
>> 
>> double fault
>
>Boot from the hard disk, you mean, or boot from the installation
>floppy?
>
>> i thought this bug was fixed ...
>
>There have never been any known memory limitations for booting off a
>hard disk or other non-installation media.  That was strictly an
>MFS-related problem on the boot floppy.

ProbIng memory has always known to be unsafe, and wasn't done until
2.2.5, so there was a safe 64MB limit.  From machdep.c:

	/* Use BIOS values stored in RTC CMOS RAM, since probing
	 * breaks certain 386 AT relics.
	 */

Bruce