Date: Sun, 13 Sep 2009 05:30:24 -0700 (PDT) From: Barney Cordoba <barney_cordoba@yahoo.com> To: Mike Tancsa <mike@sentex.net>, Jack Vogel <jfvogel@gmail.com> Cc: freebsd-net@freebsd.org Subject: Re: em driver input errors Message-ID: <116612.47408.qm@web63908.mail.re1.yahoo.com> In-Reply-To: <2a41acea0909110938l2348e35ah11bd1876fbe22dd3@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
=0A=0A--- On Fri, 9/11/09, Jack Vogel <jfvogel@gmail.com> wrote:=0A=0A> Fro= m: Jack Vogel <jfvogel@gmail.com>=0A> Subject: Re: em driver input errors= =0A> To: "Mike Tancsa" <mike@sentex.net>=0A> Cc: "Barney Cordoba" <barney_c= ordoba@yahoo.com>, freebsd-net@freebsd.org=0A> Date: Friday, September 11, = 2009, 12:38 PM=0A> Glad to hear this.=0A> =0A> Jack=0A> =0A> =0A> On Fri, S= ep 11, 2009 at 4:46 AM,=0A> Mike Tancsa <mike@sentex.net>=0A> wrote:=0A> = =0A> At 11:28 AM 9/9/2009, Mike Tancsa wrote:=0A> =0A> =0A> At 11:17 AM 9/9= /2009, Mike Tancsa wrote:=0A> =0A> =0A> The board is an intel=0A> =0A> =0A>= =0A> http://www.intel.com/support/motherboards/server/s3000ah/=0A>; =0A> = =0A> =0A> Not sure if its wired as PCI-X or just a 32bit bus. =A0I am=0A> j= ust popping in an em pcie nic to see if that makes a=0A> difference. =A0I h= ave an igb as well as bge I can try later.=0A> =0A> =0A> =0A> =0A> OK, now = there is=0A> =0A> =0A> =0A> em0@pci0:5:0:0: class=3D0x020000 card=3D0xa01f8= 086=0A> chip=3D0x10d38086 rev=3D0x00 hdr=3D0x00=0A> =0A> =A0 =A0vendor =A0= =A0 =3D 'Intel Corporation'=0A> =0A> =A0 =A0class =A0 =A0 =A0=3D network= =0A> =0A> =A0 =A0subclass =A0 =3D ethernet=0A> =0A> =A0 =A0cap 01[c8] =3D= powerspec 2 =A0supports D0 D3 =A0current=0A> D0=0A> =0A> =A0 =A0cap 05[d0= ] =3D MSI supports 1 message, 64 bit=0A> =0A> =A0 =A0cap 10[e0] =3D PCI-Ex= press 1 endpoint max data 128(256)=0A> link x1(x1)=0A> =0A> =A0 =A0cap 11[= a0] =3D MSI-X supports 5 messages in map 0x1c=0A> enabled=0A> =0A> =0A> =0A= > =0A> =0A> =0A> =0A> =0A> =0A> =0A> OK, much better. =A0Two nights in a ro= w without errors, and=0A> Friday AM has a lot of level0 dumps. =A0Perhaps a= s you=0A> speculated, the onboard NICs were wired to a slower bus...=0A> = =A0The pcie 1x hasnt shown any errors yet.=0A> =0A> =0A> =0A> Sep 11 00:01:= 00 backup3 kernel: em0: Excessive collisions =3D=0A> 0=0A> =0A> Sep 11 00:0= 1:00 backup3 kernel: em0: Sequence errors =3D 0=0A> =0A> Sep 11 00:01:00 ba= ckup3 kernel: em0: Defer count =3D 0=0A> =0A> Sep 11 00:01:00 backup3 kerne= l: em0: Missed Packets =3D 0=0A> =0A> Sep 11 00:01:00 backup3 kernel: em0: = Receive No Buffers =3D=0A> 0=0A> =0A> Sep 11 00:01:00 backup3 kernel: em0: = Receive Length Errors=0A> =3D 0=0A> =0A> Sep 11 00:01:00 backup3 kernel: em= 0: Receive errors =3D 0=0A> =0A> Sep 11 00:01:00 backup3 kernel: em0: Crc e= rrors =3D 0=0A> =0A> Sep 11 00:01:00 backup3 kernel: em0: Alignment errors = =3D 0=0A> =0A> Sep 11 00:01:00 backup3 kernel: em0: Collision/Carrier=0A> e= xtension errors =3D 0=0A> =0A> Sep 11 00:01:00 backup3 kernel: em0: RX over= runs =3D 0=0A> =0A> Sep 11 00:01:00 backup3 kernel: em0: watchdog timeouts = =3D 0=0A> =0A> Sep 11 00:01:00 backup3 kernel: em0: RX MSIX IRQ =3D 5000484= 6=0A> TX MSIX IRQ =3D 40678847 LINK MSIX IRQ =3D 1=0A> =0A> Sep 11 00:01:00= backup3 kernel: em0: XON Rcvd =3D 0=0A> =0A> Sep 11 00:01:00 backup3 kerne= l: em0: XON Xmtd =3D 0=0A> =0A> Sep 11 00:01:00 backup3 kernel: em0: XOFF R= cvd =3D 0=0A> =0A> Sep 11 00:01:00 backup3 kernel: em0: XOFF Xmtd =3D 0=0A>= =0A> Sep 11 00:01:00 backup3 kernel: em0: Good Packets Rcvd =3D=0A> 730648= 15=0A> =0A> Sep 11 00:01:00 backup3 kernel: em0: Good Packets Xmtd =3D=0A> = 52479296=0A> =0A> Sep 11 00:01:00 backup3 kernel: em0: TSO Contexts Xmtd = =3D 0=0A> =0A> Sep 11 00:01:00 backup3 kernel: em0: TSO Contexts Failed =3D= =0A> 0=0A> =0A> =0A> =0A> =0A> =0A> Name =A0 =A0Mtu Network =A0 =A0 =A0 Add= ress =A0 =A0 =A0 =A0 =A0 =A0=0A> =A0Ipkts Ierrs =A0 =A0Opkts Oerrs =A0Coll= =0A> =0A> em0 =A0 =A01500 <Link#1> =A0 =A0 =A000:1b:21:3f:62:72=0A> 1932699= 42 =A0 =A0 0 133269168 =A0 =A0 0 =A0 =A0 0=0A> =0A> em0 =A0 =A01500 10.45.1= 29.132 10.45.129.133 =A0 =A0 =A0 =A0 =A0=0A> =A00 =A0 =A0 - =A0 =A0 =A0 =A0= 0 =A0 =A0 - =A0 =A0 -=0A> =0A> em1 =A0 =A01500 <Link#2> =A0 =A0 =A000:15:17= :57:31:8a =A0=0A> =A0 =A0 =A00 =A0 =A0 0 =A0 =A0 =A0 =A00 =A0 =A0 0 =A0 =A0= 0=0A> =0A> em1 =A0 =A01500 10.45.129.128 10.45.129.129 =A0 =A0 =A0 =A0 =A0= =0A> =A00 =A0 =A0 - =A0 =A0 =A0 =A00 =A0 =A0 - =A0 =A0 -=0A> =0A> em2* =A0 = 1500 <Link#3> =A0 =A0 =A000:15:17:57:31:8b =A0 =A0=0A> =A0 =A00 =A0 =A0 0 = =A0 =A0 =A0 =A00 =A0 =A0 0 =A0 =A0=0A> 0=0A> =0A> =0A> =0A> =A0 =A0 =A0 = =A0---Mike=0A> =0A=0AIntel really shouldn't let MB manufacturers market dua= l gigabit =0Asystems with 32bit controllers. The NICs aren't intended to be= =0Aused that way, and it makes them look bad, when its really the fault=0Ao= f the MB manufacturer for cheaping out on the design.=0A=0ABarney=0A=0A=0A =
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?116612.47408.qm>