Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 20 Mar 2010 14:38:55 -0700
From:      Steven Noonan <steven@uplinklabs.net>
To:        pyunyh@gmail.com
Cc:        freebsd-net@freebsd.org, bug-followup@freebsd.org, yongari@freebsd.org
Subject:   Re: kern/144689: [re] TCP transfer corruption using if_re
Message-ID:  <f488382f1003201438w549ba53ar3b02e524a9fc72ee@mail.gmail.com>
In-Reply-To: <20100316204601.GJ2001@michelle.cdnetworks.com>
References:  <201003121754.o2CHsH7V065932@freefall.freebsd.org> <f488382f1003121619y17780ed9x52765b9a9133fb2@mail.gmail.com> <f488382f1003121624j34a8aee8kc127e82c08c3fe37@mail.gmail.com> <f488382f1003122157i12968043h31c8020007f7e8a1@mail.gmail.com> <f488382f1003130418s116e9c1frfd210db4127b4a9@mail.gmail.com> <20100316182322.GF2001@michelle.cdnetworks.com> <f488382f1003161231s2fbd7d39yf615941d028c18e8@mail.gmail.com> <20100316204601.GJ2001@michelle.cdnetworks.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 16, 2010 at 1:46 PM, Pyun YongHyeon <pyunyh@gmail.com> 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 <pyunyh@gmail.com> 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f488382f1003201438w549ba53ar3b02e524a9fc72ee>