From owner-freebsd-net@FreeBSD.ORG Fri Nov 6 05:10:04 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 190AD106568B for ; Fri, 6 Nov 2009 05:10:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E27E58FC1F for ; Fri, 6 Nov 2009 05:10:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nA65A35F023786 for ; Fri, 6 Nov 2009 05:10:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nA65A3X1023785; Fri, 6 Nov 2009 05:10:03 GMT (envelope-from gnats) Date: Fri, 6 Nov 2009 05:10:03 GMT Message-Id: <200911060510.nA65A3X1023785@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Jack Vogel Cc: Subject: Re: kern/140326: em0: watchdog timeout when communicating to windows using 9K MTU X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jack Vogel List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Nov 2009 05:10:04 -0000 The following reply was made to PR kern/140326; it has been noted by GNATS. From: Jack Vogel To: Maxim Sobolev Cc: freebsd-gnats-submit@freebsd.org Subject: Re: kern/140326: em0: watchdog timeout when communicating to windows using 9K MTU Date: Thu, 5 Nov 2009 21:05:11 -0800 --0016e6dab0fde1e7870477acc9ad Content-Type: text/plain; charset=ISO-8859-1 Good, that's a start. Now, is there a switch of some sort involved or are you going back to back? Some switches have problems with jumbo frames, there are also some vendors (including our's) interfaces that do not support jumbo frames, so you need to check on that also (I mean the RT). I will check on the Intel adapter tomorrow. Jack On Thu, Nov 5, 2009 at 6:28 PM, Maxim Sobolev wrote: > Jack Vogel wrote: > >> Can't do much unless you adequately identify hardware, on BOTH sides, >> believe >> it or not "windows" is not a sufficient description :) >> >> I need to know what the E1000 hardware is, using pciconf -l, and I also >> need to >> know what is on the Windows side before having a clue on how to repro or >> help >> you. >> > > Jack, > > Thank you for the amazingly fast reply. > > Sure, FreeBSD side is this: > > em0@pci0:0:25:0: class=0x020000 card=0x02761028 chip=0x10de8086 > rev=0x02 hdr=0x00 > vendor = 'Intel Corporation' > class = network > subclass = ethernet > > On windows side it's Realtek GiGe card. The system itself is Windows 7 > Ultimate 64-bit edition: > > PCI\VEN_10EC&DEV_8168&SUBSYS_02C01028&REV_03 > > Please let me know if any other information is necessary. > > Regards, > -- > Maksym Sobolyev > Sippy Software, Inc. > Internet Telephony (VoIP) Experts > T/F: +1-646-651-1110 > Web: http://www.sippysoft.com > MSN: sales@sippysoft.com > Skype: SippySoft > --0016e6dab0fde1e7870477acc9ad Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Good, that's a start. Now, is there a switch of some sort involved or a= re you going
back to back? Some switches have problems with jumbo frames= , there are also
some vendors (including our's) interfaces that do n= ot support jumbo frames, so
you need to check on that also (I mean the RT).

I will check on the = Intel adapter tomorrow.

Jack


O= n Thu, Nov 5, 2009 at 6:28 PM, Maxim Sobolev <sobomax@freebsd.org> wrote:
Jack Vogel wrote:
Can't do much unless you adequately identify hardware, on BOTH sides, b= elieve
it or not "windows" is not a sufficient description :)

I need to know what the E1000 hardware is, using pciconf -l, and I also nee= d to
know what is on the Windows side before having a clue on how to repro or he= lp
you.

Jack,

Thank you for the amazingly fast reply.

Sure, FreeBSD side is this:

em0@pci0:0:25:0: =A0 =A0 =A0 =A0class=3D0x020000 card=3D0x02761028 chip=3D0= x10de8086 rev=3D0x02 hdr=3D0x00
=A0 =A0vendor =A0 =A0 =3D 'Intel Corporation'
=A0 =A0class =A0 =A0 =A0=3D network
=A0 =A0subclass =A0 =3D ethernet

On windows side it's Realtek GiGe card. The system itself is Windows 7 = Ultimate 64-bit edition:

PCI\VEN_10EC&DEV_8168&SUBSYS_02C01028&REV_03

Please let me know if any other information is necessary.

Regards,
--
Maksym Sobolyev
Sippy Software, Inc.
Internet Telephony (VoIP) Experts
T/F: +1-646-651-1110
Web: http://www.sipp= ysoft.com
MSN: sales@sippyso= ft.com
Skype: SippySoft

--0016e6dab0fde1e7870477acc9ad--