From owner-freebsd-wireless@FreeBSD.ORG Thu Feb 28 11:20:27 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 09C57D0A; Thu, 28 Feb 2013 11:20:27 +0000 (UTC) (envelope-from dantavious313@gmail.com) Received: from mail-gg0-x22b.google.com (mail-gg0-x22b.google.com [IPv6:2607:f8b0:4002:c02::22b]) by mx1.freebsd.org (Postfix) with ESMTP id B213D1BE7; Thu, 28 Feb 2013 11:20:26 +0000 (UTC) Received: by mail-gg0-f171.google.com with SMTP id j1so225554ggn.30 for ; Thu, 28 Feb 2013 03:20:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:cc:subject:date:message-id:user-agent :in-reply-to:references:mime-version:content-transfer-encoding :content-type; bh=hdmNVon1uavx8Euuk95+diAOglDqnEOAcj2yzedEJTU=; b=RydxwByROTuBiOoJS7wHqH4BuUdsJ5sdzJnR37WpfVqwPNVvBD4p7R/JJWWn/91Dps 2fe8O5aUXTcuO8MdF22FWaoUsHfMvU9V5yt3OuRiEo5ghnrrL02F3o7WqRG0TJThsiEo ao/fo04GeWQuymKLYkjrzCxYWhHGvOVwdxJf09qL0ywEmDpljGHs4wDPU5fMz5ZXbPyQ dkl07gOP04GsJsuqNYacG4fyd7xfrrzYGbnUvZYcF5miJoYI1o3VIi7iqUla5q0siqTq U6dBr/KrzAQMOkvdOa3Xm8TvV1UpOnC6F8qGvAsdB/JmJ8CufyiPCv96IuDT1+lzOQSv lpUg== X-Received: by 10.236.175.67 with SMTP id y43mr4285241yhl.162.1362050426245; Thu, 28 Feb 2013 03:20:26 -0800 (PST) Received: from zeus.localnet (c-71-226-137-213.hsd1.ga.comcast.net. [71.226.137.213]) by mx.google.com with ESMTPS id w2sm12680925yhh.7.2013.02.28.03.20.25 (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 28 Feb 2013 03:20:25 -0800 (PST) From: Derrick Dantavious Edwards To: Adrian Chadd Subject: Re: ath0 Device Timeout Issues Date: Thu, 28 Feb 2013 06:20:23 -0500 Message-ID: <7632564.pQ3RMLadSs@zeus> User-Agent: KMail/4.9.5 (FreeBSD/10.0-CURRENT; KDE/4.9.5; amd64; ; ) In-Reply-To: References: <1413125.YF2HxR6oBY@zeus> <2287510.yA44TplU79@zeus> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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 11:20:27 -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 Sure, I have no problem making a change. I placed the available options for my system below. Which do you prefer I use for this test? Derrick root@zeus:~ # sysctl kern.eventtimer kern.eventtimer.et.LAPIC.flags: 7 kern.eventtimer.et.LAPIC.frequency: 49887865 kern.eventtimer.et.LAPIC.quality: 600 kern.eventtimer.et.HPET.flags: 7 kern.eventtimer.et.HPET.frequency: 14318180 kern.eventtimer.et.HPET.quality: 550 kern.eventtimer.et.HPET1.flags: 3 kern.eventtimer.et.HPET1.frequency: 14318180 kern.eventtimer.et.HPET1.quality: 440 kern.eventtimer.et.HPET2.flags: 3 kern.eventtimer.et.HPET2.frequency: 14318180 kern.eventtimer.et.HPET2.quality: 440 kern.eventtimer.et.HPET3.flags: 3 kern.eventtimer.et.HPET3.frequency: 14318180 kern.eventtimer.et.HPET3.quality: 440 kern.eventtimer.et.HPET4.flags: 3 kern.eventtimer.et.HPET4.frequency: 14318180 kern.eventtimer.et.HPET4.quality: 440 kern.eventtimer.et.RTC.flags: 17 kern.eventtimer.et.RTC.frequency: 32768 kern.eventtimer.et.RTC.quality: 0 kern.eventtimer.et.i8254.flags: 1 kern.eventtimer.et.i8254.frequency: 1193182 kern.eventtimer.et.i8254.quality: 100 kern.eventtimer.choice: LAPIC(600) HPET(550) HPET1(440) HPET2(440) HPET3(440) HPET4(440) i8254(100) RTC(0) kern.eventtimer.singlemul: 2 kern.eventtimer.idletick: 0 kern.eventtimer.activetick: 1 kern.eventtimer.timer: LAPIC kern.eventtimer.periodic: 0 root@zeus:~ # sysctl kern.timecounter kern.timecounter.tc.HPET.mask: 4294967295 kern.timecounter.tc.HPET.counter: 2161173885 kern.timecounter.tc.HPET.frequency: 14318180 kern.timecounter.tc.HPET.quality: 950 kern.timecounter.tc.i8254.mask: 65535 kern.timecounter.tc.i8254.counter: 20336 kern.timecounter.tc.i8254.frequency: 1193182 kern.timecounter.tc.i8254.quality: 0 kern.timecounter.tc.ACPI-fast.mask: 16777215 kern.timecounter.tc.ACPI-fast.counter: 3908063 kern.timecounter.tc.ACPI-fast.frequency: 3579545 kern.timecounter.tc.ACPI-fast.quality: 900 kern.timecounter.tc.TSC-low.mask: 4294967295 kern.timecounter.tc.TSC-low.counter: 2410520996 kern.timecounter.tc.TSC-low.frequency: 1247196540 kern.timecounter.tc.TSC-low.quality: 1000 kern.timecounter.stepwarnings: 0 kern.timecounter.hardware: TSC-low kern.timecounter.choice: TSC-low(1000) ACPI-fast(900) i8254(0) HPET(950) dummy(-1000000) kern.timecounter.tick: 1 kern.timecounter.fast_gettime: 1 kern.timecounter.invariant_tsc: 1 kern.timecounter.smp_tsc: 1 kern.timecounter.tsc_shift: 1