From owner-freebsd-wireless@FreeBSD.ORG Sat Aug 18 06:15:10 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2A285106564A for ; Sat, 18 Aug 2012 06:15:10 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id F16CC8FC12 for ; Sat, 18 Aug 2012 06:15:09 +0000 (UTC) Received: by dadr6 with SMTP id r6so1245648dad.13 for ; Fri, 17 Aug 2012 23:15:09 -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 :x-google-sender-auth:message-id:subject:from:to:content-type; bh=8/CaZj+tfqWC+Q6oYiqsoHW3/qS0XYIGChMUR3L/Ov8=; b=pFNXtLf/er21gCUsyoWIu005UFrD29K6RYNGIUdVP2x6sNoAt5hjZn0jB8t893yY4n yr9lWIswprfwqymieJogQ6ewgOsdaF/jXR4CRtiZGTxvayASncZOJBPWgs5hjM6KoSDh qpj3d6ZQYohi/ZIhB9hJCfeyOw4hnrFF9eiN6M34PBB0D7b+67pBKeIzW6pV7uO8remV ECiQ7B9CwN1qRDqYsoWQocY5Gh5Uq2ho6TPTnUuYHv/XMpcgK+nWkJZaHU6u2pOIqAYE +fZSNnTJwWD9A9a/tRhEWDatXSsFniS9icuOUQiDVyZL7T7JjVxny5HNCkODWNlgLkeC eM5Q== MIME-Version: 1.0 Received: by 10.68.236.102 with SMTP id ut6mr17187904pbc.113.1345270509321; Fri, 17 Aug 2012 23:15:09 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.43.169 with HTTP; Fri, 17 Aug 2012 23:15:09 -0700 (PDT) In-Reply-To: References: Date: Fri, 17 Aug 2012 23:15:09 -0700 X-Google-Sender-Auth: Vw01HheKtbwI4WhcMY8-4VCmXKU Message-ID: From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: net80211/driver LORs: http://wiki.freebsd.org/WiFiDebugging X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Sat, 18 Aug 2012 06:15:10 -0000 .. so the first LOR is between node table lock and comlock - the former in ieee80211_timeout_stations() and the latter in ieee80211_set_tim(). So, something is holding the comlock when the node table lock is being grabbed. Where is that happening? Would someone like to tackle that particular issue? Eg, what about printing out a witness backtrace if the comlock is held when the node table lock is held? And vice versa? Just to try and figure out who is holding things incorrectly? Adrian