From owner-freebsd-current Wed Jun 16 18:32:53 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 1BFD514C05 for ; Wed, 16 Jun 1999 18:32: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 SAA27167; Wed, 16 Jun 1999 18:32:36 -0700 (PDT) (envelope-from Studded@gorean.org) Date: Wed, 16 Jun 1999 18:32:36 -0700 (PDT) From: Studded X-Sender: doug@dt054n86.san.rr.com To: freebsd-current@freebsd.org Cc: "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 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. Thanks again, Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message