Subject: kern/11065: vr0: reset never occured
To: None <gnats-bugs@gnats.netbsd.org>
From: None <pollen@astrakan.hig.se>
List: netbsd-bugs
Date: 09/21/2000 23:17:21
>Number:         11065
>Category:       kern
>Synopsis:       vr0: reset never occured
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Sep 21 23:23:00 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator:     Petter Lindquist
>Release:        NetBSD 1.5_ALPHA2
>Organization:
Pållen - http://www.astrakan.hig.se/~pollen/
>Environment:
	
System: NetBSD peli 1.5_ALPHA2 NetBSD 1.5_ALPHA2 (EBI) #2: Thu Sep 14 14:17:08 CEST 2000 peli@peli:/usr/src/sys/arch/i386/compile/EBI i386
NIC: D-link 530TX

>Description:
vr0 stops responding when not using dhclient as the very first operation
on the device. (subsequent calls brakes it)

The big problem is that I can't get the vr to respond again without
rebooting.

Sep 22 08:08:48  dhclient: Internet Software Consortium DHCP Client
V3.0b2pl0-20000719
Sep 22 08:08:48  dhclient: Copyright 1995-2000 Internet Software
Consortium.
Sep 22 08:08:48  dhclient: All rights reserved.
Sep 22 08:08:48  dhclient:  Please contribute if you find this software
useful.
Sep 22 08:08:48  dhclient: For info, please visit
http://www.isc.org/dhcp-contrib.html 
Sep 22 08:08:48  /netbsd: vr0: reset never completed!
Sep 22 08:08:48  dhclient: Listening on BPF/vr0/00:50:ba:f1:ae:47
Sep 22 08:08:48  dhclient: Sending on   BPF/vr0/00:50:ba:f1:ae:47
Sep 22 08:08:48  dhclient: Sending on   Socket/fallback
Sep 22 08:08:51  dhclient: DHCPREQUEST on vr0 to 255.255.255.255 port 67
Sep 22 08:08:48  last message repeated 2 times
Sep 22 08:08:56  /netbsd: vr0: device timeout
Sep 22 08:08:56  /netbsd: vr0: reset never completed!
Sep 22 08:09:04  /netbsd: vr0: device timeout
Sep 22 08:09:04  /netbsd: vr0: reset never completed!
Sep 22 08:08:59  dhclient: DHCPREQUEST on vr0 to 255.255.255.255 port 67

	
>How-To-Repeat:
run dhclient a couple of times. Sometimes a simple ifconfig or ping before
running dhclient is enough.

>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: