From owner-freebsd-current Thu Jun 17 11:27:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id 6C1CB14BD0 for ; Thu, 17 Jun 1999 11:27:40 -0700 (PDT) (envelope-from Studded@gorean.org) Received: from localhost (doug@localhost) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id LAA03932; Thu, 17 Jun 1999 11:27:37 -0700 (PDT) (envelope-from Studded@gorean.org) Date: Thu, 17 Jun 1999 11:27:37 -0700 (PDT) From: Studded X-Sender: doug@dt054n86.san.rr.com To: Studded Cc: freebsd-current@freebsd.org, "David O'Brien" Subject: Re: Heavily loaded amd gets stuck In-Reply-To: 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 On Wed, 16 Jun 1999, Studded wrote: > Running the test with the "proto=tcp" option gave the same results > in the kernel backtrace as did "proto=udp," namely: > > Xresume1() > --- interrupt > splx() > nfs_nget() > mountnfs() > nfs_mount() > mount() > syscall() > Xint0x80_syscall() > > The last 6 are identical in all the tests I've done. At someone else's suggestions I tried the following: /defaults type:=nfs;opts:=rw,nosuid,vers=3,intr,proto=udp,noconn still with no joy. I did get a slighly different kernel trace though: Xresume1() --- interrupt vop_nounlock() vop_defaultop() nfs_inactive() vrele() Then the same last 6 functions as in all the other tests. Next step, I'm going to upgrade the box to -current and see if that helps. Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message