From owner-freebsd-current Thu Jun 13 16:21:24 2002 Delivered-To: freebsd-current@freebsd.org Received: from mta5.snfc21.pbi.net (mta5.snfc21.pbi.net [206.13.28.241]) by hub.freebsd.org (Postfix) with ESMTP id 9D5A937B411; Thu, 13 Jun 2002 16:21:18 -0700 (PDT) Received: from FreeBSD.org ([63.193.112.125]) by mta5.snfc21.pbi.net (iPlanet Messaging Server 5.1 (built May 7 2001)) with ESMTP id <0GXN0079SXWQGN@mta5.snfc21.pbi.net>; Thu, 13 Jun 2002 14:19:38 -0700 (PDT) Date: Thu, 13 Jun 2002 14:19:52 -0700 From: Jeffrey Hsu Subject: Re: Crash after world/kernel upgrade To: jhb@freebsd.org, sidcarter@symonds.net Cc: current@freebsd.org Message-id: <0GXN0079TXWQGN@mta5.snfc21.pbi.net> MIME-version: 1.0 X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Duplicate inp warnings occur whenever 2 inp locks are held, even though they're on different inps, because all the inp locks are named "inp". I've investigated a couple of these already and they were all places where we intended to grab two inp locks. So, for the most part, these warning are harmless. As John said though, panics are serious, so if you get any of those, please report them to me directly, as I only monitor this list periodically. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message