From owner-freebsd-wireless@FreeBSD.ORG Tue Feb 19 16:48:13 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 76552B6C for ; Tue, 19 Feb 2013 16:48:13 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) by mx1.freebsd.org (Postfix) with ESMTP id DCB2C369 for ; Tue, 19 Feb 2013 16:48:12 +0000 (UTC) Received: by mail-wg0-f41.google.com with SMTP id ds1so3779840wgb.4 for ; Tue, 19 Feb 2013 08:48:12 -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=hlt3Ii0bBOqQKzAfN7AE4AvPulFT9gVcOUylWfOESOg=; b=JU7RGHUzUsggW8EnrGu4ybXe4puAxGGJ28MKODm0BDAXRJEkHXyjM06C1WAy0yyXcv 2Cb+ybHvxoRFUb2R6yrHqEOccns8VwHwgzzKMe6gAc6MBJdmoa3HnwQa1lYyPcmODMQ/ Mf/gH6qGVt3YmpWjRcr/yGOIsOqK1zJZQsrNfaMONXNJ3MvfmhZP0cfxCKVHzaH3EAA1 vBkMKATQW08DjTdIe/EK/X0CmRXCbcQnNHLGd+dvrA3Lu8SvU7ECOMfxtj1E2ybgKan2 UYkzTTSGt7r7PfrzSACo+SPVC9RV43Lpcj8ROOm0tXN7YVtuYLl6/oK+1VnZK56xOkXT VwLA== MIME-Version: 1.0 X-Received: by 10.180.91.106 with SMTP id cd10mr9838374wib.6.1361292492061; Tue, 19 Feb 2013 08:48:12 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.236.88 with HTTP; Tue, 19 Feb 2013 08:48:11 -0800 (PST) In-Reply-To: References: <51175C69.6050003@gmx.net> <51189E1E.70206@gmx.net> <51194795.5070500@gmx.net> <511E910D.1080901@gmx.net> <511E9446.4070708@gmx.net> <511E9615.3020007@gmx.net> <512376AB.10003@gmx.net> <5123A714.6050105@gmx.net> Date: Tue, 19 Feb 2013 08:48:11 -0800 X-Google-Sender-Auth: 77M1ucThm4mm4wXx0YuQV5XEnnU Message-ID: Subject: Re: ath0: device timeout on 9.1-RELEASE From: Adrian Chadd To: Kamil Szczesny 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: Tue, 19 Feb 2013 16:48:13 -0000 On 19 February 2013 08:32, Adrian Chadd wrote: > 0x2003 will make things appear. Just do an active scan (ifconfig wlanX > scan) to ensure something happens. Hi, (Cc'ing the list so people can see the progress of debugging this.) It looks like this happens: * a channel change occurs; * beacons are received; * probe request frames are queued to the hardware; * but before the TX completes (either fail or succeed) the queue gets stopped and reset. So either it's not going out, or the timers are all screwed up and it's immediately resetting. It's hard to tell given the current logging (ie, no microsecond resolution timestamps, sigh.) Can you try changing the timecounter? sysctl kern.timecounter set it to something obviously inefficient, like "i8254": sysctl kern.timecounter.hardware=i8254 .. and similarly the eventtimer: sysctl kern.eventtimer.timer=i8254 and see if that changes things. It looks like the scan times default to 200ms per channel in ieee80211_scan_sta.c. It's tunable, but the scan code in ifconfig doesn't have any option to change it. 200ms should be plenty of time to finish calibrating and start sending frames though.. Thanks, Adrian