From owner-freebsd-current  Sun Sep 12 11:29:38 1999
Delivered-To: freebsd-current@freebsd.org
Received: from freebsd.netcom.com. (freebsd.netcom.com [198.211.79.3])
	by hub.freebsd.org (Postfix) with SMTP id 3EE5B14A0E
	for <freebsd-current@freebsd.org>; Sun, 12 Sep 1999 11:29:32 -0700 (PDT)
	(envelope-from bugs@freebsd.netcom.com)
Received: by freebsd.netcom.com. (SMI-8.6/SMI-SVR4)
	id KAA00268; Sun, 12 Sep 1999 10:26:26 -0500
From: bugs@freebsd.netcom.com (Mark Hittinger)
Message-Id: <199909121526.KAA00268@freebsd.netcom.com.>
Subject: re: Help! System won't boot the normal way after make world
To: freebsd-current@freebsd.org
Date: Sun, 12 Sep 1999 10:26:26 -0500 (CDT)
X-Mailer: ELM [version 2.4 PL25]
Content-Type: text
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


> Using FreeBSD 4.0 current for quite some time
> and staying current with cvsup work fine for me a few months.
> But today shit hits the fan, after a make world my system won't boot without
> errors and manual interference..

Check your dmesg for the ethernet interfaces that come up when you boot
your kernel.  I had a similar problem last week where my system drive got
so corrupted I couldn't use it - had to reinstall and start over.  Are you
using a 3c5x9 etherlinkIII card (ep0)?  Check to see if some of the other
ethernet interfaces that aren't there are being incorrectly recognized and
enabled.

In order to use the latest kernel I have to "boot -c" and disable ed0
otherwise I get major sig11's, kernel hangs, and corrupted disks.  Disabling
the ethernet drivers that don't exist on my configuration makes the bad
man stop - although I've already re-installed because of the corruption
damage.  You may need to consider that if your situation is similar to
mine.

Later

Mark Hittinger
Mindspring/Netcom/Dallas
bugs@freebsd.netcom.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message