From owner-freebsd-bugs Sat Apr 8 23: 0: 7 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 08C6E37B5C9 for ; Sat, 8 Apr 2000 23:00:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id XAA22689; Sat, 8 Apr 2000 23:00:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id C12B337B551 for ; Sat, 8 Apr 2000 22:53:33 -0700 (PDT) (envelope-from nobody@FreeBSD.org) Received: (from nobody@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id WAA22169; Sat, 8 Apr 2000 22:53:32 -0700 (PDT) (envelope-from nobody@FreeBSD.org) Message-Id: <200004090553.WAA22169@freefall.freebsd.org> Date: Sat, 8 Apr 2000 22:53:32 -0700 (PDT) From: locke@mcs.net To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: kern/17874: Watchdog Timeout in vr device Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 17874 >Category: kern >Synopsis: Watchdog Timeout in vr device >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Apr 8 23:00:01 PDT 2000 >Closed-Date: >Last-Modified: >Originator: Peter Johnson >Release: 4.0-STABLE >Organization: >Environment: FreeBSD matrix.bilogic.org 4.0-STABLE FreeBSD 4.0-STABLE #13: Fri Mar 31 02:48:21 CST 2000 >Description: After upgrading to 4.0 from 3.4, I periodically see my network connectivity completely die for about 30 seconds or so (can't ping anything on the network, nothing can ping the machine), and I get a "vr0: watchdog timeout" message in my system log. Several times the disconnection has been quite lengthy (30 secs to 2 minutes) and I get multiple (5-20) watchdog timeout messages in my system log. The connection seems to restore itself after a certain time. My network card is a D-Link 530TX. I never had this problem under 3.4, so I'm assuming something with the new miibus-based drivers is causing this problem. The problem is very intermittant; I first noticed it when trying to transfer large amounts of data over the link, but now it seems to occur even when moderate amounts of data are being transferred. Other (possibly) relevant info: the card is connected to a 10/100 switch; the link light does not go off on the switch when the problem occurs. The IP is configured via DHCP. The traffic over the link is almost exclusively ftp and Samba traffic; the problem has occurred with each one seperately. Although I have not tried to switch cards, the problem first started occurring after I upgraded to 4.0. >How-To-Repeat: Moderate to heavy traffic load on a card using a vr network driver. Hard to repeat because of its unpredictability. >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message