From owner-freebsd-stable@freebsd.org Sun Dec 6 14:31:33 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 94C6D99A78F; Sun, 6 Dec 2015 14:31:33 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5E93419E1; Sun, 6 Dec 2015 14:31:33 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (unknown [62.141.129.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 18F5D1FE023; Sun, 6 Dec 2015 15:31:29 +0100 (CET) Subject: Re: urtwn regression(?) from 10.2 to current r291431 To: mexas@bris.ac.uk, freebsd-current@freebsd.org, freebsd-stable@freebsd.org, Adrian Chadd References: <201512061414.tB6EEpTY041098@mech-as222.men.bris.ac.uk> From: Hans Petter Selasky Message-ID: <5664472E.3090601@selasky.org> Date: Sun, 6 Dec 2015 15:33:18 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <201512061414.tB6EEpTY041098@mech-as222.men.bris.ac.uk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Dec 2015 14:31:33 -0000 On 12/06/15 15:14, Anton Shterenlikht wrote: > I posted this about a week ago: > > http://lists.freebsd.org/pipermail/freebsd-current/2015-November/058683.html > > The problem is that urtwn stopped > working in current r291431. > > I did more testing with the same revision, > and sometimes it would work, but extremely > slowly, and sometimes seemingly associate > but get an address of 0.0.0.0. > > I now installed 10.2-RELEASE-p8 and > the urtwn works fine, no issues at all. > > Does this look like a bug at some recent > current revision? Should I file a PR? > > I's just I recall there have been major > chages to wlan, so perphaps I'm forgetting > to change the config in recent current? > > Please advise > > Anton Hi, There is work ongoing in the WLAN drivers. Did you try the latest -current? --HPS