From owner-freebsd-amd64@FreeBSD.ORG  Wed Apr  5 04:59:26 2006
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
X-Original-To: freebsd-amd64@freebsd.org
Delivered-To: freebsd-amd64@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id AFE6E16A400
	for <freebsd-amd64@freebsd.org>; Wed,  5 Apr 2006 04:59:26 +0000 (UTC)
	(envelope-from taob@luxography.ca)
Received: from as2.dm.egate.net (shell1.dm.egate.net [216.235.15.210])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 671AB43D45
	for <freebsd-amd64@freebsd.org>; Wed,  5 Apr 2006 04:59:26 +0000 (GMT)
	(envelope-from taob@luxography.ca)
Received: by as2.dm.egate.net (Postfix, from userid 8159)
	id 6AC1C4B43; Wed,  5 Apr 2006 00:59:25 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by as2.dm.egate.net (Postfix) with ESMTP id 5DE094B36
	for <freebsd-amd64@freebsd.org>; Wed,  5 Apr 2006 00:59:25 -0400 (EDT)
Date: Wed, 5 Apr 2006 00:59:25 -0400 (EDT)
From: Brian Tao <taob@luxography.ca>
X-X-Sender: taob@as2.dm.egate.net
To: freebsd-amd64@freebsd.org
In-Reply-To: <20060403205241.C3698-100000@as2.dm.egate.net>
Message-ID: <20060405005220.X3698-100000@as2.dm.egate.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Re: Disk I/O-related panics in 6.0-RELEASE?
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2006 04:59:26 -0000

On Mon, 3 Apr 2006, Brian Tao wrote:
>
> I'll have to check in on it tomorrow and slap a serial console on
> it.  If 6.1 isn't much better, I'll try putting an i386 kernel on it
> instead and see if I can rule out flakey hardware.

    No go with RELENG_6... kernel panic during a buildworld attempt
with the new kernel.  Additionally, on reboot, the background fsck
eventually hangs in disk wait on snaplk.  The system slowly becomes
inaccessible as more and more processes access the filesystem and also
hang on snaplk.

    There doesn't seem to be anything for savecore to dump when the
system tries to come back up either.  Any other information I should
be providing, beyond what is included in the tar file below (kernel
config file, dmesg, kgdb output)?

http://www.luxography.ca/tmp/amd64_panics.tgz

-- 
Brian Tao, Luxography
http://www.luxography.ca/ (main)
http://blog.luxography.ca/ (blog)
"The art of light"