Date: Sun, 4 Dec 2011 18:27:30 -0800 From: YongHyeon PYUN <pyunyh@gmail.com> To: Sami Halabi <sodynet1@gmail.com> Cc: freebsd-net@freebsd.org Subject: Re: Problem on re0 Message-ID: <20111205022730.GE1729@michelle.cdnetworks.com> In-Reply-To: <CAEW%2BogauicnjsNdMCBBtoYzOLKVQoxP92Lw9Q_YgYPAe96dS5g@mail.gmail.com> References: <CAEW%2BogauicnjsNdMCBBtoYzOLKVQoxP92Lw9Q_YgYPAe96dS5g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Dec 04, 2011 at 07:33:01PM +0200, Sami Halabi wrote: > Hi, > I have a desktop on which being used as a MPD server. > the server isn't that loaded, and the cpu is highly idel 90-92% of the time. > > My problem is in the network card connected to the cables provider. > in a random manner ot stops working whith no notice, and all l2tp/pptp > users disconnect, > also the provider side stops answering my pings until i ifconfig down the > card and ifconfig up it gain. > As a work around i wrote a script that does ping every 2 minutes and if the > ping timesout it do: > ifconfig re0 down > sleep 1 > ifconfig re0 up > mail me about it > > I had FBSD-8.1-R and upgraded yesterday to FBSD-8.2-p4, and did > freebsd-update fetch/install. > but the problem persists, i got already 4 emails since the upgrade (and > didn't pass yet the 24 hours). > > here is the plot of lspci: > 01:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 > Gigabit Ethernet (rev 10) > 01:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 > Gigabit Ethernet (rev 10) > (the 2nd driver isn't used, and no cable connected). > > # ifconfig -m re0 > re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 > > options=389b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC> > > capabilities=439db<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,POLLING,VLAN_HWCSUM,TSO4,WOL_UCAST,WOL_MCAST,WOL_MAGIC,VLAN_HWTSO> > ether 00:a1:b0:69:15:5d > inet 1.2.3.5 netmask 0xfffffffc broadcast 1.2.3.7 > media: Ethernet autoselect (1000baseT <full-duplex>) > status: active > supported media: > media autoselect mediaopt flowcontrol > media autoselect > media 1000baseT mediaopt full-duplex,flowcontrol,master > media 1000baseT mediaopt full-duplex,flowcontrol > media 1000baseT mediaopt full-duplex,master > media 1000baseT mediaopt full-duplex > media 1000baseT mediaopt master > media 1000baseT > media 100baseTX mediaopt full-duplex,flowcontrol > media 100baseTX mediaopt full-duplex > media 100baseTX > media 10baseT/UTP mediaopt full-duplex,flowcontrol > media 10baseT/UTP mediaopt full-duplex > media 10baseT/UTP > media none > > # netstat -aib | grep -v ng|grep -v "all\-sys" > Name Mtu Network Address Ipkts Ierrs Idrop Ibytes > Opkts Oerrs Obytes Coll > re0 1500 <Link#1> 00:a1:b0:69:15:5d 147089824 126 0 > 46718527073 206253261 0 154140535336 0 > 01:00:5e:00:00:01 139 > 0 > re0 1500 1.2.3.3/30 1.2.3.5 435 - - 35076 206240451 > - 151252235756 - > re1* 1500 <Link#2> 00:a1:b0:69:76:28 0 0 0 0 > 0 0 0 0 > > > Please help me debug and fix this issue... > Show me dmesg output to know which controller you have(pciconf(8) output is not enough). When you notice the controller is in stuck condition, could you check which part(either TX or RX or both) of controller does not work? >From netstat(1) I can see you have 126 RX errors. Could you show me the output of "sysctl dev.re.0.stats=1"?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111205022730.GE1729>