Return to BSD News archive
Xref: sserve comp.os.386bsd.misc:1323 comp.os.386bsd.questions:6200
Path: sserve!newshost.anu.edu.au!munnari.oz.au!ariel.ucs.unimelb.EDU.AU!ucsvc.ucs.unimelb.edu.au!lugb!latcs1!wongm
Newsgroups: comp.os.386bsd.misc,comp.os.386bsd.questions
Subject: Re: FreeBSD installation problem [still unsuccessful!]
Message-ID: <CFIHt1.E1F@latcs1.lat.oz.au>
From: wongm@latcs1.lat.oz.au (M.C. Wong)
Date: Tue, 26 Oct 1993 16:00:37 GMT
References: <CFGELv.1Hv@latcs1.lat.oz.au>
Organization: Comp Sci, La Trobe Uni, Australia
Lines: 85
In article <CFGELv.1Hv@latcs1.lat.oz.au> wongm@latcs1.lat.oz.au (M.C. Wong) writes:
>
>Hi,
> During my last installation of FreeBSD, I got to the step where I ahve
>finished with 3rd floppy, ie cpio-floppy, and let FreeBSD boot itself up
>off the hard disk (wd0), upon the first boot, it complains about 4 fsck errors
>as is mentioned in install notes, and boots itself up for the 2nd time, and
>supposed to be with a clean filesystem this time, but I got the following
>error messages.
>
>Automatic reboot in progress ...
>Bus error
>Unkown error in reboot
>Automatic reboot in progress ...
>Bus error
>Unkown error in reboot
>.
>.
>. [repeated!]
>
> ANd I realized where the problem was, ie fsck -p in .profile! So, I
>experimented booting up from kcopy-aha-floppy, and did fsck on /dev/wd0a
>and /dev/wd0e, and the conclusion is sometimes fsck fails, sometimes
>it doesn't. But most of the time when I boot up from hard disk, the fsck
>fails quite often, so I copy the fsck from kcopy-aha-floppy, and try it
>out and the conclusion was as before, sometimes it works, sometimes it
>complaints a Bus error (core dumped). I figured out that when the / is still
>read-only, a core dumped is not possible, and I am left with ambiguous error
>of Bus error, looks very much like hardware problem! So, I finally get to the
>point to copy a new fsck onto my FreeBSD /sbin, and let boot up use the new
>(fresh) fsck does its job, and I read in all of the binary and source
>distribution, and get them extracted in to proper places. But when I start up
>the system, I still have the following 2 problems :
>
> 1) fsck complains about Bus error, looks like transient problem to me ,
> why ? Can I make this problem go away permanently ?
>
> 2) Upon starting up network (from /etc/rc), I get a panic message :
>
> Starting network
> vm_fault (fe11e0000, fe345000, 3, 0)->1 type c, code 2
> trap type 12 code = 2 eip = fe02287d cs = 8 eflags = 10202 cr2 fe345000
> cpl 1a
> panic : trap
> Syncing disks ...
>
> I tried rebooting a few times, but I keep getting problem 2), can someone
>help please ?
>
> Well, I have been persistent enough to stay up with FreeBSD so far, and I
>hope you guys can just get me onto the right path, by baring with my
>unsuccessful installtion, and I will be right!
>
> Thanks in advance, and email replies please!
>
>- wongm@latcs1.lat.oz.au (M.C Wong)
>--
>- wongm@latcs1.lat.oz.au
Hi,
Now I am a bit confused by the installation problem with FreeBSD. I tried
yet another time with installing FreeBSD on SCSI disk only (ie on sd0), but
I still keep getting the same problem as before, ie fsck core dump error!
That actually means, it could not be just the wd driver bug, I might be wrong.
The error 2 (panic) above is again experienced! Yes, ifconfig (as suggested
by Rod Grimes) is somehow corrupted and causes panic. OTOH, one of the guys
pointed out to me that the panic during network startup is caused by my
3c503 was first probe and set up by ed0, and followed by is0 (another driver)
again, and that mess up the thing, and I was suggested to rebuild a kernel
to comment out the is0 line in the config file. I tried this on my previous
installtion on wd0, but guess what, the 386bsd which is smaller than the
original 386bsd and 386bsd.GENERICAH can't be loaded during boot with complaint
of size too big. So I tried loading 386bsd.GENERICAH (which is > my 386bsd),
and miracly it boots! So, why can't the 386bsd I built be loaded ?
Now I am really confused and frustated and tired, yes, after many sleepless
nights of trial and errors, it seems as if my FreeBSD installation is heading
no where at all!
Have someone experienced what I did at all ?
--
- wongm@latcs1.lat.oz.au