From owner-freebsd-questions Sat Jul 26 12:40:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA15972 for questions-outgoing; Sat, 26 Jul 1997 12:40:59 -0700 (PDT) Received: from gdi.uoregon.edu (cisco-ts14-line14.uoregon.edu [128.223.150.180]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA15967 for ; Sat, 26 Jul 1997 12:40:55 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.8.5) with SMTP id MAA04729; Sat, 26 Jul 1997 12:40:44 -0700 (PDT) Date: Sat, 26 Jul 1997 12:40:43 -0700 (PDT) From: Doug White X-Sender: dwhite@localhost Reply-To: Doug White To: Damien DIXSAUT cc: freebsd-questions@FreeBSD.ORG Subject: Re: Problem with 2.2.2 boot disk In-Reply-To: <199707242354.BAA00309@cristal.cristal.asso.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 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. 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