From owner-freebsd-current Tue Mar 2 15:29:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 0C38914E1E for ; Tue, 2 Mar 1999 15:29:44 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id SAA10270; Tue, 2 Mar 1999 18:29:32 -0500 (EST) Date: Tue, 2 Mar 1999 18:29:31 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Alan Cox Cc: current@freebsd.org Subject: Re: lockmgr panic with mmap() In-Reply-To: <19990302172813.A91146@nonpc.cs.rice.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 2 Mar 1999, Alan Cox wrote: > On Tue, Mar 02, 1999 at 06:16:50PM -0500, Brian Feldman wrote: > > > > Where exactly does thrd_sleep come in, since that's where the program locks > > up now? Can't be killed, of course... > > > > The lock manager isn't bright enough to detect that the process > already holds a read lock when it attempts to get the write lock. > Thus, you get the "thrd_sleep" instead of a panic. > > In short, same bug, different symptoms. > Ahh, makes sense. Quick question: how in the heck did you learn this whole VM system? Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message