From owner-freebsd-current Fri Dec 22 21:27:14 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 22 21:27:12 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id BBFFE37B400 for ; Fri, 22 Dec 2000 21:27:08 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id VAA24751 for ; Fri, 22 Dec 2000 21:27:17 -0800 Date: Fri, 22 Dec 2000 21:27:08 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: current@freebsd.org Subject: is it possible to have a NULL procp for an NFS request? 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 I had a panic just now: db> t tprintf() at tprintf+0x7c nfs_msg() at nfs_msg+0x28 nfs_timer() at nfs_timer+0x1fc softclock() at softclock+0x4f4 sithd_loop() at sithd_loop+0x18c exception_return() at exception_return This is where it's saying the server isn't responding... and as best as I can decode the assembly, the first argument to tprintf is NULL (a null procp) which is passed straight through as rep->r_procp in nfs_msg. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message