From owner-freebsd-hackers  Mon Apr 14 14:22:16 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA15101
          for hackers-outgoing; Mon, 14 Apr 1997 14:22:16 -0700 (PDT)
Received: from who.cdrom.com (who.cdrom.com [204.216.27.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA15094
          for <freebsd-hackers@freefall.FreeBSD.org>; Mon, 14 Apr 1997 14:22:10 -0700 (PDT)
Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2])
          by who.cdrom.com (8.8.5/8.6.11) with SMTP id OAA00881
          for <freebsd-hackers@freefall.FreeBSD.org>; Mon, 14 Apr 1997 14:20:39 -0700 (PDT)
Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02)
	id AA16153; Mon, 14 Apr 1997 17:20:02 -0400
Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Mon, 14 Apr 1997 17:20 EDT
Received: (from rivers@localhost) by ponds.water.net (8.8.3/8.7.3) id RAA23661 for freebsd-hackers@freefall.cdrom.com; Mon, 14 Apr 1997 17:12:23 -0400 (EDT)
Date: Mon, 14 Apr 1997 17:12:23 -0400 (EDT)
From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com>
Message-Id: <199704142112.RAA23661@ponds.water.net>
To: ponds!freefall.cdrom.com!freebsd-hackers@ucbvax.Berkeley.EDU
Subject: NFS hangups in 2.2.1 - problem in calling sowakeup()???
Content-Type: text
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


Ok - 

 (Again, this is the readdir hangs in NFS with 2.2.1).

 I've determined that soreceive() calls sbwait() - which dutifully
waits on &sb->sb_cc.

 I've also determined that sowakeup() *never* does a wakeup()
on that address.

 So, the problem; as it appears to me, has to be that sowakeup()
is never called with the socket buffer associated with the socket
from the original readdir(); and so, the "ls -l" is hung forever
in sbwait().

 It's not at all obvious to me how sowakeup() is supposed to be
called, (I imagine from some interrupt routine, somewhere...) and 
from where it gets it's second parm (the socket buffer in question) - 
but I'd bet that's where the problem lies...  Can someone "in the know" 
investigate, or point me to where this might be...  Since I have
a reliable reproduction of the problem; I'm likely the only "tester"
around...

	- Dave Rivers -