Date: Sat, 29 May 2010 06:54:00 -0400 From: "b. f." <bf1783@googlemail.com> To: Rui Paulo <rpaulo@freebsd.org> Cc: Doug Barton <dougb@freebsd.org>, zml@FreeBSD.org, freebsd-current@freebsd.org Subject: Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626)) Message-ID: <AANLkTikFQFNFGmSOlSAleLKPX7ZlK7ZkdcjhKNA8k2H2@mail.gmail.com> In-Reply-To: <958F0C5A-3CE8-41E2-9C6B-AC1C3C1863C7@FreeBSD.org> References: <AANLkTilCmEAdZXpO_hhQXOkY576POiNqf71fZ4nmu7hO@mail.gmail.com> <4C00832A.4030102@FreeBSD.org> <AANLkTikk34mBzYG_YRyjl9IJXdksdPQCa6JRaYvp-TZ6@mail.gmail.com> <958F0C5A-3CE8-41E2-9C6B-AC1C3C1863C7@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5/29/10, Rui Paulo <rpaulo@freebsd.org> wrote: > > On 29 May 2010, at 05:39, b. f. wrote: > >> On 5/28/10, Doug Barton <dougb@freebsd.org> 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. b.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTikFQFNFGmSOlSAleLKPX7ZlK7ZkdcjhKNA8k2H2>