>Number:         4115
>Category:       kern
>Synopsis:       Panic from nfs code at reboot
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    kern-bug-people (Kernel Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Sep 16 07:35:02 1997
>Last-Modified:
>Originator:     Manuel Bouyer
>Organization:
Ecole Nationale Superieure de Techniques Avancees, Paris
>Release:        NetBSD-current as of 97/08/31.
>Environment:

System: NetBSD chassiron.ensta.fr 1.2G NetBSD 1.2G (CHASSIRON) #0: Wed Jul 23 09:38:48 MEST 1997 bouyer@chassiron.ensta.fr:/usr/src/sources/src_current/sys/arch/i386/compile/CHASSIRON i386


>Description:
	Today, my NFS server (ss20 running solaris, network is ATM/LAN emulation)
	did go down for unknow reason (I'm not the admin of this one). When it came
	back up (ping ok, shoumount ok) NetBSD could't still see it (server not
	responding). It is mounted via amd. So I decided to reboot the netbsd box.
	Reboot take a long time, and ends with the following panic:
	Panic: nfs_rcvunlock
	Here is the stack trace:
		nfs_rcvunlock +0x19
		nfs_reply +ox45
		nfs_request +0x3e1
		nfs_fsinfo +0x246
		nfs_statfs +0x83
		sys_mount +0x521
		syscall (#21)
	It is possible that the server was in a state where it was not handling
	NFS request correctly. It is also possible that the server did go down
	again between the 'reboot' command and the panic (when my box rebooted,
	it was down). In any case I think the server was not in a clean state.

>How-To-Repeat:
	Don't know with precision. 
>Fix:
	unknown.
>Audit-Trail:
>Unformatted: