Date: Mon, 21 Jan 2008 14:27:49 +0900 From: gnn@freebsd.org To: Randall Stewart <rrs@cisco.com> Cc: net@freebsd.org Subject: Re: Are there known issues with multicast on Intel Pro 1000? Message-ID: <m2zluzych6.wl%gnn@neville-neil.com> In-Reply-To: <478FB53B.60808@cisco.com> References: <7izlv4pe47.wl%gnn@neville-neil.com> <478FB53B.60808@cisco.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At Thu, 17 Jan 2008 15:06:19 -0500, randall wrote: > > gnn@freebsd.org wrote: > > Howdy, > > > > At my current gig we find that the network interface locks up if we > > subject it to a high rate of multicast traffic. Since the whole > > purpose of this box is to do multicast (it absorbs a feed of data over > > multicast manipulates and then sends it out again over multicast) it's > > a "bad thing" if this kind of thing does not work. > > > > What I currently know is not complete but I figured I could start > > here. > > > > The symptom is that all network communication stops, but the system > > itself is still responsive, so I can get to the console and get > > information. > > If you let it run long enough does it eventually lock up? > > I have seen similar behavior when a lock is not released when > I was breaking things :-) > > Everything is fine EXCEPT the interface.. for a while.. then > eventually you get a train-wreck :-) > > I would drop to ddb and do the show locks.. > > Also I believe top (or ps) will tell you what locks are being > waited on in a course way... I think the ps in DDB will do this. On closer inspection it looks like an "out of mbufs" situation and so the right answer is to "up the nmbclusters" but there seem to be other issues with this code and multicast so I'm likely to jump into DDB and look more closely at it, likely next week. Thanks, George
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m2zluzych6.wl%gnn>