From owner-freebsd-current@FreeBSD.ORG Fri Jun 15 16:23:10 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 7162D16A469 for ; Fri, 15 Jun 2007 16:23:10 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 4A4DE13C489 for ; Fri, 15 Jun 2007 16:23:10 +0000 (UTC) (envelope-from sam@errno.com) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id l5FGN9Gd016548 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 15 Jun 2007 09:23:10 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <4672BD16.70707@errno.com> Date: Fri, 15 Jun 2007 09:23:50 -0700 From: Sam Leffler User-Agent: Thunderbird 2.0.0.0 (X11/20070530) MIME-Version: 1.0 To: Stefan Ehmann References: <200706141641.54668.shoesoft@gmx.net> <467169F6.7020206@errno.com> <200706151044.32493.shoesoft@gmx.net> In-Reply-To: <200706151044.32493.shoesoft@gmx.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 16:23:10 -0000 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? Andrew already responded but if you want to disable bg scanning do: ifconfig iwi0 -bgscan though that won't help resolve the issue. You can also see what's going on at the 802.11 level with: wlandebug -i iwi0 scan FWIW I ran my 2195 card for many days w/ bg scanning and saw zero dropouts (including doing a full xorg portupgrade over wireless). My canonical test is to associate, run ping to a station on the far side of the ap, and then verify bg scanning doesn't cause any ping packets to be dropped. Sam