From owner-freebsd-arch  Fri Oct 13 10: 8:12 2000
Delivered-To: freebsd-arch@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
	by hub.freebsd.org (Postfix) with ESMTP
	id 4278337B502; Fri, 13 Oct 2000 10:08:10 -0700 (PDT)
Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71])
	by feral.com (8.9.3/8.9.3) with ESMTP id KAA03301;
	Fri, 13 Oct 2000 10:08:09 -0700
Date: Fri, 13 Oct 2000 10:05:06 -0700 (PDT)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: Jake Burkholder <jburkhol@home.com>
Cc: John Baldwin <jhb@FreeBSD.ORG>, arch@FreeBSD.ORG
Subject: Re: when is it safe to call msleep? 
In-Reply-To: <20001013004626.978DFBA76@io.yi.org>
Message-ID: <Pine.LNX.4.21.0010131004210.3882-100000@zeppo.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Well, no panics, but it made the i386 like the alpha (freezes up in the middle
of probing) on my 2xPPro.

-matt


> > 
> > I've been fooling around with the new lock stuff and trying to convert things
> > over, and I called msleep with an initialized MTX_DEF lock held (on my
> > pc164) during probes, but I got a panic:
> > 
> 
> Hmm.  I don't know about the panic, but the releasing of the mutex
> is probably in the wrong place if its going to be called early in
> boot, when cold is true.
> 
> Could you try this:
> 
> 
> Jake
> 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message