Date: Thu, 7 Nov 2013 18:45:50 GMT From: Gavin Atkinson <gavin@FreeBSD.org> To: freebsd-gnats-submit@FreeBSD.org Subject: kern/183759: [iwn] [wlan] Interface dies, OACTIVE set on wlan0 Message-ID: <201311071845.rA7Ijo7I060267@oldred.freebsd.org> Resent-Message-ID: <201311071850.rA7Io0Ik089862@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 183759 >Category: kern >Synopsis: [iwn] [wlan] Interface dies, OACTIVE set on wlan0 >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Nov 07 18:50:00 UTC 2013 >Closed-Date: >Last-Modified: >Originator: Gavin Atkinson >Release: head >Organization: >Environment: r254080 >Description: With iwn(4) (Intel 5100) I often see the interface disassociate from the WPA2 11n network it is associated with. wpa_supplicant gives reason=0. When this happens, according to ifconfig OACTIVE is set on wlan0, and not on iwn0. Once in this state, it seems that destroying wlan0 and recreating it is necessary in order to get things working again. I have started binary searching for the commit that introduced this behaviour. So far, I have not yet managed to recreate it with r252500, but it can happen within 10 minutes on r254080. I have not yet proven it, but I believe that disabling ht (with ifconfig wlan0 -ht) prevents it from happening. Gavin >How-To-Repeat: Associate to 11n network, pass some data, wait. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201311071845.rA7Ijo7I060267>