In message <[EMAIL PROTECTED]> Julian Elischer writes: : It looks to me like the interrupt vector is not being registered.. : I'll try figut out what I've screwed up in the config. timeouts usually mean one of two things. With ed devices, they could be the new dlink based chips (fa-410, dlink etherfast, some linksys card) or you have a bad IRQ configured that another hunk of hardware is driving. The interrupt vector almost certainly is getting registered. It just isn't being called. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- linksys Etherfast.. broken? Julian Elischer
- Re: linksys Etherfast.. broken? Warner Losh
- Re: linksys Etherfast.. broken? Pierre Y. Dampure
- Re: linksys Etherfast.. broken? Julian Elischer
- Re: linksys Etherfast.. broken? Gerhard Sittig
- Re: linksys Etherfast.. broken? Gerhard Sittig
- Re: linksys Etherfast.. broken? Julian Elischer
- Re: linksys Etherfast.. broken? Gerhard Sittig
- Re: linksys Etherfast.. broken... Julian Elischer
- Re: linksys Etherfast.. broken? Warner Losh
- Re: linksys Etherfast.. broken? Warner Losh
- Re: linksys Etherfast.. broken? Julian Elischer
- Re: linksys Etherfast.. broken? Warner Losh