From owner-freebsd-net@FreeBSD.ORG Tue Sep 25 04:41:36 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 59F90106566C for ; Tue, 25 Sep 2012 04:41:36 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-oa0-f54.google.com (mail-oa0-f54.google.com [209.85.219.54]) by mx1.freebsd.org (Postfix) with ESMTP id 1801C8FC0C for ; Tue, 25 Sep 2012 04:41:35 +0000 (UTC) Received: by oagm1 with SMTP id m1so7976593oag.13 for ; Mon, 24 Sep 2012 21:41:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=hJSvLhznB5ERZoe1gC01+F+FbjsyiN1+4I/3GMVRzaU=; b=VTae2pyaKN/7dBpj6W0XyKYYjol4+DVzWS1i8wyJ6GK+ZxlKi/ZznlTqUrcA+s//EA +r3PyPz+kkXfj2Cj441K+VBgxIClsNNFso6Bps8NE6xBybvXHiHY3js6cMbFMOED6OqI S0xX79+8vUJEwUZxRXTbfDkl5AD3gXskcf1+yutl5/ycu/+l2LMGTm/IiQH4WKbjM25k rNKP378xZgwdU9IkDiJm7XG4K6qOroljcPDzWvV6TW9HEm6YRg6ePqIGGHLeJeVdzdMn 7+44hW72jnHOTZOs1E5Rp6Mzu3Y18FP8K6vELKUWA35wtSJnniXVjoLMeArx2VeCRP1e ahVA== MIME-Version: 1.0 Received: by 10.60.170.69 with SMTP id ak5mr1946419oec.69.1348548088905; Mon, 24 Sep 2012 21:41:28 -0700 (PDT) Received: by 10.76.142.201 with HTTP; Mon, 24 Sep 2012 21:41:28 -0700 (PDT) In-Reply-To: <50611FAE.7060809@monkeybrains.net> References: <5060884C.3050709@monkeybrains.net> <50611FAE.7060809@monkeybrains.net> Date: Mon, 24 Sep 2012 21:41:28 -0700 Message-ID: From: Garrett Cooper To: "Rudy (bulk)" Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-net , Ryan Stone Subject: Re: ping: sendto: No buffer space available 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, 25 Sep 2012 04:41:36 -0000 On Mon, Sep 24, 2012 at 8:06 PM, Rudy (bulk) wrote: > On 9/24/12 5:01 PM, Ryan Stone wrote: >> >> Can you get the output of netstat -I emX -d? > > ... > >> >> I suspect that you are seeing the em TX queue fill up. If so you >> should see output drops reported by the em interface. >> > I do see 205 in the 'Drop' column. I ran the command twice two hours > apart... I am seeing Ierrsincrement in a 2 hours window... > > #date && netstat -I em1 -d > Mon Sep 24 17:47:14 PDT 2012 > Name Mtu Network Address Ipkts Ierrs Idrop Opkts > Oerrs Coll Drop > em1 1500 00:25:90:26:62:01 110170687801 4738950 0 > 85411108876 0 0 205 > em1 1500 X.X.X.X coconut.coconut-g 111858 - - 6536889 > - - - > em1 1500 fe80::225:90f fe80::225:90ff:fe 0 - - 0 - > - - > > # date && netstat -I em1 -d > Mon Sep 24 19:48:44 PDT 2012 > Name Mtu Network Address Ipkts Ierrs Idrop Opkts > Oerrs Coll Drop > em1 1500 00:25:90:26:62:01 110723416486 4768451 0 > 85861866459 0 0 205 > em1 1500 X.X.X.X coconut.coconut-g 119244 - - 6558411 - > - - > em1 1500 fe80::225:90f fe80::225:90ff:fe 0 - - 0 - > - - > > Checking all the interfaces, there are a lot more drops/Ierrs on em2... The > igb devices (PCIe card) seem a lot better than the Supermicro motherboard em > devices. Is this an on-board vs mb thing, or em vs igb thing? > > # date && netstat -id > Mon Sep 24 19:53:49 PDT 2012 > Name Mtu Network Address Ipkts Ierrs Idrop Opkts > Oerrs Coll Drop > em0 1500 00:25:90:26:62:00 6887931271 844 0 18966954063 > 0 0 0 > em0 1500 X.X.X.X coconut 1804123 - - 1962796 > - - - > em0 1500 fe80::225:90f fe80::225:90ff:fe 0 - - 1 - > - - > em1 1500 00:25:90:26:62:01 110745957108 4770615 0 > 85882005650 0 0 205 > em1 1500 X.X.X.Xcoconut.coconut-g 119573 - - 6559700 - > - - > em1 1500 fe80::225:90f fe80::225:90ff:fe 0 - - 0 - > - - > igb0 1500 00:1b:21:af:54:4e 53194278790 1169 0 > 85861440371 0 0 0 > igb0 1500 fe80::21b:21f fe80::21b:21ff:fe 0 - - 1 - > - - > igb1 1500 00:1b:21:af:54:4f 43905355772 0 0 24817874325 > 0 0 0 > igb1 1500 fe80::21b:21f fe80::21b:21ff:fe 0 - - 1 - > - - > usbus 0 0 0 0 0 0 > 0 0 > usbus 0 0 0 0 0 0 > 0 0 > usbus 0 0 0 0 0 0 > 0 0 > usbus 0 0 0 0 0 0 > 0 0 > em2 1500 00:25:90:26:62:02 2458414787 580252415422 0 > 1640052168 0 0 37284 > em2 1500 X.X.X.Xcoconut.guava-coc 93119 - - 209407 - > - - > em2 1500 fe80::225:90f fe80::225:90ff:fe 0 - - 2 - > - - > em3 1500 00:25:90:26:62:03 57160105 0 0 87941536 0 > 0 0 > em3 1500 X.X.X.XAS32329.weed-mb.c 1014267 - - 1208726 - > - - > em3 1500 fe80::225:90f fe80::225:90ff:fe 0 - - 1 - > - - I saw similar issues (although maybe not tied to e1000 directly) when messing around with IPv6 interfaces (I have em and cxgb at my immediate disposal right now). Thanks, -Garrett