Date: Thu, 08 Sep 2005 18:40:25 +0300 From: Niki Denev <nike_d@cytexbg.com> To: freebsd-current@freebsd.org Subject: Re: Default route doesn't change to wireless device (ath0) Message-ID: <43205B69.4050508@cytexbg.com> In-Reply-To: <20050908150412.GA31354@odin.ac.hmc.edu> References: <20050907194130.GA2436@odin.ac.hmc.edu> <200509072223.20560.incmc@gmx.de> <20050907211811.GA19570@odin.ac.hmc.edu> <20050908.011138.121215369.imp@bsdimp.com> <20050908150412.GA31354@odin.ac.hmc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Brooks Davis wrote: > On Thu, Sep 08, 2005 at 01:11:38AM -0600, M. Warner Losh wrote: > >>In message: <20050907211811.GA19570@odin.ac.hmc.edu> >> Brooks Davis <brooks@one-eyed-alien.net> writes: >>: Hmm, upon further testing, I think there may be a problem with the >>: fxp(4) driver. >> >>You mean like the driver never asynchronously querries the miibus to >>find out what the state of the link is when it isn't in the UP state? > > > I certainly see that on the em nics on my laptop and I've heard claims > of a similar problems with fxp nics. I don't see it with other em > nics. Sam reports that it seems to be a bug specific to the em hardware > in thinkpads. That's not the only issue in this case, but it's one of > them. > I've experienced the same problem with the fxp nic on my thinkpad. > I suspect think we may need to poll the media state periodicly on > some devices and fake up link state notifications as a workaround for > incorrect drivers. > > -- Brooks > --niki
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43205B69.4050508>