From owner-freebsd-current@FreeBSD.ORG Fri Jun 15 10:39:55 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 752C816A46B for ; Fri, 15 Jun 2007 10:39:55 +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 10EB813C4B0 for ; Fri, 15 Jun 2007 10:39:50 +0000 (UTC) (envelope-from thompsa@freebsd.org) Received: by heff.fud.org.nz (Postfix, from userid 1001) id 942AE1CC58; Fri, 15 Jun 2007 22:39:48 +1200 (NZST) Date: Fri, 15 Jun 2007 22:39:48 +1200 From: Andrew Thompson To: Stefan Ehmann Message-ID: <20070615103948.GC18932@heff.fud.org.nz> References: <200706141641.54668.shoesoft@gmx.net> <467169F6.7020206@errno.com> <200706151044.32493.shoesoft@gmx.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200706151044.32493.shoesoft@gmx.net> User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-current@freebsd.org Subject: Re: LOR in iwi with new 802.11 work 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, 15 Jun 2007 10:39:55 -0000 On Fri, Jun 15, 2007 at 10:44:31AM +0200, Stefan Ehmann wrote: > On Thursday 14 June 2007 18:16:54 Sam Leffler wrote: > > Stefan Ehmann wrote: > > > After the system is up for about 5 minutes, I see this LOR. Haven't seen > > > it posted yet. > > > > > > Stefan > > > > > > lock order reversal: > > > 1st 0xc2e4700c ieee80211com (802.11 com lock) > > > @ /usr/src/sys/net80211/ieee80211_scan.c:523 > > > 2nd 0xc2e48400 iwi0 (network driver) > > > @ /usr/src/sys/modules/iwi/../../dev/iwi/if_iwi.c:1908 > ... > > > > Yes, known and can safely be ignored. > > Okay, thanks. > > Another problem I've noticed (don't want to start a new thread): > > Before the latest commit, I've never seen dropouts in the connnection. > > But now I've seen for the second time that the connection drops for some > seconds. ifconfig shows no IP address. At least it recovers, but open > connections die. > > In dmesg I see: > > Jun 15 10:34:25 something kernel: iwi0: firmware stuck in state 4, resetting > Jun 15 10:34:25 something kernel: iwi0: link state changed to DOWN > Jun 15 10:34:28 something kernel: iwi0: link state changed to UP > > Is this a known issue? Do you need any more info? It appears to get stuck in background scanning. How often does it happen? If you could set debug.iwi=3 and then email the logs for a couple of iterations of the reset. cheers, Andrew