From owner-freebsd-wireless@FreeBSD.ORG Thu Feb 28 03:27:23 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 973F09FC for ; Thu, 28 Feb 2013 03:27:23 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x235.google.com (mail-we0-x235.google.com [IPv6:2a00:1450:400c:c03::235]) by mx1.freebsd.org (Postfix) with ESMTP id 36AB875D for ; Thu, 28 Feb 2013 03:27:23 +0000 (UTC) Received: by mail-we0-f181.google.com with SMTP id t44so1100291wey.12 for ; Wed, 27 Feb 2013 19:27:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=3do/tfB5DN3sp0n5u/XJ/ryk/MHdGKVNhvY7EPb5IOo=; b=CSV6oZhO3CXEzYMQDIMBqGJ/u31HCvAWTt1d0Ng6vdhllz+/N3bYeCcWgmzWaHuyO7 M3kU3w0sdvE9eSOl6nzYiLraHdRqTrP0LcMA178e8Gcjv1k5kTsX0BkU3pBJk6PHNMCG oABhMxoc01s1Rg+ejOlERynRSkS/EK2CVw9ERxtqQ7TOuT3LDgR2djhHCPUhHc/7yXwd Weph25vQyVbogmf28dpsLyntOVnMatwr9QpKzXrqZpS9Y4wG5bPy6voHisCllocwJObs m3nMBozixLNc8ZWLg3Zu9uSkdGrSM2LljNxaos38W49zkOFX/I8LVIgBOPnjItrfaVLt lWAg== MIME-Version: 1.0 X-Received: by 10.180.108.229 with SMTP id hn5mr2744330wib.28.1362022041777; Wed, 27 Feb 2013 19:27:21 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.114.201 with HTTP; Wed, 27 Feb 2013 19:27:21 -0800 (PST) In-Reply-To: <2287510.yA44TplU79@zeus> References: <1413125.YF2HxR6oBY@zeus> <2287510.yA44TplU79@zeus> Date: Wed, 27 Feb 2013 19:27:21 -0800 X-Google-Sender-Auth: T65aMjNigVJgv6zphnqShgVNKSo Message-ID: Subject: Re: ath0 Device Timeout Issues From: Adrian Chadd To: Derrick Dantavious Edwards Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2013 03:27:23 -0000 On 27 February 2013 18:59, Derrick Dantavious Edwards 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