FreeBSD 7.1 Breaks re and rl Network Interface Drivers

[Dimitry Andric]

On 2009-01-13 06:02, Pyun YongHyeon wrote:
>  > I'm also having problems with re's, in my case the interfaces take about
>  > 10 seconds to come up, if they come up at all.  After the interfaces are
>  > up, half the time no packets go out at all.  Usually it helps to bring
>  > them down via the console, wait about 10 seconds, and then bring them up
>  > again...
> It looks like that RTL8169SC users see regression and I vaguely
> remember a couple of issues on RTL8169SC. As Jung-uk said in other
> post, would yoy try reverting r180519?

Reverting r180519 seems to solve the problem of not being able to send
any packets.  It does not solve the other problem, which is that the
interfaces can take a very long time to come up at boot time, e.g:

  Setting hostuuid: 3ee65237-8025-11dc-9ab5-003018a6f1a8.
  Setting hostid: 0xaaedab9a.
  Mounting local file systems:.
  Setting hostname: tensor.andric.com.
[... pauses for 10 seconds here ...]
  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 0x4
	  inet 127.0.0.1 netmask 0xff000000
  re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
	  options=389b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,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=389b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,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
[...]

(note also the "no carrier" just after upping those interfaces)


> If that have no effect would
> you try attached patch?

Apply this patch sometimes speeds up the interfaces going up at boot
time, sometimes it doesn't, I'd say about 50/50.  It doesn't solve the
problem of not being able to send any packets.


>  > And just FYI, r187080-r187083 that you recently committed (MFCs of
>  > r184240-184243, r184245, 185575 and r186390), don't seem to change
>  > anything for this situation. :(
> Those MFC are for rl(4), not re(4) so you should see no behavioural
> changes in re(4).

Sorry about that, I always keep mixing up re(4) and rl(4)...