From owner-freebsd-questions  Sat Jul 26 23:55:45 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id XAA20226
          for questions-outgoing; Sat, 26 Jul 1997 23:55:45 -0700 (PDT)
Received: from gatekeeper.barcode.co.il (gatekeeper.barcode.co.il [192.116.93.17])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA20221
          for <freebsd-questions@FreeBSD.ORG>; Sat, 26 Jul 1997 23:55:38 -0700 (PDT)
Received: (from smap@localhost) by gatekeeper.barcode.co.il (8.8.5/8.6.12) id JAA24558; Sun, 27 Jul 1997 09:54:54 +0300 (IDT)
X-Authentication-Warning: gatekeeper.barcode.co.il: smap set sender to <nadav@barcode.co.il> using -f
Received: from localhost.barcode.co.il(127.0.0.1) by gatekeeper.barcode.co.il via smap (V1.3)
	id sma024549; Sun Jul 27 09:54:20 1997
Message-ID: <33DAF038.77D7@barcode.co.il>
Date: Sun, 27 Jul 1997 09:52:40 +0300
From: Nadav Eiron <nadav@barcode.co.il>
X-Mailer: Mozilla 3.0 (X11; I; SunOS 5.5 sun4m)
MIME-Version: 1.0
To: Doug White <dwhite@resnet.uoregon.edu>
CC: Damien DIXSAUT <damien@cristal.cristal.asso.fr>,
        freebsd-questions@FreeBSD.ORG
Subject: Re: Problem with 2.2.2 boot disk
References: <Pine.BSF.3.96.970726124006.4628N-100000@localhost>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Doug White wrote:
> 
> On Fri, 25 Jul 1997, Damien DIXSAUT wrote:
> 
> >    When I boot with 2.2.2 boot disk, everything goes well (kernel visual
> > configuration, where I disable all devices I don't use, beginning of
> > boot...) but when it comes to 'changing root device to fd0c', I get 'Panic:
> > double fault  Syncing disks' followed by a system hang !
> >
> >    I tried all sorts of configurations, and this system works VERY well
> > with version 2.1.5, 2.1.7 and 2.2.1.
> >
> >    Any idea ? Thanks for your help !
> 
> There are some as of yet unknown problems in 2.2.2 that causes this to
> occur.  You might try using a 2.2-STABLE boot floppy and reseting it to
> point to 2.2.2-RELEASE.

It might be better the other way around. I had a similar problem with
-STABLE boot disks ( at least up to 970708). The cure was to boot 2.2.1
boot disk and point it to the STABLE SNAP I wanted to install... There
are also reports of 3.0-CURRENT boot disks giving better results.

> 
> Doug White                              | University of Oregon
> Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
> http://gladstone.uoregon.edu/~dwhite    | Computer Science Major
> Spam routed to /dev/null by Procmail    | Death to Cyberpromo
Nadav