Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 10 Jul 2013 16:04:31 +0900
From:      Yonghyeon PYUN <pyunyh@gmail.com>
To:        Guido Falsi <mad@madpilot.net>
Cc:        freebsd-net@freebsd.org
Subject:   Re: re0 not working at boot on -CURRENT
Message-ID:  <20130710070431.GE2753@michelle.cdnetworks.com>
In-Reply-To: <51DC726D.6040601@madpilot.net>
References:  <51DC726D.6040601@madpilot.net>

index | next in thread | previous in thread | raw e-mail

On Tue, Jul 09, 2013 at 10:28:29PM +0200, Guido Falsi wrote:
> Hi,
> 
> I have a PC with an integrate re ethernet interface, pciconf identifies 
> it like this:
> 
> re0@pci0:3:0:0: class=0x020000 card=0x11c01734 chip=0x816810ec rev=0x07 
> hdr=0x00
> 
> I'm running FreeBSD current r252261.
> 
> As stated in the subject after boot the interface does not work correctly.
> 
> Using tcpdump on another host I noticed that packets (ICMP echo requests 
> for example) do get sent, and replies generated by the other host, but 
> the kernel does not seem to see them. Except that every now and then 
> some packet does get to the system.
> 
> I'm seeing packet 7, 27, 47, 66, 86, 106, 125, 144, 164, 183 and so on 
> from a ping which has been running for some time. Just about one every 
> twenty. Some pattern is showing up.
> 
> this is the output of ifconfig re0 after boot:
> 
> re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
> 
> options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
>         ether 00:19:99:f8:d3:0b
>         inet 172.24.42.13 netmask 0xffffff00 broadcast 172.24.42.255
>         inet6 fe80::219:99ff:fef8:d30b%re0 prefixlen 64 scopeid 0x2
>         nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
>         media: Ethernet autoselect (100baseTX <full-duplex>)
>         status: active
> 
> If I just touch any interface flag with ifconfig, anyone, tso, -txcsum 
> -rxcsum, it starts working flawlessly. It keeps working also if I 
> perform the opposite operation with ifconfig afterwards, so it is not 
> the flag itself fixing it.
> 
> This is an ifconfig after performing this exercise(it's the same, since 
> I disabled txcsum and reactivated it in this instance):
> 
> re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
> 
> options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
>         ether 00:19:99:f8:d3:0b
>         inet 172.24.42.13 netmask 0xffffff00 broadcast 172.24.42.255
>         inet6 fe80::219:99ff:fef8:d30b%re0 prefixlen 64 scopeid 0x2
>         nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
>         media: Ethernet autoselect (100baseTX <full-duplex>)
>         status: active
> 
> I don't know much about FreeBSD network drivers so i can't make theories 
> about this. I hope someone has an idea what the problem could be.
> 
> I'm available for any further information needed, test, experiment and 
> so on.

Could you show me dmesg output(re(4) and rgephy(4) only)?
Did it ever work or you see the issue only on CURRENT?


help

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