From owner-freebsd-net@FreeBSD.ORG Tue May 16 17:58:32 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0046916AECD; Tue, 16 May 2006 17:58:31 +0000 (UTC) (envelope-from rsf@ns.live555.com) Received: from ns.live555.com (ns.live555.com [66.80.62.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F93243D6A; Tue, 16 May 2006 17:58:31 +0000 (GMT) (envelope-from rsf@ns.live555.com) Received: from ns.live555.com (localhost.live555.com [127.0.0.1]) by ns.live555.com (8.13.4/8.13.4) with ESMTP id k4GHwVvA020086; Tue, 16 May 2006 10:58:31 -0700 (PDT) (envelope-from rsf@ns.live555.com) Received: (from rsf@localhost) by ns.live555.com (8.13.4/8.13.4/Submit) id k4GHwVA3020081; Tue, 16 May 2006 10:58:31 -0700 (PDT) (envelope-from rsf) Message-Id: <7.0.1.0.1.20060516105535.01dafe98@live555.com> Message-Id: <7.0.1.0.1.20060515163433.01dc8008@live555.com> X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0 Date: Tue, 16 May 2006 10:58:25 -0700 To: freebsd-mobile@freebsd.org, freebsd-net@freebsd.org From: Ross Finlayson Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: Subject: Apparent 'resource' problems with "ath0" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 May 2006 17:58:33 -0000 %cat /etc/motd FreeBSD 6.1-STABLE (GENERIC) #3: Tue May 9 19:36:33 PDT 2006 Problem #1 (yesterday): May 15 16:05:30 ns named[398]: client 66.80.0.9#1075: error sending response: not enough free resources May 15 16:05:38 ns last message repeated 2 times May 15 16:05:39 ns named[398]: client 66.80.0.9#1096: error sending response: not enough free resources May 15 16:05:47 ns last message repeated 2 times May 15 16:05:56 ns named[398]: client 66.80.0.9#1075: error sending response: not enough free resources May 15 16:05:58 ns named[398]: client 66.80.0.9#1075: error sending response: not enough free resources May 15 16:05:58 ns named[398]: client 66.80.0.9#1096: error sending response: not enough free resources %netstat -m 231/294/525 mbufs in use (current/cache/total) 106/156/262/8896 mbuf clusters in use (current/cache/total/max) 106/150 mbuf+clusters out of packet secondary zone in use (current/cache) 0/0/0/0 4k (page size) jumbo clusters in use (current/cache/total/max) 0/0/0/0 9k jumbo clusters in use (current/cache/total/max) 0/0/0/0 16k jumbo clusters in use (current/cache/total/max) 269K/385K/655K bytes allocated to network (current/cache/total) 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) 0/0/0 requests for jumbo clusters denied (4k/9k/16k) 0/4/2480 sfbufs in use (current/peak/max) 0 requests for sfbufs denied 0 requests for sfbufs delayed 0 requests for I/O initiated by sendfile 0 calls to protocol drain routines Problem #2 (today): May 16 10:53:00 ns dhcpd: send_packet: No buffer space available May 16 10:53:09 ns dhcpd: send_packet: No buffer space available May 16 10:53:29 ns named[398]: client 66.80.0.9#1290: error sending response: not enough free resources May 16 10:53:37 ns last message repeated 2 times May 16 10:53:55 ns dhcpd: send_packet: No buffer space available %netstat -m 364/161/525 mbufs in use (current/cache/total) 207/55/262/8896 mbuf clusters in use (current/cache/total/max) 207/49 mbuf+clusters out of packet secondary zone in use (current/cache) 0/0/0/0 4k (page size) jumbo clusters in use (current/cache/total/max) 0/0/0/0 9k jumbo clusters in use (current/cache/total/max) 0/0/0/0 16k jumbo clusters in use (current/cache/total/max) 505K/150K/655K bytes allocated to network (current/cache/total) 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) 0/0/0 requests for jumbo clusters denied (4k/9k/16k) 0/11/2480 sfbufs in use (current/peak/max) 0 requests for sfbufs denied 0 requests for sfbufs delayed 6 requests for I/O initiated by sendfile 483 calls to protocol drain routines Any ideas? (Is this a known issue that has been fixed since May 9th?) In each case, the client to named and/or dhcpd was using the "ath0" interface. Ross.