From owner-freebsd-current@FreeBSD.ORG Mon Nov 16 00:43:01 2009 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 1CF7510656B9 for ; Mon, 16 Nov 2009 00:43:01 +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 9D89A8FC22 for ; Mon, 16 Nov 2009 00:43:00 +0000 (UTC) Received: (qmail 20804 invoked by uid 399); 16 Nov 2009 00:43:00 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 16 Nov 2009 00:43:00 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4B00A01D.9040704@FreeBSD.org> Date: Sun, 15 Nov 2009 16:43:09 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Thunderbird 2.0.0.23 (X11/20090822) MIME-Version: 1.0 To: Rui Paulo References: <4B0087C2.9070508@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 0.96.0 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Antoine Brodin , freebsd-current@freebsd.org Subject: Re: wpa_supplicant + wpi0 won't lock in on today's -current 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, 16 Nov 2009 00:43:01 -0000 Rui Paulo wrote: > Hi, > > On 15 Nov 2009, at 22:59, Doug Barton wrote: > >> I upgraded my -current laptop from r199019 to r199291 and on the newer >> kernel wpa_supplicant runs but doesn't ever lock in. >> >> The only suspect commits in that range are r19918[67] which seem to be >> minor fixes to sys/net80211. I haven't yet had a chance to test that >> theory; I thought I'd post sooner than later to see if anyone has a >> bright idea first. :) > > The commits you mention couldn't have caused any kind of the malfunction that you describe. Yes, I didn't think it likely, but as I noted those were the only commits that (to my untrained eye) looked like they could be relevant. I'm currently in the process of doing a binary search, r199185 exhibits the problem, so the bug came before that. I'll update again when I'm done. Doug -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/