Subject: kern/19373:
To: None <gnats-bugs@gnats.netbsd.org>
From: None <mlh@goathill.org>
List: netbsd-bugs
Date: 12/13/2002 00:29:52
>Number:         19373
>Category:       kern
>Synopsis:       
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Dec 12 22:30:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     MLH
>Release:        NetBSD 1.6K
>Organization:
none
	
>Environment:
	
	
System: NetBSD tiamat.goathill.org 1.6K NetBSD 1.6K (TIAMAT) #0: Thu Dec 5
00:34:35 CST 2002 build@tiamat.goathill.org:/usr/syssrc/sys/arch/i386/compile/TIAMAT i386
Architecture: i386
Machine: i386
>Description:
	
The VIA VT6102 (Rhine II) 10/100 Ethernet - vr0 driver is dropping packets.

I first ran into this when trying to cvs update after new hardware
build. The update would run part way through the archivers directory
and then hang. Ktruss and tcpdump would show that it was simply
waiting for a response from the cvs server. The server would respond
with acks, but would appear to not send any more data. The client
would eventually timeout. tcpdump shwed no dropped packets though.

I connected another host to the local network and noticed that scp
and nfs transfers between the two machines using a 10/100 switch
would often result in 25% - 50% of the packets being dropped,
according to tcpdump.

vr0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        address: 00:04:61:42:93:9b
        media: Ethernet autoselect (100baseTX full-duplex)
        status: active
        inet xxx.xx.xx.xxx netmask 0xfffffff0 broadcast xxx.xx.xx.255
        inet6 fe80::204:61ff:fe42:939b%vr0 prefixlen 64 scopeid 0x2

fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        address: 00:02:b3:90:82:79
        media: Ethernet autoselect (100baseTX full-duplex)
        status: active
        inet xxx.xx.xx.xxx netmask 0xfffffff0 broadcast xxx.xx.xx.255
        inet6 fe80::202:b3ff:fe90:8279%fxp0 prefixlen 64 scopeid 0x1

>How-To-Repeat:
	

Configure to use vr0 as nic.

>Fix:
	
I fixed the situation by installing an Intel i82550 nic. Problem
completely goes away. I have no idea of how to repair the vr0
driver. Will be glad to assist testing fixes if possible.

>Release-Note:
>Audit-Trail:
>Unformatted:
 Problem with vr0 - VIA VT6102 (Rhine II) 10/100 Ethernet
         NetBSD 1.6K (TIAMAT) #0: Thu Dec  5 00:34:35 CST 2002 (via cvs)