Date: Wed, 27 Feb 2013 19:27:21 -0800 From: Adrian Chadd <adrian@freebsd.org> To: Derrick Dantavious Edwards <dantavious313@gmail.com> Cc: freebsd-wireless@freebsd.org Subject: Re: ath0 Device Timeout Issues Message-ID: <CAJ-Vmo=Xy9jsLaZwewWizFnTj3Cck0VWV5nce_iOV%2BXEM422PA@mail.gmail.com> In-Reply-To: <2287510.yA44TplU79@zeus> References: <1413125.YF2HxR6oBY@zeus> <CAJ-Vmo=93z75Hoyz1OMyZ21aXYuq-eOS-PrL0iamg9yMMKjO7Q@mail.gmail.com> <2287510.yA44TplU79@zeus>
next in thread | previous in thread | raw e-mail | index | archive | help
On 27 February 2013 18:59, Derrick Dantavious Edwards <dantavious313@gmail.com> wrote: > > Yes. When I start the system, I get those messages. Wireless Link fails to > establish thus causing all services requring link to fail....ie NFS . Soon > after I am at the command prompt or GUI, I can ping hosts however, I have to > /etc/rc.d/mountlate to get remote filesystems connected. Thanks for your > assistance. > right. Well, those network services should only (re)start once the network link is up. But as to why the network link is taking a while to come up; I'm not sure. The device timeouts are a known race. It's not indicative that a device timeout actually did occur. Fixing the watchdog to be actually correct is on my TODO list but it's fallen behind in priority. I have a feeling that the probe requests aren't being given enough time to go out. Would you mind trying to change the eventtimer / timesource (sysctl kern.eventtimer and sysctl kern.timecounter); see if that helps things along? Thanks, adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=Xy9jsLaZwewWizFnTj3Cck0VWV5nce_iOV%2BXEM422PA>