>Number:         37484
>Category:       kern
>Synopsis:       vr(4) does not deal well with link disappearing and reappearing
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Dec 05 20:50:00 +0000 2007
>Originator:     Jared D. McNeill
>Release:        NetBSD 4.99.22
>Organization:
	
>Environment:
	
	
System: NetBSD endeavour.invisible.ca 4.99.22 NetBSD 4.99.22 (GENERIC) #6: Sun Jul 8 14:13:58 EDT 2007 jmcneill@silver.invisible.ca:/nbbuild/jmcneill-bootprops/sys/arch/i386/compile/GENERIC i386
Architecture: i386
Machine: i386
>Description:
	The vr(4) driver will usually stall and require an ifconfig down/up
	cycle to recover if the network link drops and reappears.

	Hardware is as follows:

vr0 at pci0 dev 6 function 0: VIA VT6105M (Rhine III) 10/100 Ethernet
vr0: interrupting at irq 11
vr0: Ethernet address: 00:00:24:xx:xx:xx
ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface
ukphy0: OUI 0x0002c6, model 0x0034, rev. 3
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

>How-To-Repeat:
	While running:
		$ /sbin/ping somehost
	Unplug and re-plug the network cable. Usually between one and a few
	times is all it takes for the network connection to fail. An
	ifconfig down ; ifconfig up is required to recover.
>Fix:
	Unknown.

>Unformatted: