>Number:         34952
>Category:       kern
>Synopsis:       re0 fails to attach some of the time
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Oct 31 02:30:00 +0000 2006
>Originator:     Perry E. Metzger
>Release:        NetBSD 4.99.3
>Organization:
	
>Environment:
	
	
System: NetBSD ein.piermont.com 4.99.3 NetBSD 4.99.3 (ZWEI) #1: Mon Oct 30 21:10:22 EST 2006 perry@ein.piermont.com:/usr/src/sys/arch/amd64/compile/ZWEI amd64
Architecture: x86_64
Machine: amd64
>Description:

Some percentage of the time, this happens to the realtek ethernet
driver (re) during boot:

re0 at pci4 dev 8 function 0: Linksys EG1032 rev. 3 Gigabit Ethernet
APC1: Picked IRQ 16 with weight 0
re0: interrupting at ioapic0 pin 16 (irq 5)
re0: Ethernet address 00:14:bf:57:21:ae
re0: using 256 tx descriptors
rgephy0 at re0 phy 7: RTL8169S/8110S 1000BASE-T media interface, rev. 0
rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
re0: diagnostic failed, failed to receive packet in loopback mode
re0: attach aborted due to hardware diag failure
rgephy0 detached

A reboot fixes the problem. The issue happens about one in every five
reboots. Naturally when the device is the only way to get to a remote
box, this can be very disturbing.

>How-To-Repeat:

I don't know if this happens on all such machines. I know that
Matt Green indicated he has had the problem on a sparc64 box with an re.

>Fix:
	

>Unformatted: