Date: Mon, 8 Sep 2014 18:31:15 +0000 From: Steve Wills <swills@freebsd.org> To: Allan Jude <allanjude@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: network hang using intel em nic Message-ID: <20140908183114.GC18604@mouf.net> In-Reply-To: <540DE77B.2070704@freebsd.org> References: <20140908171451.GB18604@mouf.net> <540DE77B.2070704@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Sep 08, 2014 at 01:29:31PM -0400, Allan Jude wrote: > > Try periodically setting dev.em.0.debug=1 > > it will dump a bunch of stats to syslog then set it self back to -1 > > there are also a bunch of useful stats under: > dev.em.0 including things like: > dev.em.0.mbuf_alloc_fail > dev.em.0.watchdog_timeouts > dev.em.0.mac_stats.collision_count > > etc > > that might provide some insight. > > I have a box with 4x of the i210 (but that shows up as igb(4)) > > I have one of the i217LM nics in this machine, but it is used for video > production so it isn't running BSD at the moment. Thanks for the suggestions, I think I may have solved it just by ensuring my kernel modules for vbox and cuse were in sync with the kernel. Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140908183114.GC18604>