From owner-freebsd-current@FreeBSD.ORG Thu Aug 5 19:18:34 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 464871065672 for ; Thu, 5 Aug 2010 19:18:34 +0000 (UTC) (envelope-from uqs@spoerlein.net) Received: from acme.spoerlein.net (acme.spoerlein.net [IPv6:2001:470:9a47::1]) by mx1.freebsd.org (Postfix) with ESMTP id B6FA68FC17 for ; Thu, 5 Aug 2010 19:18:33 +0000 (UTC) Received: from acme.spoerlein.net (localhost.spoerlein.net [IPv6:::1]) by acme.spoerlein.net (8.14.4/8.14.4) with ESMTP id o75JIBu4093774 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 5 Aug 2010 21:18:11 +0200 (CEST) (envelope-from uqs@spoerlein.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=spoerlein.net; s=dkim200908; t=1281035891; bh=ZhAZEqCxBhE0/mggCv1+zTiF1puqhNfdkRnqq5NLQg4=; h=Date:From:To:Subject:Message-ID:References:MIME-Version: Content-Type:In-Reply-To; b=BJhQO7+mS/VHR3d3m2yLGbnockMoWgfcntoe2PMTBlRba34juQ/FRhURnMCeWQaW8 ayl/n9SGNQWUL4f+iDF80Rd6Nlmw5zPCBZdWOvAYcKz8akZuxYAMUxRwDcE7AN6joK tMNsQfMjMzO36t1hflBru7wGvCdbR/lUA3GbjzTE= Received: (from uqs@localhost) by acme.spoerlein.net (8.14.4/8.14.4/Submit) id o75JIB1r093773; Thu, 5 Aug 2010 21:18:11 +0200 (CEST) (envelope-from uqs@spoerlein.net) Date: Thu, 5 Aug 2010 21:18:11 +0200 From: Ulrich =?utf-8?B?U3DDtnJsZWlu?= To: David Wolfskill , current@freebsd.org Message-ID: <20100805191811.GF80306@acme.spoerlein.net> Mail-Followup-To: David Wolfskill , current@freebsd.org References: <20100805140550.GT12818@albert.catwhisker.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100805140550.GT12818@albert.catwhisker.org> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Subject: Re: Panic @r210841 in iwi_auth_and_assoc(): iwi firmware not idle, state ASSOCIATING 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: Thu, 05 Aug 2010 19:18:34 -0000 On Thu, 05.08.2010 at 07:05:50 -0700, David Wolfskill wrote: > Before I get to the "good stuff", I'll note that: > > * I'm no longer running a VIMAGE kernel, so that possible source of > confusion should be absent. > > * The hardware in question (a miniPCI device in my laptop) has been > working under stable/7 and stable/8 (so I believe that there should be > nothing so wrong with the hardware that it should cause a panic). > > * I tend to see a lot of messages: "iwi0: firmware error" -- especially > running CURRENT. I have seen a few of them while running stable/7, as > well (but no panics under stable/*). > > * An ath(4) PCcard works fine (now that I'm not running VIMAGE). Ever since I upgrade to 9-CURRENT (might have happened before) I have trouble with iwi(4) from time to time. The firmware error is pretty common but I can usually recover using "kldunload if_iwi; sleep 10; kldload if_iwi". However, sometimes a real panic occurs and iwi(4) seems to play a role. Note that I'm using wpa_supplicant and iwi0/wlan0 is aggregated into lagg0 (but same problems also exist without if_lagg in the mix). I cannot get to the laptop's /var/crash right now (due to a freak spilling accident) but hope to be able to provide crashdumps in a fortnight (if there's someone interested in further iwi(4) development ...) Cheers, Uli