From owner-freebsd-current Tue Mar 2 15:29: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 6982114E6D for ; Tue, 2 Mar 1999 15:28:32 -0800 (PST) (envelope-from alc@cs.rice.edu) Received: from nonpc.cs.rice.edu (nonpc.cs.rice.edu [128.42.1.219]) by cs.rice.edu (8.9.0/8.9.0) with ESMTP id RAA12990; Tue, 2 Mar 1999 17:28:14 -0600 (CST) Received: (from alc@localhost) by nonpc.cs.rice.edu (8.9.2/8.7.3) id RAA32070; Tue, 2 Mar 1999 17:28:14 -0600 (CST) Date: Tue, 2 Mar 1999 17:28:13 -0600 From: Alan Cox To: Brian Feldman Cc: current@freebsd.org Subject: Re: lockmgr panic with mmap() Message-ID: <19990302172813.A91146@nonpc.cs.rice.edu> References: <19990302113704.B90473@nonpc.cs.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: ; from Brian Feldman on Tue, Mar 02, 1999 at 06:16:50PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message