From owner-freebsd-net@FreeBSD.ORG Fri Mar 8 20:20:09 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 52313AFC for ; Fri, 8 Mar 2013 20:20:09 +0000 (UTC) (envelope-from jeffrey.e.pieper@intel.com) Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by mx1.freebsd.org (Postfix) with ESMTP id BAD05880 for ; Fri, 8 Mar 2013 20:20:08 +0000 (UTC) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga102.fm.intel.com with ESMTP; 08 Mar 2013 12:19:56 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.84,809,1355126400"; d="scan'208";a="298045704" Received: from orsmsx105.amr.corp.intel.com ([10.22.225.132]) by fmsmga001.fm.intel.com with ESMTP; 08 Mar 2013 12:19:51 -0800 Received: from orsmsx110.amr.corp.intel.com (10.22.225.11) by ORSMSX105.amr.corp.intel.com (10.22.225.132) with Microsoft SMTP Server (TLS) id 14.1.355.2; Fri, 8 Mar 2013 12:19:50 -0800 Received: from orsmsx101.amr.corp.intel.com ([169.254.8.213]) by ORSMSX110.amr.corp.intel.com ([10.22.225.11]) with mapi id 14.01.0355.002; Fri, 8 Mar 2013 12:19:50 -0800 From: "Pieper, Jeffrey E" To: mxb , Jack Vogel Subject: RE: 9.1-RELEASE-p1: em0: Could not setup receive structures Thread-Topic: 9.1-RELEASE-p1: em0: Could not setup receive structures Thread-Index: AQHOHDnr1t1jJJcMs0m4zpHbw4SFOpicPASA Date: Fri, 8 Mar 2013 20:19:49 +0000 Message-ID: <2A35EA60C3C77D438915767F458D65687D4608A9@ORSMSX101.amr.corp.intel.com> References: <5587F8D1-2242-4579-B992-357C75425A37@alumni.chalmers.se> <2E6BC0C8-D435-433A-ABF7-D0E4F649F262@alumni.chalmers.se> In-Reply-To: <2E6BC0C8-D435-433A-ABF7-D0E4F649F262@alumni.chalmers.se> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.22.254.138] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-net@freebsd.org" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Mar 2013 20:20:09 -0000 kern.ipc.nmbclusters Jeff -----Original Message----- From: owner-freebsd-net@freebsd.org [mailto:owner-freebsd-net@freebsd.org] = On Behalf Of mxb Sent: Friday, March 08, 2013 12:17 PM To: Jack Vogel Cc: freebsd-net@freebsd.org; mxb Subject: Re: 9.1-RELEASE-p1: em0: Could not setup receive structures Any sysctl I'd should look out for? //maxim On 8 mar 2013, at 21:03, Jack Vogel wrote: > The message occurs because you don't have enough mbufs to setup the RX > ring, so you > need to look at nmbclusters. It may be that em is just the victim, since > you have igb interfaces > as well from what I see. >=20 > Jack >=20 >=20 > On Fri, Mar 8, 2013 at 11:19 AM, mxb wrote: >=20 >>=20 >> Hello list@, >>=20 >> I'm mostly active on OpenBSD-side, however I have several machines runni= ng >> fbsd with ZFS. >>=20 >> I'v recently upgraded(today) from 8.2-stable to 9.1-rel because of em(4) >> with the problem on 8.2-stable. >> However, my problem has not disappeared after mentioned upgrade. >>=20 >> I serve VMWare images from this machine. >>=20 >> Configuration: >>=20 >> lagg0: flags=3D8843 metric 0 mtu= 9000 >>=20 >> options=3D4019b >> ether 00:25:90:24:70:e8 >> inet 172.16.0.243 netmask 0xfffff800 broadcast 172.16.7.255 >> nd6 options=3D1 >> media: Ethernet autoselect >> status: active >> laggproto lacp lagghash l2,l3,l4 >> laggport: igb0 flags=3D1c >> laggport: em0 flags=3D18 >> lagg1: flags=3D8843 metric 0 mtu= 9000 >>=20 >> options=3D4019b >> ether 00:25:90:24:70:e9 >> inet 10.11.11.1 netmask 0xffffff00 broadcast 10.11.11.255 >> inet 10.11.11.11 netmask 0xffffff00 broadcast 10.11.11.255 >> inet 10.11.11.12 netmask 0xffffff00 broadcast 10.11.11.255 >> inet 10.11.11.13 netmask 0xffffff00 broadcast 10.11.11.255 >> inet 10.11.11.14 netmask 0xffffff00 broadcast 10.11.11.255 >> inet 10.11.11.15 netmask 0xffffff00 broadcast 10.11.11.255 >> inet 10.11.11.16 netmask 0xffffff00 broadcast 10.11.11.255 >> inet 10.11.11.17 netmask 0xffffff00 broadcast 10.11.11.255 >> inet 10.11.11.18 netmask 0xffffff00 broadcast 10.11.11.255 >> inet 10.11.11.19 netmask 0xffffff00 broadcast 10.11.11.255 >> inet 10.11.11.20 netmask 0xffffff00 broadcast 10.11.11.255 >> inet 10.11.11.21 netmask 0xffffff00 broadcast 10.11.11.255 >> inet 10.11.11.22 netmask 0xffffff00 broadcast 10.11.11.255 >> inet 10.11.11.23 netmask 0xffffff00 broadcast 10.11.11.255 >> inet 10.11.11.24 netmask 0xffffff00 broadcast 10.11.11.255 >> inet 10.11.11.25 netmask 0xffffff00 broadcast 10.11.11.255 >> inet 10.11.11.26 netmask 0xffffff00 broadcast 10.11.11.255 >> inet 10.11.11.27 netmask 0xffffff00 broadcast 10.11.11.255 >> inet 10.11.11.28 netmask 0xffffff00 broadcast 10.11.11.255 >> nd6 options=3D1 >> media: Ethernet autoselect >> status: active >> laggproto lacp lagghash l2,l3,l4 >> laggport: igb1 flags=3D1c >> laggport: em1 flags=3D1c >>=20 >> current sysctl.conf (not fixed after upgrade): >> # Every socket is a file, so increase them >> kern.maxfiles=3D204800 >> kern.maxfilesperproc=3D200000 >> kern.ipc.maxsockets=3D204800 >>=20 >> # Increase max command-line length showed in `ps` (e.g for Tomcat/Java) >> # Default is PAGE_SIZE / 16 or 256 on x86 >> # For more info see: http://www.freebsd.org/cgi/query-pr.cgi?pr=3D120749 >> kern.ps_arg_cache_limit=3D4096 >>=20 >> # Security >> #net.inet.udp.blackhole=3D1 >> #net.inet.tcp.blackhole=3D2 >>=20 >> kern.ipc.maxsockbuf=3D16777216 >> kern.ipc.nmbclusters=3D65535 >> kern.ipc.somaxconn=3D32768 >> #kern.maxfiles=3D65535 >> kern.maxvnodes=3D800000 >>=20 >> vfs.zfs.l2arc_noprefetch=3D0 >> vfs.zfs.l2arc_write_max=3D16777216 >> vfs.zfs.l2arc_write_boost=3D16777216 >>=20 >> net.inet.tcp.sendspace=3D65535 >> net.inet.tcp.recvspace=3D131072 >> net.inet.tcp.mssdflt=3D1452 >> net.inet.tcp.sendbuf_max=3D16777216 >> net.inet.tcp.sendbuf_inc=3D524288 >> net.inet.tcp.recvbuf_max=3D16777216 >> net.inet.tcp.recvbuf_inc=3D524288 >> net.inet.udp.recvspace=3D65535 >> net.inet.udp.maxdgram=3D65535 >> net.local.stream.recvspace=3D65535 >> net.local.stream.sendspace=3D65535 >> net.inet.tcp.delayed_ack=3D0 >>=20 >>=20 >> Any clues? >>=20 >> Please mail directly to me or cc to sysop@prisjakt.nu >>=20 >> Regards >> Maxim >>=20 >>=20 >> _______________________________________________ >> freebsd-net@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-net >> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >>=20 > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"