Subject: bin/6037: amd is broken
To: None <gnats-bugs@gnats.netbsd.org>
From: Lennart Augustsson <augustss@cs.chalmers.se>
List: netbsd-bugs
Date: 08/25/1998 15:18:10
>Number:         6037
>Category:       bin
>Synopsis:       amd is broken
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    bin-bug-people (Utility Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Aug 25 06:35:01 1998
>Last-Modified:
>Originator:     Lennart Augustsson
>Organization:
>Release:        NetBSD-current 980824
>Environment:
System: NetBSD dogbert.cs.chalmers.se 1.3F NetBSD 1.3F (DOGBERT) #0: Mon Jul 13 15:30:56 CEST 1998 augustss@dogbert.cs.chalmers.se:/usr/src/sys/arch/i386/compile/DOGBERT i386


>Description:
	Amd seems to be broken.  With the same configuration as before
	it now works for about 15 minutes and then you get
		nfs server XXX:/yyy: not responding 
	and it never recovers from that.  I'm using a Solaris NFS server.
	This problem occurs both on the arm32 and i386 ports and seems to
	have been introduced with the latest amd import.
>How-To-Repeat:
	Use amd to mount something.  Wait a while.  Watch it die.
>Fix:
	I have no clue.
>Audit-Trail:
>Unformatted: