From owner-freebsd-current@FreeBSD.ORG  Thu May 29 15:07:00 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 644B737B401
	for <freebsd-current@freebsd.org>;
	Thu, 29 May 2003 15:07:00 -0700 (PDT)
Received: from gravy.homeunix.net (pool-151-197-48-53.phil.east.verizon.net
	[151.197.48.53])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6633243F3F
	for <freebsd-current@freebsd.org>;
	Thu, 29 May 2003 15:06:59 -0700 (PDT)
	(envelope-from bleez@verizon.net)
Received: from gravy.homeunix.net (gravy.homeunix.net [192.168.1.2])
	by gravy.homeunix.net (8.12.9/8.12.9) with ESMTP id h4TM6waf000475;
	Thu, 29 May 2003 18:06:58 -0400 (EDT)
	(envelope-from bleez@verizon.net)
Date: Thu, 29 May 2003 18:06:58 -0400 (EDT)
From: Bryan Liesner <bleez@verizon.net>
To: "Nick H." <nickh@supportteam.net>
In-Reply-To: <000901c32625$6fc89e50$0402a8c0@dotnet>
Message-ID: <20030529180400.W474@gravy.homeunix.net>
References: <20030529164240.X769@gravy.homeunix.net>
	<000901c32625$6fc89e50$0402a8c0@dotnet>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-current@freebsd.org
Subject: Re: panic: kern/52718
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 29 May 2003 22:07:00 -0000

On Thu, 29 May 2003, Nick H. wrote:

> Just out of curosity...  I had this same error a while back on one of my
> boxes.  I ended up booting to a recovery cd and running an fsck_ffs on it
> and it fixed the problem.  Mine would get to a login and *WHAM* it's dead.
> Worth a shot to see if that fixes your problem or not....
>

Tried that, and it still panics.  Way before we get to a login, at the
point where it starts to set up the disks...

Thanks!