From owner-freebsd-current  Wed Dec  5 20:45:40 2001
Delivered-To: freebsd-current@freebsd.org
Received: from hawk.prod.itd.earthlink.net (hawk.mail.pas.earthlink.net [207.217.120.22])
	by hub.freebsd.org (Postfix) with ESMTP id CEA5B37B41B
	for <current@freebsd.org>; Wed,  5 Dec 2001 20:45:33 -0800 (PST)
Received: from dialup-209.245.132.144.dial1.sanjose1.level3.net ([209.245.132.144] helo=mindspring.com)
	by hawk.prod.itd.earthlink.net with esmtp (Exim 3.33 #1)
	id 16BqPc-00038n-00; Wed, 05 Dec 2001 20:45:32 -0800
Message-ID: <3C0EF7F4.8456D514@mindspring.com>
Date: Wed, 05 Dec 2001 20:45:40 -0800
From: Terry Lambert <tlambert2@mindspring.com>
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Galen Sampson <galen_sampson@yahoo.com>
Cc: current@freebsd.org
Subject: Re: Non-network Fatal Trap 12
References: <20011205194808.45278.qmail@web14106.mail.yahoo.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

Galen Sampson wrote:
> 
> Hello all,
> 
> Your input was most appreciated (I hadn't thought to boot to single user to run
> fsck).  When I ran fsck -p all filesystems generated output as if the
> filesystems were clean.  After attempting to bring it to multi-user mode it
> passes through init scripts, but panics where the login prompt should be.  I've
> never experienced filesystem corruption before.  I'm curious as to what the
> cause of my problem is.  Does this sound like filesystem corruption, or some
> other problem?

This sounds like a new kernel with old modules, or vice versa.

The easiest way to deal with this and identify the culprit is to
boot single user mode.  If it fails:

o	Get to the boot countdown prompt
o	Hit a key to interrupt
o	List everything loaded
o	Unload everything
o	Load only the kernel
o	Boot with -s

If it still doesn't work, it's your kernel or RAM.

If it works, then it is one of your modules.

If it didn't fail booting to single user mode, but only fails to
go to multiuser, then:

o	Manually run through the startup scripts
o	Note where it panics
o	Take that out: it's broken.
o	You're done

-- Terry

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