From owner-freebsd-net@FreeBSD.ORG Sat Mar 20 21:38:58 2010 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 71E9E106564A; Sat, 20 Mar 2010 21:38:58 +0000 (UTC) (envelope-from steven@uplinklabs.net) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id EC8718FC13; Sat, 20 Mar 2010 21:38:57 +0000 (UTC) Received: by gwj15 with SMTP id 15so2293508gwj.13 for ; Sat, 20 Mar 2010 14:38:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.101.176.6 with SMTP id d6mr1669488anp.155.1269121135564; Sat, 20 Mar 2010 14:38:55 -0700 (PDT) In-Reply-To: <20100316204601.GJ2001@michelle.cdnetworks.com> References: <201003121754.o2CHsH7V065932@freefall.freebsd.org> <20100316182322.GF2001@michelle.cdnetworks.com> <20100316204601.GJ2001@michelle.cdnetworks.com> Date: Sat, 20 Mar 2010 14:38:55 -0700 Message-ID: From: Steven Noonan To: pyunyh@gmail.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-net@freebsd.org, bug-followup@freebsd.org, yongari@freebsd.org Subject: Re: kern/144689: [re] TCP transfer corruption using if_re 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: Sat, 20 Mar 2010 21:38:58 -0000 On Tue, Mar 16, 2010 at 1:46 PM, Pyun YongHyeon wrote: > On Tue, Mar 16, 2010 at 12:31:22PM -0700, Steven Noonan wrote: >> On Tue, Mar 16, 2010 at 11:23 AM, Pyun YongHyeon wrot= e: > > [...] > >> > The real issue looks like PHY read failure which can result in >> > unexpected behavior. I don't see rgephy(4) related message here, >> > would you show me the output of "devinfo -rv | grep phy"? >> > By chance are you using PCMCIA ethernet controller? >> >> I am. It's a Netgear GA511. I think I said in my original post that it >> was connected via cardbus. >> >> xerxes ~ # devinfo -rv | grep phy >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 rg= ephy0 pnpinfo oui=3D0x732 model=3D0x11 rev=3D0x3 at phyno=3D1 >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 inphy0 pnpinfo o= ui=3D0xaa00 model=3D0x33 rev=3D0x0 at phyno=3D1 >> > > Ok, thanks for the info. Did the controller ever work before? > Or you start seeing the issue on 8.0-RELEASE? > Uh, hm. This is weird, now I'm getting the problem not just using re(4), but also with fxp(4) (which is my on-board card). I don't think it's a driver bug here. Could this be a TCP stack bug? - Steven