From owner-freebsd-current@FreeBSD.ORG Fri Aug 31 01:39:06 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B22D16A419 for ; Fri, 31 Aug 2007 01:39:06 +0000 (UTC) (envelope-from thompsa@FreeBSD.org) Received: from heff.fud.org.nz (203-109-251-39.static.bliink.ihug.co.nz [203.109.251.39]) by mx1.freebsd.org (Postfix) with ESMTP id 068B113C46C for ; Fri, 31 Aug 2007 01:39:05 +0000 (UTC) (envelope-from thompsa@FreeBSD.org) Received: by heff.fud.org.nz (Postfix, from userid 1001) id 5D99D1CC58; Fri, 31 Aug 2007 13:38:47 +1200 (NZST) Date: Fri, 31 Aug 2007 13:38:47 +1200 From: Andrew Thompson To: haro@kgt.co.jp Message-ID: <20070831013847.GA5577@heff.fud.org.nz> References: <20070830.043519.109271629.haro@kgt.co.jp> <20070829215249.GA54430@heff.fud.org.nz> <20070830.143335.89920717.haro@kgt.co.jp> <20070831.103257.52837654.haro@kgt.co.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070831.103257.52837654.haro@kgt.co.jp> User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-current@freebsd.org Subject: Re: LOR with iwi (was Re: Panic with iwi) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Aug 2007 01:39:06 -0000 On Fri, Aug 31, 2007 at 10:32:57AM +0900, haro@kgt.co.jp wrote: > Hi Andrew, > > FYI, I just got following LOR with iwi, at the hotel: > > > lock order reversal: > 1st 0xc368e00c ieee80211com (802.11 com lock) @ net80211/ieee80211_scan.c:523 > 2nd 0xc368f400 iwi0 (network driver) @ /home/haro/tmp/sys-7/modules/iwi/../../dev/iwi/if_iwi.c:1907 > KDB: stack backtrace: > db_trace_self_wrapper(c07d80aa,db312a4c,c05c1cce,c07da553,c368f400,...) at db_trace_self_wrapper+0x26 > kdb_backtrace(c07da553,c368f400,c36771a0,c0997ade,c09974ca,...) at kdb_backtrace+0x29 Thanks. This one is known and considered harmless, it will be fixed up after 7.0 is out and the tree unfrozen. Andrew