From owner-freebsd-current@FreeBSD.ORG Wed Apr 14 23:11:29 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F27B616A4CE; Wed, 14 Apr 2004 23:11:28 -0700 (PDT) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CF0443D1D; Wed, 14 Apr 2004 23:11:28 -0700 (PDT) (envelope-from cristjc@comcast.net) Received: from blossom.cjclark.org (c-24-6-187-112.client.comcast.net[24.6.187.112]) by comcast.net (rwcrmhc13) with ESMTP id <2004041506112701500rcoq4e>; Thu, 15 Apr 2004 06:11:28 +0000 Received: from blossom.cjclark.org (localhost. [127.0.0.1]) by blossom.cjclark.org (8.12.9p2/8.12.8) with ESMTP id i3F6BN0m010954; Wed, 14 Apr 2004 23:11:27 -0700 (PDT) (envelope-from cristjc@comcast.net) Received: (from cjc@localhost) by blossom.cjclark.org (8.12.9p2/8.12.9/Submit) id i3F6BMTa010953; Wed, 14 Apr 2004 23:11:22 -0700 (PDT) (envelope-from cristjc@comcast.net) X-Authentication-Warning: blossom.cjclark.org: cjc set sender to cristjc@comcast.net using -f Date: Wed, 14 Apr 2004 23:11:22 -0700 From: "Crist J. Clark" To: current@freebsd.org Message-ID: <20040415061122.GA10883@blossom.cjclark.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-URL: http://people.freebsd.org/~cjc/ cc: truckman@freebsd.org Subject: dc(4) Troubles 5.2.1 to CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: cjc@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Apr 2004 06:11:29 -0000 Ah, dc(4), everyone's favorite buggy NIC. I've got a system with a dc(4) that I am trying to move to 5-CURRENT from 5.2.1-R. Here's the info on the NIC, dc0@pci0:9:0: class=0x020000 card=0xf0022646 chip=0x000211ad rev=0x20 hdr=0x00 vendor = 'Lite-On Communications Inc' device = 'NGMC169B 10/100 Ethernet (NetGear FA310TX)' class = network subclass = ethernet It has been working alright in 5.2.1-R, but with CURRENT, I end up with, dc0: failed to force tx and rx to idle state dc0: failed to force tx and rx to idle state dc0: watchdog timeout dc0: failed to force tx and rx to idle state dc0: watchdog timeout dc0: failed to force tx and rx to idle state dc0: watchdog timeout The 'failed to force tx and rx to idle state' are not new. I would get those at boot time with 5.2.1-R, but the 'watchdog timeout' is new. The NIC is no longer working at all. No traffic going in or out. I noticed that the src/sys/pci/if_dc* files had had some changes since 5.2.1-R and tried regressing just those, but it had no effect. Bummer, since it looked like 1.138 of if_dc.c was a good candidate for causing the trouble. Anyone else have this card and see this? Ideas about what may have changed? Some dmesg(8) output, dc0: <82c169 PNIC 10/100BaseTX> port 0xd800-0xd8ff mem 0xde000000-0xde0000ff irq 9 at device 9.0 on pci0 dc0: Bus reserved 0x100 bytes for rid 0x10 type 4 at 0xd800 dc0: Ethernet address: 00:c0:f0:5a:6c:0a miibus0: on dc0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc0: Ethernet address: 00:c0:f0:5a:6c:0a dc0: [GIANT-LOCKED] dc0: failed to force tx and rx to idle state dc0: failed to force tx and rx to idle state dc0: watchdog timeout dc0: failed to force tx and rx to idle state dc0: watchdog timeout dc0: failed to force tx and rx to idle state dc0: watchdog timeout -- Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@freebsd.org