From owner-freebsd-current@FreeBSD.ORG Tue Dec 9 21:32:21 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2198716A4CE; Tue, 9 Dec 2003 21:32:21 -0800 (PST) Received: from white.imgsrc.co.jp (ns.imgsrc.co.jp [210.226.20.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id E4DD443D2B; Tue, 9 Dec 2003 21:32:18 -0800 (PST) (envelope-from kuriyama@imgsrc.co.jp) Received: from localhost (localhost [127.0.0.1]) by white.imgsrc.co.jp (Postfix) with ESMTP id B768928408E; Wed, 10 Dec 2003 14:32:17 +0900 (JST) Received: from black.imgsrc.co.jp (black.imgsrc.co.jp [2001:218:422:2::130]) by white.imgsrc.co.jp (Postfix) with ESMTP id A949028408B; Wed, 10 Dec 2003 14:32:16 +0900 (JST) Received: from black.imgsrc.co.jp (black.imgsrc.co.jp [2001:218:422:2::130]) by black.imgsrc.co.jp (Postfix) with ESMTP id C51041E4A62; Wed, 10 Dec 2003 14:32:15 +0900 (JST) Date: Wed, 10 Dec 2003 14:32:15 +0900 Message-ID: <7mekvd44rk.wl@black.imgsrc.co.jp> From: Jun Kuriyama To: Don Lewis In-Reply-To: <200312100341.hBA3fBeF051423@gw.catspoiler.org> References: <7mhe094ajj.wl@black.imgsrc.co.jp> <200312100341.hBA3fBeF051423@gw.catspoiler.org> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 Emacs/21.3 (i386--freebsd) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by AMaViS snapshot-20020531 cc: freebsd-current@FreeBSD.org Subject: Re: 5.2-RC: vnode_pager_alloc: 0xc6bc66f0 is not locked but should be X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2003 05:32:21 -0000 At Tue, 9 Dec 2003 19:41:11 -0800 (PST), Don Lewis wrote: > I ran into this problem in 5.2-CURRENT. It has sinced been fixed there, > in sys/vm/mmap.c 1.175. I believe this is under consideration for > mergeing into RELENG_5_2. In the mean time, you can get under way again > by setting vfs_badlock_panic and vfs_badlock_print to 0 in the ddb and > continuing. This panic will also go away if you rebuild your kernel > with vnode lock checking disabled. Thanks! I've applied the diff between 1.174 (RELENG_5_2) and 1.175 and it works fine. -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project