From owner-freebsd-current@FreeBSD.ORG Thu Apr 15 23:08:10 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 13D0016A4CE; Thu, 15 Apr 2004 23:08:10 -0700 (PDT) Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 912B843D54; Thu, 15 Apr 2004 23:08:09 -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 (sccrmhc11) with ESMTP id <200404160608080110099v1me>; Fri, 16 Apr 2004 06:08:08 +0000 Received: from blossom.cjclark.org (localhost. [127.0.0.1]) by blossom.cjclark.org (8.12.9p2/8.12.8) with ESMTP id i3G6860m068985; Thu, 15 Apr 2004 23:08:06 -0700 (PDT) (envelope-from cristjc@comcast.net) Received: (from cjc@localhost) by blossom.cjclark.org (8.12.9p2/8.12.9/Submit) id i3G6866q068984; Thu, 15 Apr 2004 23:08:06 -0700 (PDT) (envelope-from cristjc@comcast.net) X-Authentication-Warning: blossom.cjclark.org: cjc set sender to cristjc@comcast.net using -f Date: Thu, 15 Apr 2004 23:08:06 -0700 From: "Crist J. Clark" To: Ruslan Ermilov Message-ID: <20040416060806.GA68933@blossom.cjclark.org> References: <20040415061122.GA10883@blossom.cjclark.org> <20040415063204.GJ4415@ip.net.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040415063204.GJ4415@ip.net.ua> User-Agent: Mutt/1.4.2.1i X-URL: http://people.freebsd.org/~cjc/ X-Mailman-Approved-At: Fri, 16 Apr 2004 04:59:38 -0700 cc: current@FreeBSD.org Subject: Re: dc(4) Troubles 5.2.1 to CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: cjclark@alum.mit.edu List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Apr 2004 06:08:10 -0000 On Thu, Apr 15, 2004 at 09:32:04AM +0300, Ruslan Ermilov wrote: > On Wed, Apr 14, 2004 at 11:11:22PM -0700, Crist J. Clark wrote: > > 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 > > > My notebook doesn't assign a proper interrupt to dc(4) when I enable > ACPI. Since I don't know what your system is, assuming it's a > notebook, please try without ACPI. The system is not a notebook, and I don't think it is ACPI. ACPI has always refused to load on this system, BIOS 639kB/261120kB available memory acpi: bad RSDP checksum (155) Well, this could be a problem I suppose, but it has always been this way, and it's been running the 5.x branch fine up to 5.2.1-R. Here is the complete dmesg(8) for more info on what else the system has, Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.2-CURRENT #0: Tue Apr 13 08:13:43 PDT 2004 cjc@vegeta.cjclark.org:/var/tmp/obj/usr/src/sys/VEGETA Preloaded elf kernel "/boot/kernel/kernel" at 0xc070b000. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD-K6(tm) 3D processor (501.14-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0x80000800 real memory = 268435456 (256 MB) avail memory = 257191936 (245 MB) random: K6-family MTRR support enabled (2 registers) cpu0 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface pcibios: BIOS version 2.10 Found $PIR table, 5 entries at 0xc00f0d00 pcib0: at pcibus 0 on motherboard pci0: on pcib0 $PIR: 0:9 INTA routed to irq 9 $PIR: 0:10 INTA routed to irq 10 pcib1: at device 1.0 on pci0 pci1: on pcib1 $PIR: 0:1 INTA routed to irq 9 pcib1: slot 0 INTA is routed to irq 9 pci1: at device 0.0 (no driver attached) pci0: at device 3.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 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] pci0: at device 10.0 (no driver attached) atapci0: port 0xd400-0xd40f at device 15.0 on pci0 atapci0: Bus reserved 0x10 bytes for rid 0x20 type 4 at 0xd400 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 orm0: