From owner-freebsd-current@FreeBSD.ORG Sat May 29 17:53:05 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 37C491065676 for ; Sat, 29 May 2010 17:53:05 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id D1EC18FC0A for ; Sat, 29 May 2010 17:53:04 +0000 (UTC) Received: (qmail 21372 invoked by uid 399); 29 May 2010 17:53:03 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 29 May 2010 17:53:03 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4C01547E.2020303@FreeBSD.org> Date: Sat, 29 May 2010 10:53:02 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.9) Gecko/20100330 Thunderbird/3.0.4 MIME-Version: 1.0 To: bf1783@gmail.com References: <4C00832A.4030102@FreeBSD.org> <958F0C5A-3CE8-41E2-9C6B-AC1C3C1863C7@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.0.1 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Rui Paulo , "b. f." , zml@FreeBSD.org Subject: Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626)) 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: Sat, 29 May 2010 17:53:05 -0000 On 05/29/10 03:54, b. f. wrote: > On 5/29/10, Rui Paulo wrote: >> >> On 29 May 2010, at 05:39, b. f. wrote: >> >>> On 5/28/10, Doug Barton wrote: >>>> On 5/28/2010 4:50 PM, b. f. wrote: >>>>> >>>>> I can't see any problems when using WPA2 with AES on r208606 i386 with >>>>> uath(4). I'm updating this machine to r208630 tonight, and if I >>>>> encounter problems with the later revision, I'll let you know. >>>> >>>> Ok, thanks. >>>> >>>>> Are >>>>> you saying that you experienced problems when trying to use a r207134 >>>>> base with a r208626 kernel? If that's the case, I would recommend >>>>> updating the base to the same revision as the kernel, and then >>>>> retesting. >>>> >>>> Yes, that's what I'm doing I actually tried running the newly built >>>> wpa_supplicant but that didn't work. I'm kind of hesitant to do the full >>>> upgrade since I'm having kernel problems with the nvidia driver, but if >>>> I'm sure wpa_supplicant will work then I suppose I can bite the bullet. >>>> >>> >>> It appears that something is wrong. My wireless stick no longer >>> associates with the network with r208630. I'll do some tinkering. >> >> That's odd. The only way for that to happen would be caused bug in the >> taskqueue stuff that zml committed, I think, but that's a long shot. >> >> Regards, >> -- >> Rui Paulo > > Yes, that was also my suspicion, and after seeing, via top(1), that > ifconfig is stuck in the "*taskq" state while attempting to set up > the wlan, I believe either r208623, or r208624, or both, is > responsible for the regression. Reverting those two changes allows wpa_supplicant to work again. Thanks for the hint bf. Zach? Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/