From owner-freebsd-current@FreeBSD.ORG Fri Jun 22 07:04:25 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 DAD8816A421 for ; Fri, 22 Jun 2007 07:04:25 +0000 (UTC) (envelope-from tataz@tataz.chchile.org) Received: from smtp5-g19.free.fr (smtp5-g19.free.fr [212.27.42.35]) by mx1.freebsd.org (Postfix) with ESMTP id A169413C468 for ; Fri, 22 Jun 2007 07:04:25 +0000 (UTC) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (tataz.chchile.org [82.233.239.98]) by smtp5-g19.free.fr (Postfix) with ESMTP id CF77443E4C; Fri, 22 Jun 2007 09:04:24 +0200 (CEST) Received: from obiwan.tataz.chchile.org (unknown [192.168.1.25]) by tatooine.tataz.chchile.org (Postfix) with ESMTP id 7CDA49B497; Fri, 22 Jun 2007 07:04:02 +0000 (UTC) Received: by obiwan.tataz.chchile.org (Postfix, from userid 1000) id 50E08405B; Fri, 22 Jun 2007 09:04:02 +0200 (CEST) Date: Fri, 22 Jun 2007 09:04:02 +0200 From: Jeremie Le Hen To: Stefan Ehmann Message-ID: <20070622070402.GA95204@obiwan.tataz.chchile.org> References: <200706141641.54668.shoesoft@gmx.net> <200706151044.32493.shoesoft@gmx.net> <4672BD16.70707@errno.com> <200706161415.15641.shoesoft@gmx.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200706161415.15641.shoesoft@gmx.net> User-Agent: Mutt/1.5.15 (2007-04-06) 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, 22 Jun 2007 07:04:25 -0000 Hi Stefan, On Sat, Jun 16, 2007 at 02:15:15PM +0200, Stefan Ehmann wrote: > Was bgscan on for iwi before the latest changes? A "ifconfig iwi0 scan" seems > to cause a "scan stuck" every time. But this also happened before the 802.11 > changes IIRC. So this might be an old iwi bug after all. (I still wouldn't > mind if it was resolved :)) I had endured this behaviour for months before the iwi(4) drivers began to complain it couldn't load its firmware. The message came along a connection freeze for a few seconds. Regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org >