From owner-freebsd-current@FreeBSD.ORG Thu Sep 8 15:25:53 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 43E1F16A41F for ; Thu, 8 Sep 2005 15:25:53 +0000 (GMT) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF44843D46 for ; Thu, 8 Sep 2005 15:25:52 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.200] ([10.0.0.200]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id j88FPj6j004067 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 8 Sep 2005 08:25:46 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <432059A2.3020408@errno.com> Date: Thu, 08 Sep 2005 08:32:50 -0700 From: Sam Leffler User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050327) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brooks Davis 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> In-Reply-To: <20050908150412.GA31354@odin.ac.hmc.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: incmc@gmx.de, "M. Warner Losh" , freebsd-current@freebsd.org Subject: Re: Default route doesn't change to wireless device (ath0) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Sep 2005 15:25:53 -0000 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 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. Sam