From owner-freebsd-current Fri Feb 16 23: 1:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 0DD4937B491 for ; Fri, 16 Feb 2001 23:01:11 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f1H70rW84857; Sat, 17 Feb 2001 00:00:53 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200102170700.f1H70rW84857@harmony.village.org> To: Julian Elischer Subject: Re: linksys Etherfast.. broken? Cc: Gerhard Sittig , current@FreeBSD.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> Date: Sat, 17 Feb 2001 00:00:53 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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