From owner-freebsd-current@FreeBSD.ORG Sat May 29 10:54:02 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 60AA0106564A; Sat, 29 May 2010 10:54:02 +0000 (UTC) (envelope-from bf1783@googlemail.com) Received: from mail-ww0-f54.google.com (mail-ww0-f54.google.com [74.125.82.54]) by mx1.freebsd.org (Postfix) with ESMTP id 736C58FC17; Sat, 29 May 2010 10:54:01 +0000 (UTC) Received: by wwb34 with SMTP id 34so798064wwb.13 for ; Sat, 29 May 2010 03:54:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:reply-to :in-reply-to:references:date:message-id:subject:from:to:cc :content-type; bh=w/mYc3i3nshkpcZ8QQ1inn2dVwmgTflXI7vT8pygDr4=; b=LEtS/R95QTPfZSyl+w8Ye8UnGgPxbxJBBeX9g45UQ7gJBMMstW6eiQnrsZfuiLVGGx lPAOIs025S/ZrlzkTxgBny3W0TDcQrMuF5HZTGc3fYc/KvGxAzxDe+FXRUnXtUUmLNqw bg8qJpGncCfjqcrZBCJRn37WRnEB4Mecn0Brg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; b=Jj7QjfyE8ev5G9nIpFuNM5Eq6hcLa0ZH5vAivsSe9NXcmqq2qMQM1dF8lUqwcOxOtz 6Aw5AlkwVJmCwIy05R7Bbl9mldSFpT3CPd75ndc2+igIxhFDmgcB8vaBJXWC6lB3ZH2J Sk6J0yzcCSRf+jPR5JCuvrf41kVSUsOMlKreM= MIME-Version: 1.0 Received: by 10.227.128.193 with SMTP id l1mr1424417wbs.197.1275130440347; Sat, 29 May 2010 03:54:00 -0700 (PDT) Received: by 10.216.158.146 with HTTP; Sat, 29 May 2010 03:54:00 -0700 (PDT) In-Reply-To: <958F0C5A-3CE8-41E2-9C6B-AC1C3C1863C7@FreeBSD.org> References: <4C00832A.4030102@FreeBSD.org> <958F0C5A-3CE8-41E2-9C6B-AC1C3C1863C7@FreeBSD.org> Date: Sat, 29 May 2010 06:54:00 -0400 Message-ID: From: "b. f." To: Rui Paulo Content-Type: text/plain; charset=ISO-8859-1 Cc: Doug Barton , zml@FreeBSD.org, freebsd-current@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 Reply-To: bf1783@gmail.com 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 10:54:02 -0000 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. b.