*BSD News Article 97872


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mira.net.au!news.netspace.net.au!news.mel.connect.com.au!munnari.OZ.AU!spool.mu.edu!uwm.edu!vixen.cso.uiuc.edu!not-for-mail
From: Vlad <roubtsov@uiuc.edu>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: 2.2.2 floppies/newer/boot.flp: double fault
Date: Tue, 17 Jun 1997 03:42:42 -0500
Organization: Baphomet's Throne
Lines: 32
Message-ID: <33A64DF5.41C67EA6@uiuc.edu>
NNTP-Posting-Host: llama-4.slip.uiuc.edu
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 3.0 (X11; I; FreeBSD 2.1.5-RELEASE i386)
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:43017

Hi:
	Haven't seen messages related to this lately, so maybe I can add
another description of a problem with v2.2.x installation:

scenario:

- downloaded the required 2.2.2 dist files to a DOS partition;
- made a bootable floppy from the image in floppies/newer;
- rebooted; edited the kernel config in visual mode; went on;
- the kernel loaded from the floppy detects all hardware correctly, but
at the very end says something like:
"switching root to fd0c
 panic: double fault",
after which it tries to sync disks and hangs.

The fault occurs just before the sysinstall tool would normally be
loaded. It also occurs regardless of any previous config manipulations.
An attempt to use the older image from floppies/ fails in the same way.
I have verified that the downloaded boot.flp image had the correct
checksum and the floppy in question was error-free.

Finally, I had to use the v2.2.1 boot.flp image with my downloaded 2.2.2
distribution. This worked Ok and now I have v2.2.2 on my SCSI disk with
no problems except for those already reported by others.

I have been a v2.1.5 user for quite some time with no problems and went
through several installs of similar kind -- never a single problem
during this kind of procedure. Any idea what is the difference between
v2.2.1 and 2.2.2 boot.flp images that would cause the latter one to
generate the exception?

Vlad.