From owner-freebsd-current@FreeBSD.ORG  Wed Aug 11 17:21:32 2004
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 3CBB316A4CE; Wed, 11 Aug 2004 17:21:32 +0000 (GMT)
Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 30AD943D31; Wed, 11 Aug 2004 17:21:32 +0000 (GMT)
	(envelope-from dwhite@gumbysoft.com)
Received: by carver.gumbysoft.com (Postfix, from userid 1000)
	id 24CDF72DF2; Wed, 11 Aug 2004 10:21:32 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by carver.gumbysoft.com (Postfix) with ESMTP
	id 22A7772DB5; Wed, 11 Aug 2004 10:21:32 -0700 (PDT)
Date: Wed, 11 Aug 2004 10:21:32 -0700 (PDT)
From: Doug White <dwhite@gumbysoft.com>
To: Terrence Koeman <root@mediamonks.net>
In-Reply-To: <200408111527566.SM01804@manrikigusari>
Message-ID: <20040811101859.P99067@carver.gumbysoft.com>
References: <200408111527566.SM01804@manrikigusari>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-current@FreeBSD.org
cc: 'John Baldwin' <jhb@FreeBSD.org>
Subject: RE: Lock order reversal in 5.2-CURRENT
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: Wed, 11 Aug 2004 17:21:32 -0000

On Wed, 11 Aug 2004, Terrence Koeman wrote:

> I think something else is wrong, as I get different lock order reversals and
> some other errors that all lockup the box. Earlier I had a corrupted cc
> binary after a buildworld.
>
> Everything points to a hardware failure somewhere, but I already switched
> the hardware before this happened, I swapped RAID arrays in identical
> machines, and the machine where -CURRENT runs on now was a production server
> that ran 4.9/4.10-STABLE for months under heavy load without any problems
> whatsoever.
>
> The following is what I got today:
>
> Second bad
> /: bad dir ino 16110954 at offset 24: mangled entry
> panic: ufs_dirbad: bad dir

Your RAID is doing a really good job of corrupting your data. :)  What
RAID controller and volume layout are you using?
> Fatal trap 18: integer divide fault while in kernel mode

This looks more serious .. you may have a bad CPU, memory, or some other
critical component.

-- 
Doug White                    |  FreeBSD: The Power to Serve
dwhite@gumbysoft.com          |  www.FreeBSD.org