From owner-freebsd-questions Tue Sep 3 12:53:39 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA22009 for questions-outgoing; Tue, 3 Sep 1996 12:53:39 -0700 (PDT) Received: from croute.com (ishm2.croute.com [199.97.106.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA21999; Tue, 3 Sep 1996 12:53:34 -0700 (PDT) Received: from bldg1.croute.com by croute.com (4.1/SMI-4.1) id AA02740; Tue, 3 Sep 96 14:53:26 CDT Received: from COMPUROUTE/SpoolDir by bldg1.croute.com (Mercury 1.13); Tue, 3 Sep 96 14:53:22 +600 Received: from SpoolDir by COMPUROUTE (Mercury 1.13); Tue, 3 Sep 96 14:53:10 +600 From: "Larry Dolinar" Organization: CompuRoute, Inc. To: owner-questions@freebsd.org Date: Tue, 3 Sep 1996 14:53:09 +600 CDT Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Subject: Re: TCP/IP incoming falling asleep? Cc: questions@freebsd.org X-Confirm-Reading-To: "Larry Dolinar" X-Pmrqc: 1 Priority: normal X-Mailer: Pegasus Mail v3.22 Message-Id: Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk | From: Doug White | | Something to try after shuffling IRQs (and perhaps trying polled mode): Polled mode's been tried already (all set polled). | | 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 33 Kbytes allocated to network (3% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines after reboot: 7 mbufs in use: 5 mbufs allocated to protocol control blocks 2 mbufs allocated to socket names and addresses 0/2 mbuf clusters in use 4 Kbytes allocated to network (17% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines thanks, larry