From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 23 01:18:27 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3417D5CD; Wed, 23 Oct 2013 01:18:27 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qa0-x22d.google.com (mail-qa0-x22d.google.com [IPv6:2607:f8b0:400d:c00::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D5591268D; Wed, 23 Oct 2013 01:18:26 +0000 (UTC) Received: by mail-qa0-f45.google.com with SMTP id ii20so3849549qab.18 for ; Tue, 22 Oct 2013 18:18:26 -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=EAaaBS6C0UFYdUKrtFZ0lb+L9Jk1MzO8AMEY3FHr+x8=; b=CCuGf7cWcWyjkmtWWXjca/aX1/fdHgr5HSm/46SW8cYMwJ5Xbk/6CnuXhCSVbvyD11 9dL7T9MyRrpnWGcXNvsGyOu4F/Jf7c/0httrEDPaN2Dk+yOFdpNY/pjBGljF4LSDYyaU l9yr6axv5rZ0ScerJPzzmgdlxGQ9Rt/xGcmPwqpSplM4PXlIcA4hcObwIcxG0Suvoy9t eb5Jq+hvFiZ5MddRNgMFJwh+uBgN94fykhHki7fMwgp/2+OXaNBb2/QD2OtCbFQNGZd1 qJhG9YLmFsFf9vJy4RT8e3dMCERktGYKkH1FcpUplPwjV+aIpzAFlWQKS6rRkArIy+M9 eXFg== MIME-Version: 1.0 X-Received: by 10.224.36.201 with SMTP id u9mr757200qad.76.1382491106050; Tue, 22 Oct 2013 18:18:26 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Tue, 22 Oct 2013 18:18:25 -0700 (PDT) In-Reply-To: References: Date: Tue, 22 Oct 2013 18:18:25 -0700 X-Google-Sender-Auth: DvGJb_WlJ7MkU3exnbX1O1DWZxM Message-ID: Subject: Re: 9.2-STABLE r255918 with GENERIC and iwn - core dump From: Adrian Chadd To: claudiu vasadi Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-hackers@freebsd.org" , "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: Wed, 23 Oct 2013 01:18:27 -0000 Grr, it's slightly more complicated than that. That whole timer mess is actually used for two things: * if the management transmit succeeds - it acts as a short-interval (a few seconds) timer to ensure that the probe request ends up providing some response that transitions to auth; otherwise it aborts and transitions back to the SCAN state; * if the management transmit fails - it immediately transitions back to SCAN. So, the "correct" fix involves correctly locking things and turning that timer into a "if I fail to transition into a run state, then just go back to scanning" timeout. It sucks and it's going to take an evening of deep thought to figure out the correct solution to. Thanks for reminding me about this mess! -adrian