>Number:         26205
>Category:       kern
>Synopsis:       nfs_send: proc botch: rep 0x0 arg 0x0 curproc 0xf29bd380
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Jul 08 12:28:01 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator:     matthew green
>Release:        NetBSD 2.0G
>Organization:
people's front against (bozotic) www (softwar foundation)
>Environment:
System: NetBSD 2.0G (_evil_) #1: Wed Jul  7 01:55:10 EST 2004 mrg@littlekev.eterna.com.au:/var/obj/sparc/usr/src/sys/arch/sparc/compile/_evil_
Architecture: sparc
Machine: sparc
>Description:

	while netbooting my 3-cpu SS10 i noticed it printed the nfs
	proc botch message right after init started up:

		root on splode:/export/root/sparc
		root time: 0x40ed0ceb
		root file system type: nfs
		cpu0: booting secondary processors: cpu1 cpu2
		init: copying out flags `-s' 3
		init: copying out path `/sbin/init' 11
		nfs_send: proc botch: rep 0x0 arg 0x0 curproc 0xf29bd380
		erase ^H, werase ^W, kill ^U, intr ^C
		Terminal type? [sun] ^C
		#

	this message only occurs with DIAGNOSTIC so i assume it is an
	attempt to find places that don't pass the r_procp correctly..
	this is one of them. :-)

>How-To-Repeat:
	
	nfs boot a multi-cpu sparc with a DIAGNOSTIC enabled kernel?

>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: