Date: Fri, 8 Mar 2013 21:16:50 +0100 From: mxb <mxb@alumni.chalmers.se> To: Jack Vogel <jfvogel@gmail.com> Cc: freebsd-net@freebsd.org, mxb <mxb@alumni.chalmers.se> Subject: Re: 9.1-RELEASE-p1: em0: Could not setup receive structures Message-ID: <2E6BC0C8-D435-433A-ABF7-D0E4F649F262@alumni.chalmers.se> In-Reply-To: <CAFOYbcmr8LzhUt6VndDgvX%2BW-0r17X3W0xqt7JYgFJSUVUJF-A@mail.gmail.com> References: <5587F8D1-2242-4579-B992-357C75425A37@alumni.chalmers.se> <CAFOYbcmr8LzhUt6VndDgvX%2BW-0r17X3W0xqt7JYgFJSUVUJF-A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Any sysctl I'd should look out for? //maxim On 8 mar 2013, at 21:03, Jack Vogel <jfvogel@gmail.com> 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 <mxb@alumni.chalmers.se> wrote: >=20 >>=20 >> Hello list@, >>=20 >> I'm mostly active on OpenBSD-side, however I have several machines = running >> fbsd with ZFS. >>=20 >> I'v recently upgraded(today) from 8.2-stable to 9.1-rel because of = em(4) >> with the problem <subject> 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<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 = mtu 9000 >>=20 >> = options=3D4019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLA= N_HWTSO> >> ether 00:25:90:24:70:e8 >> inet 172.16.0.243 netmask 0xfffff800 broadcast 172.16.7.255 >> nd6 options=3D1<PERFORMNUD> >> media: Ethernet autoselect >> status: active >> laggproto lacp lagghash l2,l3,l4 >> laggport: igb0 flags=3D1c<ACTIVE,COLLECTING,DISTRIBUTING> >> laggport: em0 flags=3D18<COLLECTING,DISTRIBUTING> >> lagg1: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 = mtu 9000 >>=20 >> = options=3D4019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLA= N_HWTSO> >> 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<PERFORMNUD> >> media: Ethernet autoselect >> status: active >> laggproto lacp lagghash l2,l3,l4 >> laggport: igb1 flags=3D1c<ACTIVE,COLLECTING,DISTRIBUTING> >> laggport: em1 flags=3D1c<ACTIVE,COLLECTING,DISTRIBUTING> >>=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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2E6BC0C8-D435-433A-ABF7-D0E4F649F262>