Date: Mon, 25 Jan 2010 15:25:24 +0100 From: Lars Eggert <lars.eggert@nokia.com> To: Nick Rogers <ncrogers@gmail.com> Cc: Jason Chambers <jchambers@ucla.edu>, "stable@freebsd.org" <stable@freebsd.org>, "jfvogel@gmail.com" <jfvogel@gmail.com> Subject: Re: em interface slow down on 8.0R Message-ID: <95D3CB82-BC44-491D-86E4-5CB82F89C0FC@nokia.com> In-Reply-To: <147432021001242047k659a26d0s44b35164920aeb74@mail.gmail.com> References: <20091201.102925.218343479.hrs@allbsd.org> <2a41acea0912021249w1aed8e83kf89ceb1e6041edaf@mail.gmail.com> <2a41acea0912021514r2d44dd33n4c364518d7fe1703@mail.gmail.com> <20091203.182931.129751456.hrs@allbsd.org> <4B43F6EE.3010308@ucla.edu> <147432021001242047k659a26d0s44b35164920aeb74@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, have you tried turning off TCP Segmentation Offloading (net.inet.tcp.tso sysctl)? That fixed performance issues with some em cards for me. Lars On 2010-1-25, at 5:47, Nick Rogers wrote: > I am having similar em interface problems with some of my production > machines running older intel 2-port cards, since upgrading from 7.2-RELEASE > to 8.0-RELEASE. The problem is basically, everything works fine, but > periodically the interface "hangs" (tcpdump shows no frames). A reboot or an > ifconfig down followed by an ifconfig up fixes the problem for some time. > Traffic peaks at maybe 20mbit per day and its all 802.1Q VLAN tagged traffic > (about 10 vlan interfaces). When this happens netstat reports only errors > and no packets on the affected interface. Media is set to autoselect. This > is happening about 5-10x per day. > > Heres relevant sysctl and ifconfig info. > > dev.em.6.%desc: Intel(R) PRO/1000 Network Connection 6.9.14 > dev.em.6.%driver: em > dev.em.6.%location: slot=3 function=0 > dev.em.6.%pnpinfo: vendor=0x8086 device=0x1079 subvendor=0x8086 > subdevice=0x1179 class=0x020000 > dev.em.6.%parent: pci3 > dev.em.6.debug: -1 > dev.em.6.stats: -1 > dev.em.6.rx_int_delay: 0 > dev.em.6.tx_int_delay: 66 > dev.em.6.rx_abs_int_delay: 66 > dev.em.6.tx_abs_int_delay: 66 > dev.em.6.rx_processing_limit: 100 > > em6: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 > options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM> > ether 00:04:23:cd:47:82 > media: Ethernet autoselect (1000baseT <full-duplex>) > status: active > > On Tue, Jan 5, 2010 at 6:35 PM, Jason Chambers <jchambers@ucla.edu> wrote: > >> Hiroki Sato wrote: >>> Thank you! I have investigated some more details. First, I got >>> something wrong with the affected FreeBSD versions; one I tried was >>> 8.0-STABLE, not 8.0-RELEASE. So I started to try 8.0R. A summary of >>> chips and releases I tried so far is now the following: >>> >>> 7.2R 8.0R 8.0-STABLE >>> 82540EM (chip=0x100e8086, rev=0x02) OK OK too slow[1] >>> 82541PI (chip=0x107c8086, rev=0x05) OK ? OK >> >> >> Running 8.0R I've noticed the same problem with this card (0x107c8086). >> Duplex and speed are manually set at full/1000. >> >> >> em0@pci0:3:3:0: class=0x020000 card=0x13768086 chip=0x107c8086 rev=0x05 >> hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Gigabit Ethernet Controller (Copper) rev 5 (82541PI)' >> class = network >> subclass = ethernet >> >> >> Regards, >> >> --Jason >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?95D3CB82-BC44-491D-86E4-5CB82F89C0FC>