Date: Wed, 17 Nov 1999 23:41:57 -0800 (PST) From: Matthew Dillon <dillon@apollo.backplane.com> To: Warner Losh <imp@village.org> Cc: "David E. Cross" <crossd@cs.rpi.edu>, freebsd-hackers@FreeBSD.ORG Subject: Re: AMD wedging Message-ID: <199911180741.XAA78627@apollo.backplane.com> References: <199911180646.BAA57262@cs.rpi.edu> <199911180651.XAA22901@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
: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
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199911180741.XAA78627>