From owner-freebsd-current@FreeBSD.ORG  Mon Apr 12 15:32:47 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 8E2A916A4CE
	for <current@freebsd.org>; Mon, 12 Apr 2004 15:32:47 -0700 (PDT)
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu
	[128.208.78.105])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 614A743D4C
	for <current@freebsd.org>; Mon, 12 Apr 2004 15:32:47 -0700 (PDT)
	(envelope-from sgk@troutmask.apl.washington.edu)
Received: from troutmask.apl.washington.edu (localhost [127.0.0.1])
	i3CMWltG060393;	Mon, 12 Apr 2004 15:32:47 -0700 (PDT)
	(envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)i3CMWlYX060392;
	Mon, 12 Apr 2004 15:32:47 -0700 (PDT)	(envelope-from sgk)
Date: Mon, 12 Apr 2004 15:32:47 -0700
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Chris Shenton <chris@shenton.org>
Message-ID: <20040412223247.GA59079@troutmask.apl.washington.edu>
References: <86ekqtcemd.fsf@PECTOPAH.shenton.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <86ekqtcemd.fsf@PECTOPAH.shenton.org>
User-Agent: Mutt/1.4.1i
cc: current@freebsd.org
Subject: Re: 5.2-CURRENT yesterday: GIANT-LOCKED, lock order reversal
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: Mon, 12 Apr 2004 22:32:47 -0000

On Mon, Apr 12, 2004 at 01:03:54PM -0400, Chris Shenton wrote:
> Built world and new kernel from yesterday's CVSup and noticed a bunch
> of [GIANT-LOCKED] in the bootup.  Then, after it came up, it spewed
> errors about lock order reversal. I'm not clueful enough to understand
> what it's trying to tell me :-(
> 
> Here's a "uname -a" info, then the dmesg output with GIANT-LOCK and
> lock order reversal. Should I be concerned? Any work-arounds?  Thanks.
> 

GIANT-LOCK is simply an anotation that a device driver is
still under the GAINT lock.   Until a few weeks ago, drivers
were reporting [MPSAFE] to note the driver was now under
a finer grain lock.

The LOR you reported has been reported previous.  

-- 
Steve