From owner-freebsd-questions@FreeBSD.ORG  Sat Jul 12 12:34:03 2003
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4AC6537B404
	for <freebsd-questions@freebsd.org>;
	Sat, 12 Jul 2003 12:34:03 -0700 (PDT)
Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39])
	by mx1.FreeBSD.org (Postfix) with ESMTP id A1AA443F93
	for <freebsd-questions@freebsd.org>;
	Sat, 12 Jul 2003 12:34:02 -0700 (PDT)
	(envelope-from freebsd-questions-local@be-well.no-ip.com)
Received: from be-well.ilk.org (be-well.no-ip.com[66.30.200.37])
          by comcast.net (rwcrmhc13) with ESMTP
          id <2003071219340201500gj7n2e>; Sat, 12 Jul 2003 19:34:02 +0000
Received: from be-well.ilk.org (lowellg.ne.client2.attbi.com [66.30.200.37]
	(may be forged))
	by be-well.ilk.org (8.12.9/8.12.9) with ESMTP id h6CJXulA070619;
	Sat, 12 Jul 2003 15:33:56 -0400 (EDT)
	(envelope-from freebsd-questions-local@be-well.no-ip.com)
Received: (from lowell@localhost)
	by be-well.ilk.org (8.12.9/8.12.6/Submit) id h6CJXtXX070616;
	Sat, 12 Jul 2003 15:33:55 -0400 (EDT)
X-Authentication-Warning: be-well.ilk.org: lowell set sender to
	freebsd-questions-local@be-well.ilk.org using -f
Sender: lowell@be-well.no-ip.com
To: freebsd-questions@freebsd.org
References: <20030710032006.V1031@metafocus.net>
From: Lowell Gilbert <freebsd-questions-local@be-well.no-ip.com>
In-Reply-To: <20030710032006.V1031@metafocus.net>
Message-ID: <44u19rk09o.fsf@be-well.ilk.org>
Lines: 16
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
cc: Dave <mudman@metafocus.net>
Subject: Re: Lock Order Reversal (5.1 CUR kern)
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: freebsd-questions@freebsd.org
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
Date: Sat, 12 Jul 2003 19:34:03 -0000
X-Original-Date: 12 Jul 2003 15:33:55 -0400
X-List-Received-Date: Sat, 12 Jul 2003 19:34:03 -0000

Dave <mudman@metafocus.net> writes:

> My thinking: the threading in the kernel for 5.1 CURRENT hasn't all the
> kinks out yet.  Does anyone know what is going on?
> 
> Before rushing off to the FreeBSD people with it though, they 1) might
> already be aware, and 2) maybe I don't understand the error entirely and
> its a problem with how I setup my system?
> 
> So I'm asking here I guess.

If you're going to track -CURRENT, you really should read the -CURRENT
mailing list.  Offhand, I can't see how the system map would be
getting locked in your case, but you're right that it seems to be a
bug in the threading code (DRM *is* likely to be related, since it
constitutes a separate path into "direct" memory manipulation...).