Bug 199933

Summary: re0 fails on boot, but works after manual intervention
Product: Base System Reporter: cen5848
Component: kernAssignee: freebsd-net (Nobody) <net>
Status: New ---    
Severity: Affects Some People    
Priority: ---    
Version: 10.1-RELEASE   
Hardware: amd64   
OS: Any   

Description cen5848 2015-05-04 17:16:35 UTC
Hello all,
  I have an issue with networking on a fresh vanilla install of FreeBSD 10.1 amd64. I've been trying to use the built in wired networking on a Gigabyte GA-F2A55M and when using a static IP any sort of network activity fails on boot. However, if I wait 15 seconds, and manually\script restart networking (netif and routing) everything works as expected.

The problem with this temp solution is that this breaks my jails and nfs client.

I first noticed this issue in FreeBSD 10.0 and I have not tried earlier versions, and anytime I've reinstalled this problem is consistent. This does seem similar to Bug 180852, but there has been no activity for a year on that bug. It is because of that previously filed bug that I'm using the second level severity.

If there is any additional information that I can provide to help solve this problem, please let me know. 

Thanks!

useful information:
----
uname -a:
FreeBSD freebsd.host.tld 10.1-RELEASE FreeBSD 10.1-RELEASE #0 r274401: Tue Nov 11 21:02:49 UTC 2014     root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64

sysctl -a | grep re0:
re0: <RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet> port 0xe000-0xe                                      0ff mem 0xfea00000-0xfea00fff,0xd0000000-0xd0003fff irq 16 at device 0.0 on pci1
re0: Using 1 MSI-X message
re0: Chip rev. 0x2c800000
re0: MAC rev. 0x00100000
miibus0: <MII bus> on re0
re0: Ethernet address: 74:d4:35:9b:3f:28
<118>Starting Network: lo0 re0.
<118>re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
<5>re0: link state changed to UP
<5>re0: link state changed to DOWN
<5>re0: link state changed to UP
dev.miibus.0.%parent: re0