Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 14 Apr 2004 23:11:22 -0700
From:      "Crist J. Clark" <cristjc@comcast.net>
To:        current@freebsd.org
Cc:        truckman@freebsd.org
Subject:   dc(4) Troubles 5.2.1 to CURRENT
Message-ID:  <20040415061122.GA10883@blossom.cjclark.org>

next in thread | raw e-mail | index | archive | help
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: <MII bus> on dc0
  ukphy0: <Generic IEEE 802.3u media interface> 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040415061122.GA10883>