On Wed, 23 Mar 2005 12:53:39 -0500, Christos Zoulas <christos@zoulas.com> wrote:
> The linksys appears to have bad CIS. Which is the cardbus information
> space. We have to parse this to find stuff like power, mac address,
> memory and i/o space, etc. If it is bad, then it will need a kludge in
> the parser to ignore the bad tuple and continue.
> 
> |     cbb0: wait took 0.007948s
> |     ex0: interrupting at 11
> 
> This looks fine.
> 
> | So it still looks like an IRQ problem?
> |
> I don't think that using irq 11 would be an issue. What does the
> rest of the ex0 messages look like? What happens if you ifconfig
> ex0 a.b.c.d and then try to ping a.b.c.d?

# ifconfig ex0 10.0.0.1
cbb0: wait took 0.009797s
ex0: interrupting at 11
# Mar 23 12:40:36 honey-brown /netbsd: cbb0: wait took 0.009797s
Mar 23 12:40:36 honey-brown /netbsd: ex0: interrupting at 11
Mar 23 12:40:41 honey-brown /netbsd: ex0: device timeout
Mar 23 12:40:41 honey-brown /netbsd: ex0: device timeout

# ping 10.0.0.1
PING 10.0.0.1 (10.0.0.1): 56 data bytes
64 bytes from 10.0.0.1: icmp_seq=0 ttl=255 time=0.053ms
64 bytes from 10.0.0.1: icmp_seq=1 ttl=255 time=0.062ms
^C
----10.0.0.1 PING Statistics----
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.053/0.058/0.062/0.006 ms
# ifconfig ex0
ex0: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        capabilities=7<IP4CSUM,TCP4CSUM,UDP4CSUM>
        enabled=0
        address: 00:50:da:da:ac:d2
        media: Ethernet autoselect (10baseT)
        status: active
        inet 10.0.0.1 netmask 0xff000000 broadcast 10.255.255.255
        inet6 fe80::250:daff:feda:acd2%ex0 prefixlen 64 scopeid 0x2

If I try and bring the interface up with dhcp I get "last message
repeated 3 times" and "ex0: device timeout"

Thanks,
-Zach