From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 9 03:07:41 2014 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 0AFC5AFA; Wed, 9 Apr 2014 03:07:41 +0000 (UTC) Received: from mail-ve0-x236.google.com (mail-ve0-x236.google.com [IPv6:2607:f8b0:400c:c01::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A8B4E1CC3; Wed, 9 Apr 2014 03:07:40 +0000 (UTC) Received: by mail-ve0-f182.google.com with SMTP id jw12so1547693veb.41 for ; Tue, 08 Apr 2014 20:07:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=s/Xd/HTGMH/eCrrgGvQLLkiVoB5v7XEhP5qIp+dTxXQ=; b=jWpNLyiA2X9KfONiXpP8ouvluL1GTvMfmZbe/wJWbJzct3zvH6YRBaDN5anaqILAWV d0w1UkamQSCn+7NfkQSUNyGzby+0MLRSsILz48ddyt0NvFfXWeDJYY83q0gEoM5V1aFp JC1LN6+BlDlnOczwCp50zGgR5akkZQHNUIHbnTcR6Vq21q42xtiQuBU6EmD3yvHDJjVz R8aMI3QcI0sHzX5gufmEzgFTHJUwN14moS7OoEK8UsZt0+VokSwPC31xwJK/nOeO6u6e gRpYMPwi8XnPS1GxLMIaWy6F1qMXFH+SkKJjWKwHJWaXltXK5u73d6+c1sI6wz8KvXzu K1Bg== MIME-Version: 1.0 X-Received: by 10.58.185.145 with SMTP id fc17mr6663559vec.14.1397012859810; Tue, 08 Apr 2014 20:07:39 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.220.113.199 with HTTP; Tue, 8 Apr 2014 20:07:39 -0700 (PDT) In-Reply-To: <20140409093642.19c2f5cb@X220.alogt.com> References: <20140331073054.5d7642d6@X220.alogt.com> <1397006320.5173.2.camel@powernoodle.corp.yahoo.com> <20140409093642.19c2f5cb@X220.alogt.com> Date: Tue, 8 Apr 2014 20:07:39 -0700 X-Google-Sender-Auth: mPhUhv3gIw8k-iXcJuVpk6af85Y Message-ID: Subject: Re: iwn0 hangs randomly when starting the machine From: Adrian Chadd To: Erich Dollansky Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" , sean bruno X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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: Wed, 09 Apr 2014 03:07:41 -0000 Coexistence is to deal with the fact that a 40MHz channel may overlap a 20MHz-only AP in the extension channel. If the AP finds a 20MHz AP in the extension channel (ie, the other half of its 40MHz) channel then it'll flip itself to 20MHz. If it determines it isn't there any more, it'll flip the BSS to the 40MHz channel. Now, why the hell it's causing the connection to fail? I have no idea. can someone file a PR that says it's all busted with 40MHz coxistence enabled? We can then start debugging from that position. -a