From owner-freebsd-bugs  Fri Feb  9 16:50:25 2001
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP id E77C437B6AD
	for <freebsd-bugs@hub.freebsd.org>; Fri,  9 Feb 2001 16:50:02 -0800 (PST)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.11.1/8.11.1) id f1A0o2Y48537;
	Fri, 9 Feb 2001 16:50:02 -0800 (PST)
	(envelope-from gnats)
Received: from ee.elen.utah.edu (ee.elen.utah.edu [128.110.18.3])
	by hub.freebsd.org (Postfix) with ESMTP id D7DAF37B698
	for <FreeBSD-gnats-submit@freebsd.org>; Fri,  9 Feb 2001 16:46:15 -0800 (PST)
Received: by ee.elen.utah.edu (Postfix, from userid 106)
	id EE2F049; Fri,  9 Feb 2001 17:46:14 -0700 (MST)
Message-Id: <20010210004614.EE2F049@ee.elen.utah.edu>
Date: Fri,  9 Feb 2001 17:46:14 -0700 (MST)
From: howard@elen.utah.edu
Reply-To: howard@elen.utah.edu
To: FreeBSD-gnats-submit@freebsd.org
X-Send-Pr-Version: 3.2
Subject: kern/24978: Intermittent driver problem 
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         24978
>Category:       kern
>Synopsis:       "dc" network interface goes into continuous reset
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Feb 09 16:50:02 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     Walt Howard
>Release:        FreeBSD 4.1.1-RELEASE i386
>Organization:
University of Utah Electrical Engineering Dept
>Environment:

        Dual-Pentium motherboard, both (450 MHz) Pentiums installed
        PCI bus
        two installed Ethernet/Fast-Ethernet interface cards, using the
        Intel 21143 chip, and controlled by the dc driver.  I have not
        observed this problem on our smaller 1-cpu boxes that have only
        one such network interface card.

>Description:

        After some period of time (90 days in the latest case, but
        sometimes less than one day), one of the interface cards begins
        reporting "watchdog timeout" at roughly one-second intervals.
        The driver code suggests that this message is associated with
        resetting the entire interface, and it cannot be pinged from
        other computers while in this state.  The problem seemed worse
        with earlier releases of FreeBSD.  This does not panic the
        kernel or have a noticeable effect on other processes.

>How-To-Repeat:

        Boot up computer.  Watch system log.

>Fix:

        Replace network interface with a different kind that takes a
        different driver?  I like the Tulip interfaces; they and their
        driver provide more interesting information in my system logs
        when anything odd is on my network, than do other interfaces.


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


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message