>Number:         28664
>Category:       kern
>Synopsis:       vr(4) driver timeouts
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Dec 15 04:20:00 +0000 2004
>Originator:     Juan RP
>Release:        NetBSD 2.99.11 i386
>Organization:
>Environment:


System: NetBSD 2.99.11 (Nocturno) #153: Wed Dec 15 04:52:25 CET 2004
	juan@Nocturno:/home/juan/build/obj/sys/arch/i386/compile/Nocturno



>Description:


I was playing with the QEMU emulator, when I noticed a weird thing,
My configuration looks like:

	vr0: flags=8b43<UP,BROADCAST,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICAST> mtu 1500
        address: 00:11:2f:3c:66:b5
        media: Ethernet autoselect (100baseTX full-duplex)
        status: active
        inet 192.168.1.7 netmask 0xffffff00 broadcast 192.168.1.255
        inet6 fe80::211:2fff:fe3c:66b5%vr0 prefixlen 64 scopeid 0x1

ethfoo0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
        address: f0:0b:a4:c3:29:bb
        media: Ethernet autoselect
        inet 192.168.1.5 netmask 0xffffff00 broadcast 192.168.1.255
        inet6 fe80::f20b:a4ff:fec3:29bb%ethfoo0 prefixlen 64 scopeid 0x3
bridge0: flags=41<UP,RUNNING> mtu 1500

When I boot an OS inside QEMU, it gets assigned an IP via dhcp correctly
and you can interact correctly, but when trying to install a package from
pkgsrc (NFS mount), my vr(4) was totally stopped without receiving/sending
packets, I saw "vr0: device timeout".

I have no problems when using it without the bridge0.


>How-To-Repeat:


See above.


>Fix:


I wish!