Date: Thu, 08 Sep 2005 08:32:50 -0700 From: Sam Leffler <sam@errno.com> To: Brooks Davis <brooks@one-eyed-alien.net> Cc: incmc@gmx.de, "M. Warner Losh" <imp@bsdimp.com>, freebsd-current@freebsd.org Subject: Re: Default route doesn't change to wireless device (ath0) Message-ID: <432059A2.3020408@errno.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>
index | next in thread | previous in thread | raw e-mail
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. Ah, I don't believe I said there was a bug specific to thinkpads; I only said that I had observed issues with the em devices on my thinkpads. > > 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. Some drivers do some form of polling but I believe we could correct many issues with a little documentation and some TLC. The drivers I've looked at typically are plastered with comments about workarounds for detecting link state changes. Samhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?432059A2.3020408>