From owner-freebsd-questions  Tue Sep  3 22:03:40 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id WAA22398
          for questions-outgoing; Tue, 3 Sep 1996 22:03:40 -0700 (PDT)
Received: from gdi.uoregon.edu (cisco-ts10-line5.uoregon.edu [128.223.150.103])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA22393
          for <questions@freebsd.org>; Tue, 3 Sep 1996 22:03:37 -0700 (PDT)
Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.7.5/8.6.12) with SMTP id WAA00490; Tue, 3 Sep 1996 22:03:48 -0700 (PDT)
Date: Tue, 3 Sep 1996 22:03:48 -0700 (PDT)
From: Doug White <dwhite@gdi.uoregon.edu>
Reply-To: dwhite@resnet.uoregon.edu
To: Larry Dolinar <LARRYD@bldg1.croute.com>
cc: questions@freebsd.org
Subject: Re: TCP/IP incoming falling asleep?
In-Reply-To: <CAF16D42845@bldg1.croute.com>
Message-ID: <Pine.BSI.3.94.960903220015.431I-100000@gdi.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Tue, 3 Sep 1996, Larry Dolinar wrote:

> |  I wonder if you are running low on mbufs.  You aren't getting any unusual
> |  kernel messages?  (And what happened to vty0?)  
> 
> Not that I've seen, and I'm puzzled about vty0 also.  The "after" dump 
> was done from the console, but it doesn't answer the question.
> 
> |  
> |  Send us the output of netstat -m during normal ops and when it gets stuck.
> 
> before (3 or 4 lpd's running):
> 
> 13 mbufs in use:
>     3 mbufs allocated to data
>     3 mbufs allocated to packet headers
>     5 mbufs allocated to protocol control blocks
>     2 mbufs allocated to socket names and addresses
> 3/8 mbuf clusters in use
> 17 Kbytes allocated to network (43% in use)
> 0 requests for memory denied
> 0 requests for memory delayed
> 0 calls to protocol drain routines
> 
> after (everything SSSSLLLOOOOOWWWW):
> 
> 8 mbufs in use:
>     1 mbufs allocated to packet headers
>     5 mbufs allocated to protocol control blocks
>     2 mbufs allocated to socket names and addresses
> 0/16 mbuf clusters in use
    ^^  
This is the only thing I can find that is unusual.  I don't quite know if
it's what is causing the hangups or not.

Not quite sure where to turn next... 

Doug White                              | University of Oregon  
Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite    | Computer Science Major