Date: Sat, 17 Feb 2001 00:00:53 -0700 From: Warner Losh <imp@harmony.village.org> To: Julian Elischer <julian@elischer.org> Cc: Gerhard Sittig <Gerhard.Sittig@gmx.net>, current@FreeBSD.ORG Subject: Re: linksys Etherfast.. broken? Message-ID: <200102170700.f1H70rW84857@harmony.village.org> In-Reply-To: Your message of "Fri, 16 Feb 2001 21:35:24 PST." <3A8E0D9C.261A0259@elischer.org> References: <3A8E0D9C.261A0259@elischer.org> <3A896E33.8AC84353@elischer.org> <3A89C231.D03793D4@westmarsh.com> <20010214211548.B15618@speedy.gsinet> <20010216211610.B20830@speedy.gsinet>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <3A8E0D9C.261A0259@elischer.org> 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200102170700.f1H70rW84857>