kern/144689: [re] TCP transfer corruption using if_re

[Steven Noonan]

On Wed, Sep 22, 2010 at 10:35 AM, Pyun YongHyeon <pyunyh at gmail.com> wrote:
> On Sat, Mar 20, 2010 at 02:38:55PM -0700, Steven Noonan wrote:
>> On Tue, Mar 16, 2010 at 1:46 PM, Pyun YongHyeon <pyunyh at 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 at gmail.com> wrote:
>> >
>> > [...]
>> >
>> >> > 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
>> >> ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? rgephy0 pnpinfo oui=0x732 model=0x11 rev=0x3 at phyno=1
>> >> ?? ?? ?? ?? ?? ?? ?? ?? inphy0 pnpinfo oui=0xaa00 model=0x33 rev=0x0 at phyno=1
>> >>
>> >
>> > 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?
>>
>
> How about using 8.1-RELEASE? Does it make any difference?

Don't have FreeBSD installed on that machine right now. Ended up going
back to Linux. But I'll definitely pop in another hard drive and try
it again within the next couple days.

>> - Steven
>