From owner-freebsd-wireless@FreeBSD.ORG Tue Nov 12 20:28:58 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 571418B5; Tue, 12 Nov 2013 20:28:58 +0000 (UTC) Received: from mail-ee0-x22f.google.com (mail-ee0-x22f.google.com [IPv6:2a00:1450:4013:c00::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C06AE23D1; Tue, 12 Nov 2013 20:28:57 +0000 (UTC) Received: by mail-ee0-f47.google.com with SMTP id c13so3388703eek.20 for ; Tue, 12 Nov 2013 12:28:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=YDw7HXRMf8Hz7xyFRUBlUE+4Bj9gJ+7dooF6w3UctCY=; b=VLHveip4ZzrFx9/eNGX7GOlC/zxAKOv84/uuBz3oo5zZY2PX7Q0WuWCk9PAEjc8WZL NAyYRacaGyimxWRT3n8XgRcDvtPMSKN6sJECuesv2O/ZJJoawhsME5WtM6OX2QedJHaL 3bKNc1p2h1skKY7rL5bPIL7p41bI+NnW+v8USy4n4FJwvyfkdq/RgDInJ1ghZIjC9r8o Mw89/K/Chp1jo1Vhg+Sn6+X4wUewVEQGyfx/8GVcQsrFIxAX9+7xVl+whtW2Ako+CMa3 mJij6wBvytE1lWByNNLcaoJ67NnhSicrwdnQU3yMIAjaMMbmp0930gfgBF/TdU8nOhZ9 kZhA== MIME-Version: 1.0 X-Received: by 10.14.111.129 with SMTP id w1mr4167330eeg.83.1384288136180; Tue, 12 Nov 2013 12:28:56 -0800 (PST) Received: by 10.14.127.195 with HTTP; Tue, 12 Nov 2013 12:28:56 -0800 (PST) In-Reply-To: References: Date: Tue, 12 Nov 2013 12:28:56 -0800 Message-ID: Subject: Re: [iwn] Cedric's stuff is in -HEAD From: hiren panchasara To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.16 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, 12 Nov 2013 20:28:58 -0000 On Tue, Nov 12, 2013 at 12:19 PM, Adrian Chadd wrote: > On 12 November 2013 11:13, hiren panchasara wrote: >> On Tue, Nov 12, 2013 at 10:45 AM, Adrian Chadd wrote: >>> Run with wlandebug +assoc +state +debug +output +scan +crypto >> >> http://people.freebsd.org/~hiren/20131112_iwnfail_atwork.txt > > What's this showing? What was going on at this time? I keep pings going on another window just to see when it stops. It was doing alright (pings going through) and suddenly "stops working" around following lines in logs: Nov 12 10:59:51 flymockour-l7 kernel: wlan0: ieee80211_bg_scan: active scan, ticks 7165936 duration 150 Nov 12 10:59:51 flymockour-l7 kernel: wlan0: [6c:f3:7f:4d:88:47] send QoS null data frame on channel 1, pwr mgt ena and then it tries scanning and what not but never recovers. Funny (read annoying) thing is, its not failing in the same way every time it disconnects. I do not see the same pattern. And by "stops working" I see, it still has ip and ssid but "status: no carrier" in ifconfig. > >> Thanks a bunch Adrian! > > so, I have a feeling that for "best" iwn(4) behaviour, we should > likely extend net80211 to not do its own scan stuff (by putting the > VAP into power save mode whilst doing scanning) but just to fire off a > scan request. I _think_ iwn(4) will do it itself. > > We should however still fix the scan code to not be a racy, unpredictable thing. I am not sure if I follow. Any more clues you can throw based on the logs? Thanks again, Hiren