From owner-freebsd-bugs Tue Jul 10 10:14:41 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from midten.fast.no (midten.fast.no [213.188.8.11]) by hub.freebsd.org (Postfix) with ESMTP id CA05137B403 for ; Tue, 10 Jul 2001 10:14:29 -0700 (PDT) (envelope-from Tor.Egge@fast.no) Received: from fast.no (IDENT:tegge@midten.fast.no [213.188.8.11]) by midten.fast.no (8.9.3/8.9.3) with ESMTP id TAA11209; Tue, 10 Jul 2001 19:14:14 +0200 (CEST) Message-Id: <200107101714.TAA11209@midten.fast.no> To: neteng@tide.iadfw.net Cc: freebsd-bugs@FreeBSD.ORG Subject: re: kern/26224: VFS Panic/SMP/CFLOW(HEAVY network)/Heavy NFS From: Tor.Egge@fast.no In-Reply-To: Your message of "Tue, 10 Jul 2001 06:20:01 -0700 (PDT)" References: <200107101320.f6ADK1152861@freefall.freebsd.org> X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 10 Jul 2001 19:14:14 +0200 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The panic message and the stack backtrace indicates that a process has gone to sleep while holding a vnode interlock. When pagedaemon tries to obtain the vnode interlock (in vput() called from vm_pageout()) the machine will either hang (if the vnode interlock was held by the other CPU) or panic (if the vnode interlock was held by the same CPU). Use ps axlww -N kernel.debug.76 -M vmcore.76 to list the processes on the system when it died. Use gdb to list the kernel stack of each process. The offending process probably has an uncommon WCHAN string. - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message