From owner-freebsd-current@FreeBSD.ORG Wed Apr 14 10:16:11 2004 Return-Path: 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 8AE2216A4CE for ; Wed, 14 Apr 2004 10:16:11 -0700 (PDT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3DCB043D45 for ; Wed, 14 Apr 2004 10:16:11 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: from freebsd.org (junior-wifi.samsco.home [192.168.0.11]) by pooker.samsco.org (8.12.10/8.12.10) with ESMTP id i3EHIEc8097281; Wed, 14 Apr 2004 11:18:15 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <407D71D7.7000803@freebsd.org> Date: Wed, 14 Apr 2004 11:16:07 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040304 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Chris Shenton References: <86ekqtcemd.fsf@PECTOPAH.shenton.org> In-Reply-To: <86ekqtcemd.fsf@PECTOPAH.shenton.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Apr 2004 17:16:11 -0000 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 :-( The GIANT-LOCKED messages are normal and flag drivers that have not been converted to use their own locks. The Lock Order Reversals are a bug that is known and will hopefully be fixed soon. Btw, I think that the GIANT-LOCKED and FAST interrupt messages will go behind bootverbose before 5.3. Scott