From owner-freebsd-bugs  Tue Jul 22 01:54:03 1997
Return-Path: <owner-freebsd-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id BAA17364
          for bugs-outgoing; Tue, 22 Jul 1997 01:54:03 -0700 (PDT)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA17359
          for <freebsd-bugs@FreeBSD.ORG>; Tue, 22 Jul 1997 01:53:58 -0700 (PDT)
Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.6/8.6.9) with ESMTP id BAA00481; Tue, 22 Jul 1997 01:52:31 -0700 (PDT)
To: Julian Sanchez <julian@w-bin.com>
cc: "'freebsd-bugs@freebsd.org'" <freebsd-bugs@FreeBSD.ORG>, dg@root.com
Subject: Re: 2.2.2 Installation problems 
In-reply-to: Your message of "Mon, 21 Jul 1997 18:52:22 CDT."
             <01BC9607.39B2D510@hatt_52.datastar.net> 
Date: Tue, 22 Jul 1997 01:52:31 -0700
Message-ID: <477.869561551@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

[sorry for earlier empty reply - my fingers slipped on the cc-edit]

> I recently downloaded from ftp.cdrom.com the version 2.2.2 of
> FreeBSD. I crea ted the boot floppy by using the file stored in
> /floppies (and later the one th at was in /floppies/newer).
>
> The problem I have is that everytime I start the boot floppy it
> hangs right after the message
> "changing root device to fd0c panic:
>  double fault"
> 
> I read in a FreeBSD related newsgroup that you haven't got such
> error in your test computers. Well, if this helps, the computer I'm
> trying to use is an AMD1 33 with 48mb of RAM, 3 H.D. IDE (the
> controller is included in the motherboard)

There's the problem - you have 48MB of RAM and something very very
mysterious which has happened to FreeBSD twixt 2.2.1 and 2.2.2 makes
it fail with just that exact memory size.  Given the popularity of
16MB simms, it also explains why none of us have seen it since we
typically have either 16MB, 32MB or 64MB of memory in our systems. :)

Some things to try in helping us debug this a little:

1. Boot the 2.2.2 boot floppy and when it comes to the first menu which
   asks you whether or not you want to go into the kernel configuration
   editor, choose the "experts only" CLI mode option.  Now type:

	iosize npx0 32768
	visual
	<and do your visual kernel configuration as normal then exit>

And see if you can get through to the installation.  If so, go to step 3.

2. If the above does not work, physically remove all but 32MB of memory
   from your machine and then boot the boot floppy.  Unless your problem
   is totally weird and something we've not seen at all before, you should
   now be able to go on to step 3.

3. Complete the installation and then boot off your hard disk.  This
   boot should work fine, since you are no longer using the memory
   filesystem that the installation uses and which seems to interact
   badly with these memory size issues to create the failure you saw.

This note has also been added to ERRATA.TXT in 2.2.2.

					Jordan