-CURRENT, D-Link DFE-670TXD gets "device_probe_and_attach: ed1 attach returned 6"

[David Wolfskill]

This has actually been a fairly long-standing issue on my laptop, but my
laptop was having problems, then I had problems with -CURRENT ....
anyway, I'm back to tracking -STABLE and -CURRENT daily, and this
appears to be quite reproduceable.

Fortunately, other NICs (such as my Cisco/Aironet 340) still work:


Nov 23 15:20:28 localhost kernel: pccard1: CIS version PCCARD 2.0 or 2.1
Nov 23 15:20:28 localhost kernel: pccard1: CIS info: Cisco Systems, 340 Series Wireless LAN Adapter
Nov 23 15:20:28 localhost kernel: pccard1: Manufacturer code 0x15f, product 0x7
Nov 23 15:20:28 localhost kernel: pccard1: function 0: network adapter, ccr addr 3e0 mask 7
Nov 23 15:20:28 localhost kernel: pccard1: function 0, config table entry 5: I/O card; irq mask ffff; iomask 6, iospace 0-3f; io16 irqlevel
Nov 23 15:20:28 localhost kernel: an0: <Cisco Systems 340 Series Wireless LAN Adapter> at port 0x100-0x13f irq 11 function 0 config 5 on pccard1
Nov 23 15:20:28 localhost kernel: an0: got RSSI <-> dBM map
Nov 23 15:20:28 localhost kernel: an0: Ethernet address: 00:40:96:32:19:a9
Nov 23 15:20:28 localhost kernel: an0: supported rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
Nov 23 15:20:28 localhost kernel: an0: bpf attached
....

But running the same software:

g1-15(5.2)[6] uname -a
FreeBSD g1-15.catwhisker.org 5.2-BETA FreeBSD 5.2-BETA #1: Sun Nov 23 11:49:39 PST 2003     root at g1-15.catwhisker.org:/common/S2/obj/usr/src/sys/LAPTOP_30W  i386
g1-15(5.2)[7] 

and trying a D-Link DFE-670TXD (it's a fairly vanilla 10/100 PCMCIA card
that works OK in -STABLE), I get:

Nov 23 15:19:18 localhost kernel: pccard1: CIS version PCCARD 2.0 or 2.1
Nov 23 15:19:18 localhost kernel: pccard1: CIS info: D-Link, DFE-670TXD, PC Card
Nov 23 15:19:18 localhost kernel: pccard1: Manufacturer code 0x149, product 0x4530
Nov 23 15:19:18 localhost kernel: pccard1: function 0: network adapter, ccr addr 400 mask b
Nov 23 15:19:18 localhost kernel: pccard1: function 0, config table entry 32: I/O card; irq mask befc; iomask 5, iospace 0-1f; mwait_required io16 irqlevel
Nov 23 15:19:18 localhost kernel: pccard1: function 0, config table entry 1: I/O card; irq mask befc; iomask a, iospace 300-31f; mwait_required io16 irqlevel
Nov 23 15:19:18 localhost kernel: pccard1: function 0, config table entry 2: I/O card; irq mask befc; iomask a, iospace 320-33f; mwait_required io16 irqlevel
Nov 23 15:19:18 localhost kernel: pccard1: function 0, config table entry 3: I/O card; irq mask befc; iomask a, iospace 340-35f; mwait_required io16 irqlevel
Nov 23 15:19:18 localhost kernel: pccard1: function 0, config table entry 4: I/O card; irq mask befc; iomask a, iospace 380-39f; mwait_required io16 irqlevel
Nov 23 15:19:18 localhost kernel: ed1: <D-Link DFE-670TXD> at port 0x100-0x11f irq 11 function 0 config 32 on pccard1
Nov 23 15:19:18 localhost kernel: device_probe_and_attach: ed1 attach returned 6


As you see, both tried to use IRQ 11; one succeeded, while the other did
not.  I don't have reason to believe that it's a problem with IRQ
allocation; here's what "vmstat -i" says with the Cisco/Aironet card
inserted:

g1-15(5.2)[7] vmstat -i
interrupt                          total       rate
irq0: clk                        1567994        101
irq1: atkbd0                       21688          1
irq5: uhci0 pcm0                      15          0
irq6: fdc0                             1          0
irq8: rtc                        2007040        130
irq11: cbb0 cbb1                   61665          4
irq12: psm0                       109761          7
irq13: npx0                            1          0
irq14: ata0                        39264          2
Total                            3807429        247
g1-15(5.2)[8] 

Is anyone else either seeing this kind of failure or getting the device
to work?

What other information should I be checking out to get to the root cause
of the problem?

Thanks,
david
-- 
David H. Wolfskill				david at catwhisker.org
If you want true virus-protection for your PC, install a non-Microsoft OS
on it.  Plausible candidates include FreeBSD, Linux, NetBSD, OpenBSD, and
Solaris (in alphabetical order).