Date: Sat, 5 Dec 2009 14:25:13 -0500 From: John Nielsen <john@jnielsen.net> To: Hiroki Sato <hrs@freebsd.org> Cc: "stable@freebsd.org" <stable@freebsd.org>, "jfvogel@gmail.com" <jfvogel@gmail.com> Subject: Re: em interface slow down on 8.0R Message-ID: <1E3C66EA-A6D3-44D7-B28E-BF068FFF16A6@jnielsen.net> In-Reply-To: <20091205.184017.30030575.hrs@allbsd.org> References: <2a41acea0912021249w1aed8e83kf89ceb1e6041edaf@mail.gmail.com> <2a41acea0912021514r2d44dd33n4c364518d7fe1703@mail.gmail.com> <20091203.182931.129751456.hrs@allbsd.org> <20091205.184017.30030575.hrs@allbsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Dec 5, 2009, at 4:40 AM, Hiroki Sato <hrs@freebsd.org> wrote: > Hiroki Sato <hrs@freebsd.org> wrote > in <20091203.182931.129751456.hrs@allbsd.org>: > > hr> And another thing, I noticed a box with 82573E and 82573L > sometimes > hr> got stuck after upgrading to 8.0-STABLE. It has moderate network > hr> load (average 5-10Mbps) on both NICs. It worked for a day or > two and > hr> then got stuck suddenly. Rebooting the box solved the > situation, but > hr> it got stuck again after a day or so. After it happens, the > hr> interface does not respond. The other functionalities of FreeBSD > hr> seemed working. Doing an up/down cycle for the NICs seemed to > send > hr> some packets, but it did not recover completely; rebooting was > needed > hr> for recovery. This box does not have the RTT problem. I am > still > hr> not sure what is the trigger, there seems something wrong. > > Things turned out for this symptom so far are: > > - This occurs around once per 1-2 days. > > - Once it occurs, all of communications including ARP and IPv4 stop. > > - "ifconfig em0 down/up" can recover the interface. However, on doing > "up" after "down" the following message was displayed: > > # ifconfig em0 up > em0: Could not setup receive structures > > After trying it several times it worked. > > Then, the interface seemed back to normal for a couple of minutes, > but it stopped again. > > I guess there is a kind of deadlock somewhere but not sure it is > really related to the em(4) driver. I will continue to investigate > anyway. I'm curious, what speed/duplex is your interface using and is it statically set or using autoselect? JN
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1E3C66EA-A6D3-44D7-B28E-BF068FFF16A6>