Date: Thu, 17 Jun 1999 11:27:37 -0700 (PDT) From: Studded <Studded@gorean.org> To: Studded <Studded@gorean.org> Cc: freebsd-current@freebsd.org, "David O'Brien" <obrien@NUXI.com> Subject: Re: Heavily loaded amd gets stuck Message-ID: <Pine.BSF.4.05.9906171124570.3882-100000@dt054n86.san.rr.com> In-Reply-To: <Pine.BSF.4.05.9906161830090.27162-100000@dt054n86.san.rr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9906171124570.3882-100000>