From owner-freebsd-wireless@FreeBSD.ORG  Fri Jan 10 17:37:53 2014
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
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 086FAE49;
 Fri, 10 Jan 2014 17:37:53 +0000 (UTC)
Received: from mail-qe0-x232.google.com (mail-qe0-x232.google.com
 [IPv6:2607:f8b0:400d:c02::232])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id A8D201F20;
 Fri, 10 Jan 2014 17:37:52 +0000 (UTC)
Received: by mail-qe0-f50.google.com with SMTP id 1so4794323qec.23
 for <multiple recipients>; Fri, 10 Jan 2014 09:37:51 -0800 (PST)
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=i4JMFFw+ZHaMyIQqdMtj3ssURev2J3TUZBqx25FH1S4=;
 b=pE4GnmTR/IkpsLYgD08kWJL10vtS4xGYhK1Ko7GZ1d92sakZ/upAyL+bmDMrcnoac0
 qGULYw1LX906lESbSfR4Ez1VysAwfMBv37gkZuyaI3Eed3DM5jfRzOZRHX+0/pYlkYze
 e7ghEF/XNVv/cB5G/ZMcQRqZF9LaZsg7PObIuQQFM5tbPMOn+G3PgwrdKA0fXX9h+3/L
 uys13rXx0gEtZWY4t0drs0VD5bGwq6ZY9QgNTDp7/8Zgx4gQYLRlgrzKPxgxFb9xtIem
 0zcVAjToeoruFHlgIn0xSQhlL2ecknRWZggweiEH5zACov4hWf+QrBAqzOy0CgX8IDMw
 hc3Q==
MIME-Version: 1.0
X-Received: by 10.224.15.74 with SMTP id j10mr9789771qaa.26.1389375471888;
 Fri, 10 Jan 2014 09:37:51 -0800 (PST)
Sender: adrian.chadd@gmail.com
Received: by 10.224.52.8 with HTTP; Fri, 10 Jan 2014 09:37:51 -0800 (PST)
In-Reply-To: <e630ae96669b34cc3f2ba0efadee9aa1@mail.0x20.net>
References: <CAN6yY1ujxmUBo-jt8QRa6ozRk8otSX-4LHGum=4na9ObkEGxXQ@mail.gmail.com>
 <e630ae96669b34cc3f2ba0efadee9aa1@mail.0x20.net>
Date: Fri, 10 Jan 2014 09:37:51 -0800
X-Google-Sender-Auth: p-tU6DjT1yA84vuadhp6Mav8pD8
Message-ID: <CAJ-Vmo=mKRTR6vzCUUA5cR8rHDhnhcUcQj1DFCnkPwqqb6PBHg@mail.gmail.com>
Subject: Re: IWN hangs periodically on 10.0RC3
From: Adrian Chadd <adrian@freebsd.org>
To: Lars Engels <lars.engels@0x20.net>, Kevin Oberman <rkoberman@gmail.com>, 
 "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: FreeBSD Stable Mailing List <freebsd-stable@freebsd.org>
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." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless/>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jan 2014 17:37:53 -0000

.. when you see it hang, does anything get logged in dmesg (eg a
firmware panic) ?

Try recompiling your kernel with:

IEEE80211_DEBUG
IWN_DEBUG

That way it can be debugged :)

The first thing I'd check is whether there's more fun races going on
in the crypto code - try wlandebug +crypto .


-a