From owner-freebsd-current@FreeBSD.ORG Mon Jun 18 22:27:40 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 88EB916A46D for ; Mon, 18 Jun 2007 22:27:40 +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 4DCFD13C4BA for ; Mon, 18 Jun 2007 22:27:39 +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 539C744678; Tue, 19 Jun 2007 00:27:39 +0200 (CEST) Received: from obiwan.tataz.chchile.org (unknown [192.168.1.25]) by tatooine.tataz.chchile.org (Postfix) with ESMTP id 22CF49C333; Mon, 18 Jun 2007 22:27:20 +0000 (UTC) Received: by obiwan.tataz.chchile.org (Postfix, from userid 1000) id 2906D4086; Mon, 18 Jun 2007 19:56:55 +0200 (CEST) Date: Mon, 18 Jun 2007 19:56:55 +0200 From: Jeremie Le Hen To: Andrew Thompson Message-ID: <20070618175655.GD88370@obiwan.tataz.chchile.org> References: <20070616224703.GC63387@obiwan.tataz.chchile.org> <20070618100238.GD46910@heff.fud.org.nz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070618100238.GD46910@heff.fud.org.nz> User-Agent: Mutt/1.5.15 (2007-04-06) Cc: freebsd-current@FreeBSD.org, Jeremie Le Hen Subject: Re: Cannot use iwi(4): "could not load firmware iwi_bss" 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: Mon, 18 Jun 2007 22:27:40 -0000 Hi Andrew, Thank you for replying. I'm a bit disconcerted by this problem since nobody seems to meet it but me. On Mon, Jun 18, 2007 at 10:02:38PM +1200, Andrew Thompson wrote: > The driver will wait one second for the firmware to load, it is possible > that the interrupt storm is affecting this. You can always increase the > iwi timeout on line 2516 of if_iwi.c and see what happens. Change hz to > hz * 3 perhaps. I've tried this change without success. Interestingly, it seems that the interrupt storm happens while if_iwi module is trying to load the firmware and stops as soon as if_iwi gives up. If you have any other idea, please let me knom. I am willing to test whatever you might deem useful. Best regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org >