Re: Call for testers: re(4) and RTL8168C/RTL8168CP/RTL8111C/RTL8111CP

On Sat, Jun 28, 2008 at 6:54 PM, Dimitry Andric <dimitry_at_andric.com> wrote:
> On 2008-06-11 02:58, Pyun YongHyeon wrote:
>>  > This seems to work better, although it still takes quite some time
>>  > (~10s) for the interfaces to go up at boot time.  I haven't yet been
>>  > able to get them "stuck", however, so that's good. :)
>> Hmm, that's interesting. Can you spot where re(4) spends its time?
>> Did RELENG_7 also have this issue?
>
> Apparently it's experiencing timeouts, I usually get these:
>
> re0: link state changed to DOWN
> re0: watchdog timeout
> re0: 3 link states coalesced
> re0: link state changed to UP
> re1: link state changed to DOWN
>
> I've been running all tests under RELENG_7, btw.  Note also, these
> delays don't always happen, in some cases the interfaces react very
> quickly.  In rare cases, they don't work at all, until you manually
> ifconfig down and up them a few times.
>
> What's funny though, is that the interfaces seem to start in DOWN mode:
>
> [...booting...]
> Mounting local file systems:.
> Setting hostname: tensor.andric.com.
> re0: link state changed to DOWN
> re1: link state changed to DOWN
> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
>        inet6 ::1 prefixlen 128
>        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
>        inet 127.0.0.1 netmask 0xff000000
> re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
>        options=399b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_UCAST,WOL_MCAST,WOL_MAGIC>
>        ether 00:30:18:a6:f1:a8
>        inet6 fe80::230:18ff:fea6:f1a8%re0 prefixlen 64 tentative scopeid 0x1
>        inet 87.251.56.140 netmask 0xffffffc0 broadcast 87.251.56.191
>        media: Ethernet autoselect (none)
>        status: no carrier
> re1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
>        options=399b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_UCAST,WOL_MCAST,WOL_MAGIC>
>        ether 00:30:18:a6:f1:a9
>        inet6 fe80::230:18ff:fea6:f1a9%re1 prefixlen 64 tentative scopeid 0x2
>        inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255
>        media: Ethernet autoselect (none)
>        status: no carrier
> [...more initialization...]
> net.inet6.ip6.forwarding: 0 -> 1
> net.inet6.ip6.accept_rtadv: 0 -> 0
> re0: link state changed to UP
> re1: link state changed to UP
>
> and only then do they "really" go up... :)
>
> Do you have any good suggestions on where I could put some debug
> printfs in re to find out what it's timing out on?
>
>
>> Plugging/unplugging UTP cable to ethernet controller during boot
>> change the long delay? How about disabling WOL before system
>> shutdown?(e.g. ifconfig re0 -wol)
>
> Plugging/unplugging the cable doesn't seem to make much difference, and
> neither does disabling WOL before shutdown (or altogether)...
>
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
>

Hi Dimitry,

what happens if you load the if_re module after you logged in instead
of loading it while boot time?
I get a watchdog every time with a boot time loaded if_re, so maybe
this is not affecting you too.

Regards,

vb