From owner-freebsd-current@FreeBSD.ORG Wed Jun 1 05:44:22 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org 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 CD5CC16A41C; Wed, 1 Jun 2005 05:44:22 +0000 (GMT) (envelope-from kuriyama@imgsrc.co.jp) Received: from black.imgsrc.co.jp (black.imgsrc.co.jp [210.226.20.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F89743D54; Wed, 1 Jun 2005 05:44:22 +0000 (GMT) (envelope-from kuriyama@imgsrc.co.jp) Received: from localhost (localhost [127.0.0.1]) by black.imgsrc.co.jp (Postfix) with ESMTP id DA4D450CFD; Wed, 1 Jun 2005 14:44:20 +0900 (JST) Received: from black.imgsrc.co.jp (black.imgsrc.co.jp [IPv6:2001:218:422:2::9999]) by black.imgsrc.co.jp (Postfix) with ESMTP id 96A0650CFC; Wed, 1 Jun 2005 14:44:18 +0900 (JST) Date: Wed, 01 Jun 2005 14:44:18 +0900 Message-ID: <7msm02k4wd.wl%kuriyama@imgsrc.co.jp> From: Jun Kuriyama To: Current , jeff@FreeBSD.org User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/21.3 (i386--freebsd) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd 0.1 Cc: Subject: Hang in NFS client operation X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 01 Jun 2005 05:44:23 -0000 Since 2005-04-09 (*), my (-current) box sometimes hang at NFS client operation (usually CVS update from readonly NFS mounted repository. Server is 5.3R). Is there something I can help debugging about this issue? ----- db> ps pid proc uid ppid pgrp flag stat wmesg wchan cmd 7778 c3b73e00 103 7776 7767 0004000 [SLPQ nfsreq 0xc3d87e80][SLP] cvs ... db> trace 7778 Tracing pid 7778 tid 100124 td 0xc3b6b300 sched_switch(c3b6b300,0,1) at sched_switch+0x14f mi_switch(1,0,c3b6b300,1,c3b6b300) at mi_switch+0x1ba sleepq_switch(c3d87e80) at sleepq_switch+0x133 sleepq_wait(c3d87e80,0,c3bc5298,0,c3d87e80) at sleepq_wait+0xb msleep(c3d87e80,c0721a60,53,c06c28fc,0) at msleep+0x356 nfs_reply(c3d87e80,0,f,0,c3b6b300) at nfs_reply+0x23c nfs_request(c4d69aa0,c3eb1200,3,c3b6b300,c3bf0d80) at nfs_request+0x3c1 nfs_lookup(ecf93bd8) at nfs_lookup+0x2d8 VOP_LOOKUP_APV(c06f8ba0,ecf93bd8) at VOP_LOOKUP_APV+0x38 lookup(ecf93c68,ecf93c14,0,c3b6b300,ecf93c90) at lookup+0x431 namei(ecf93c68,c3bf0d80,c3dd8e00,80c3080,0) at namei+0x396 kern_access(c3b6b300,80c3080,0,4,ecf93d30) at kern_access+0x6a access(c3b6b300,ecf93d04,2,2d7,286) at access+0x15 syscall(3b,bfbf003b,bfbf003b,80c3080,80de8c0) at syscall+0x2b3 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (33, FreeBSD ELF32, access), eip = 0x282e6bc7, esp = 0xbfbfe47c, ebp = 0xbfbfe498 --- ----- (*) I tried to find actual commit by using binary search: > Modified files: > sys/kern vfs_lookup.c > Log: > - If we vrele() a dvp while the child is locked we can potentially > deadlock > when vrele() acquires the directory lock in the wrong order. Fix > this > via the following changes: > ... -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project