From owner-freebsd-net@FreeBSD.ORG Wed Aug 17 18:05:50 2011 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 19B36106566B for ; Wed, 17 Aug 2011 18:05:50 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1-6.sentex.ca [IPv6:2607:f3e0:0:1::12]) by mx1.freebsd.org (Postfix) with ESMTP id BE95A8FC13 for ; Wed, 17 Aug 2011 18:05:49 +0000 (UTC) Received: from [IPv6:2607:f3e0:0:4:f025:8813:7603:7e4a] (saphire3.sentex.ca [IPv6:2607:f3e0:0:4:f025:8813:7603:7e4a]) by smarthost1.sentex.ca (8.14.4/8.14.4) with ESMTP id p7HI5lHa022379; Wed, 17 Aug 2011 14:05:47 -0400 (EDT) (envelope-from mike@sentex.net) Message-ID: <4E4C0300.5010409@sentex.net> Date: Wed, 17 Aug 2011 14:05:52 -0400 From: Mike Tancsa Organization: Sentex Communications User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: Sami Halabi References: <4E4BC6CB.40305@sentex.net> <4E4BFD30.9040204@sentex.net> In-Reply-To: X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.71 on IPv6:2607:f3e0:0:1::12 Cc: freebsd-net@freebsd.org Subject: Re: strange problem FreeBSD-8.1-Release 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: Wed, 17 Aug 2011 18:05:50 -0000 On 8/17/2011 2:00 PM, Sami Halabi wrote: > > > too many missed packets? > any ideas to improve it? RELENG_8 :) Lots of bug fixes and improvements. ---Mike > > Sami > > > On Wed, Aug 17, 2011 at 8:41 PM, Mike Tancsa > wrote: > > On 8/17/2011 12:07 PM, Sami Halabi wrote: > > Hi, > > it might be a driver problem... can i update the driver only without > > updating to 8.2? if so how and from where i can get the update? > > You are better off updating the box. There are a number of bug fixes > you would benefit from. But that being said, if you really need to just > try the new driver, csup is the easiest still. > cp /usr/share/examples/cvusp/stable-supfile /tmp/ > > Edit the file, to change the prefix location so as not to override your > base src > mkdir /usr/RELENG8 > > In the sup file change the values to > > prefix=/usr/RELENG8 host=cvsup10.freebsd.org > > > csup -g -L2 /tmp/stable-supfile > > This will get the entire tree, but you can try and then compile as a > module to newer em driver in /usr/RELENG8/sys/modules/em > > > > > > > here is my sysctl: > > # sysctl -a dev.em > > On this old driver, try > > sysctl -w dev.em.2.stats=1 > > that will spit out to the console the stats for that nic. > > > > dev.em.0.%desc: Intel(R) PRO/1000 Network Connection 7.0.5 > > dev.em.0.%driver: em > > dev.em.0.%location: slot=0 function=0 > > dev.em.0.%pnpinfo: vendor=0x8086 device=0x10bc subvendor=0x8086 > > subdevice=0x11bc > > class=0x020000 > > dev.em.0.%parent: pci28 > > 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 > > dev.em.1.%desc: Intel(R) PRO/1000 Network Connection 7.0.5 > > dev.em.1.%driver: em > > dev.em.1.%location: slot=0 function=1 > > dev.em.1.%pnpinfo: vendor=0x8086 device=0x10bc subvendor=0x8086 > > subdevice=0x11bc > > class=0x020000 > > dev.em.1.%parent: pci28 > > dev.em.1.debug: -1 > > dev.em.1.stats: -1 > > dev.em.1.rx_int_delay: 0 > > dev.em.1.tx_int_delay: 66 > > dev.em.1.rx_abs_int_delay: 66 > > dev.em.1.tx_abs_int_delay: 66 > > dev.em.1.rx_processing_limit: 100 > > dev.em.2.%desc: Intel(R) PRO/1000 Network Connection 7.0.5 > > dev.em.2.%driver: em > > dev.em.2.%location: slot=0 function=0 > > dev.em.2.%pnpinfo: vendor=0x8086 device=0x10bc subvendor=0x8086 > > subdevice=0x11bc > > class=0x020000 > > dev.em.2.%parent: pci29 > > dev.em.2.debug: -1 > > dev.em.2.stats: -1 > > dev.em.2.rx_int_delay: 0 > > dev.em.2.tx_int_delay: 66 > > dev.em.2.rx_abs_int_delay: 66 > > dev.em.2.tx_abs_int_delay: 66 > > dev.em.2.rx_processing_limit: 100 > > dev.em.3.%desc: Intel(R) PRO/1000 Network Connection 7.0.5 > > dev.em.3.%driver: em > > dev.em.3.%location: slot=0 function=1 > > dev.em.3.%pnpinfo: vendor=0x8086 device=0x10bc subvendor=0x8086 > > subdevice=0x11bc > > class=0x020000 > > dev.em.3.%parent: pci29 > > dev.em.3.debug: -1 > > dev.em.3.stats: -1 > > dev.em.3.rx_int_delay: 0 > > dev.em.3.tx_int_delay: 66 > > dev.em.3.rx_abs_int_delay: 66 > > dev.em.3.tx_abs_int_delay: 66 > > dev.em.3.rx_processing_limit: 100 > > > > Sami > > > > On Wed, Aug 17, 2011 at 4:48 PM, Mike Tancsa > > >> wrote: > > > > On 8/17/2011 7:46 AM, Sami Halabi wrote: > > > Hi, > > > I have a FBSD router base on version 8.1-RELEASE-p4. > > > Today at 13:00 approx i had a sudden fall down of the traffic on > > the graphs > > > on all ports. > > > the strange thing is that no connection was lost, but the > traffic > > like went > > > down. > > > on the logs i had these lines only: > > > Aug 17 12:59:45 bgpServer kernel: em2: Watchdog timeout -- > resetting > > > Aug 17 12:59:45 bgpServer kernel: em2: link state changed to > DOWN > > > Aug 17 12:59:48 bgpServer kernel: em2: link state changed to UP > > > > > > anyone ever faced this problem? any ideas how i can track down > > what happened > > > there? > > > > Until I saw the em errors, I was thinking you are just running > into the > > 32bit counter limitations of snmp. e.g. an example graph at > > http://www.tancsa.com/overflow.png > > > > more info at > > > > > http://www.cisco.com/en/US/tech/tk648/tk362/technologies_q_and_a_item09186a00800b69ac.shtml > > > > However, the em2 suggests a possible driver error. There have > been a > > number of bug fixes to the em driver since 8.1-R. If possible, > going to > > 8.2 or even RELENG_8 might help. > > also, > > what does > > sysctl -a dev.em > > show ? > > > > > > ---Mike > > > > > > > > -- > > ------------------- > > Mike Tancsa, tel +1 519 651 3400 > > > Sentex Communications, mike@sentex.net > > > > Providing Internet services since 1994 www.sentex.net > > > > > Cambridge, Ontario Canada http://www.tancsa.com/ > > > > > > > > > > -- > > Sami Halabi > > Information Systems Engineer > > NMS Projects Expert > > > > > -- > ------------------- > Mike Tancsa, tel +1 519 651 3400 > Sentex Communications, mike@sentex.net > Providing Internet services since 1994 www.sentex.net > > Cambridge, Ontario Canada http://www.tancsa.com/ > > > > > -- > Sami Halabi > Information Systems Engineer > NMS Projects Expert > -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/