From owner-freebsd-questions  Sun Jul 27 09:05:28 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id JAA10708
          for questions-outgoing; Sun, 27 Jul 1997 09:05:28 -0700 (PDT)
Received: from jason04.u.washington.edu (root@jason04.u.washington.edu [140.142.78.5])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA10698
          for <freebsd-questions@FreeBSD.ORG>; Sun, 27 Jul 1997 09:05:21 -0700 (PDT)
Received: from saul6.u.washington.edu (root@saul6.u.washington.edu [140.142.82.1])
          by jason04.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP
	  id JAA30596; Sun, 27 Jul 1997 09:05:15 -0700
Received: from s5-25-199.student.washington.edu (S5-25-199.student.washington.edu [128.95.25.199])
          by saul6.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with SMTP
	  id JAA26399; Sun, 27 Jul 1997 09:05:15 -0700 (PDT)
Message-Id: <3.0.2.32.19970727160944.007bea60@jcwells.deskmail.washington.edu>
X-Sender: jcwells@jcwells.deskmail.washington.edu
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.2 (32)
Date: Sun, 27 Jul 1997 16:09:44 +0000
To: Damien DIXSAUT <damien@cristal.cristal.asso.fr>
From: Jason Wells <jcwells@u.washington.edu>
Subject: Re: Problem with 2.2.2 boot disk
Cc: freebsd-questions@FreeBSD.ORG
In-Reply-To: <33DAF038.77D7@barcode.co.il>
References: <Pine.BSF.3.96.970726124006.4628N-100000@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>> >    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.

Yep. I used a 3.0-CURRENT floppy to install 2.2.2-RELEASE system. I had the
very same problem. The CURRENT disk solved it.

Jason Wells
 __   __
/ 0\ / 0\         Thank you * Highperformance.net            
     )     Wannabe Sysadmin * The homeless domain            
)-------(       Jason Wells * "Pardon me sir, spare some bandwidth?"  
 \_____/