----- Original Message ---- > From: Andre Keller <a...@list.ak.cx> > To: misc@openbsd.org > Cc: James Peltier <james_a_pelt...@yahoo.ca> > Sent: Mon, September 20, 2010 3:51:16 PM > Subject: Re: em(4) ierrs > > Am 20.09.2010 19:54, schrieb James Peltier: > > I see you are using LACP as your trunk protocol. You might want to check >that > > > all the LACP settings are correct or that there aren't any links being >dropped > > > for some reason that might cause the errors to occur. Additionally, have >you > > > tried with only one link in the LACP pairs being active? Does it stop then? > > > > Just tried that. There is not much I can configure for LACP. On the > switch I see no errors. > > I've now pulled one cable so that only on interface in the trunk is > active. The problem is still existing. Ierrs on the interfaces (mostly > em2) (btw. there are no ifq.drops) > It seems to me that some buffers are running full. As now when there is > low traffic there is only a small amount of errors (about 150 in 5minutes) > > Are there any other knobs I could try to tune? > > > Regards Andri
I would be tempted to say, back out all your changes and return to a stock configuration, except for the net.inet.ip.ifq.maxlen parameter. I posted in early august that I was able to push nearly full gigabit speeds with a Dell R200 w/4GB of RAM with a pretty stock configuration. Eventually I had to bump maxlen and the state table but that's about it. I don't see these problems on an mid August snapshot. I haven't had a chance to try the latest ones yet though. --- James A. Peltier james_a_pelt...@yahoo.ca
