From owner-freebsd-net@FreeBSD.ORG Sun May 4 21:51:02 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DEC7D106564A for ; Sun, 4 May 2008 21:51:02 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.freebsd.org (Postfix) with ESMTP id A95A98FC0A for ; Sun, 4 May 2008 21:51:02 +0000 (UTC) (envelope-from mike@sentex.net) Received: from Mobile2.sentex.ca (cage.simianscience.com [64.7.134.1]) by smarthost2.sentex.ca (8.14.2/8.14.2) with SMTP id m44Lp10R089004; Sun, 4 May 2008 17:51:01 -0400 (EDT) (envelope-from mike@sentex.net) From: mike@sentex.net To: Oleksandr Samoylyk Date: Sun, 04 May 2008 17:51:22 -0400 Message-ID: References: <481C84B7.6020205@samoylyk.sumy.ua> In-Reply-To: <481C84B7.6020205@samoylyk.sumy.ua> X-Mailer: Forte Agent 4.2/32.1118 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Cc: freebsd-net@freebsd.org Subject: Re: Troubles with em on FreeBSD 7 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 May 2008 21:51:02 -0000 On Sat, 03 May 2008 18:28:55 +0300, in sentex.lists.freebsd.net you wrote: >Hi! > >I'm running a SMP FreeBSD box with mpd5 on it. > ># uname -a >FreeBSD xxx.xxxxxxxxx.xxx 7.0-STABLE FreeBSD 7.0-STABLE #0: Sat May 3=20 >12:40:02 EEST 2008 xxxxx@xxx.xxxxxxxxx.xxx:/usr/obj/usr/src/sys/XXXX= =20 > amd64 > ># mpd5 -v >Version 5.1 (root@xxx.xxxxxxxxx.xxx 09:53 1-May-2008) > >Somehow em0 begins to eat all CPU time of one core. > A new version of the em drivers went into the tree Friday. >dev.em.0.%desc: Intel(R) PRO/1000 Network Connection Version - 6.7.3 dev.em.0.%desc: Intel(R) PRO/1000 Network Connection 6.9.0 dev.em.0.%driver: em dev.em.0.%location: slot=3D0 function=3D0 dev.em.0.%pnpinfo: vendor=3D0x8086 device=3D0x108c subvendor=3D0x15d9 subdevice=3D0x108c class=3D0x020000 dev.em.0.%parent: pci13 dev.em.0.debug: -1 dev.em.0.stats: -1 dev.em.0.rx_int_delay: 0 dev.em.0.tx_int_delay: 66 dev.em.0.rx_abs_int_delay: 66 dev.em.0.tx_abs_int_delay: 66 dev.em.0.rx_processing_limit: 100 Also, post some of the stats. Do a=20 sysctl -w dev.em.1.stats=3D1 to all of your em nics em1: Excessive collisions =3D 0 em1: Sequence errors =3D 0 em1: Defer count =3D 0 em1: Missed Packets =3D 0 em1: Receive No Buffers =3D 0 em1: Receive Length Errors =3D 0 em1: Receive errors =3D 0 em1: Crc errors =3D 0 em1: Alignment errors =3D 0 em1: Collision/Carrier extension errors =3D 0 em1: RX overruns =3D 0 em1: watchdog timeouts =3D 0 em1: RX MSIX IRQ =3D 0 TX MSIX IRQ =3D 0 LINK MSIX IRQ =3D 0 em1: XON Rcvd =3D 0 em1: XON Xmtd =3D 0 em1: XOFF Rcvd =3D 0 em1: XOFF Xmtd =3D 0 em1: Good Packets Rcvd =3D 71949 em1: Good Packets Xmtd =3D 2507 em1: TSO Contexts Xmtd =3D 369 em1: TSO Contexts Failed =3D 0 And are you using gigabit or fastE. If fastE, try disabling TSO as some people have said they have problems with it at 100Mb.=20 ---Mike