From owner-freebsd-hackers Wed Nov 17 23:42: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 3D142151C4 for ; Wed, 17 Nov 1999 23:42:04 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA78627; Wed, 17 Nov 1999 23:41:57 -0800 (PST) (envelope-from dillon) Date: Wed, 17 Nov 1999 23:41:57 -0800 (PST) From: Matthew Dillon Message-Id: <199911180741.XAA78627@apollo.backplane.com> To: Warner Losh Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG Subject: Re: AMD wedging References: <199911180646.BAA57262@cs.rpi.edu> <199911180651.XAA22901@harmony.village.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :In message <199911180646.BAA57262@cs.rpi.edu> "David E. Cross" writes: :: 30 minutes and *poof*, the problem went away. Any ideas? : :Contact Matt Dillon :-). The specific case that I hit he was able to :help me with, but it is very definitely NFS client/server on the same :machine only. : :Warner In the cases where the kernel might be at fault you will see one or more processes stuck in an NFS wait state or a VM wait state. For example, stuck nfsd's or nfsiod's. If you don't see anything like that happening, then there is a good chance that the bug is in AMD itself. I think we've fixed most of the protocol hangs... there may still be problems with 'intr' mounts -- I recommend using only hard mounts. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message