From owner-freebsd-amd64@freebsd.org  Tue Mar  1 23:20:59 2016
Return-Path: <owner-freebsd-amd64@freebsd.org>
Delivered-To: freebsd-amd64@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 46CC7AC0528
 for <freebsd-amd64@mailman.ysv.freebsd.org>;
 Tue,  1 Mar 2016 23:20:59 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (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 383AD1A54
 for <freebsd-amd64@FreeBSD.org>; Tue,  1 Mar 2016 23:20:59 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u21NKwYX026157
 for <freebsd-amd64@FreeBSD.org>; Tue, 1 Mar 2016 23:20:59 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-amd64@FreeBSD.org
Subject: [Bug 207445] net80211 Atheros AR938x: non-working WiFi hostap since
 ~ January
Date: Tue, 01 Mar 2016 23:20:58 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: wireless
X-Bugzilla-Version: 11.0-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: avos@freebsd.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-207445-6-Dmj81GyYjN@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-207445-6@https.bugs.freebsd.org/bugzilla/>
References: <bug-207445-6@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 01 Mar 2016 23:34:26 +0000
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64/>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2016 23:20:59 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207445

--- Comment #9 from Andriy Voskoboinyk <avos@freebsd.org> ---
> as far as I can describe is that the client still receives its IP via DHCP
so, traffic can flow? because
> station associated at aid 1: short preamble, short slot time, QoS
means that association was successful. Is there any problems with other
clients?

P.S. Looks like inactivity processing (with timeout in 205 seconds and this
weird reason code (1 =3D unspecified)).

--=20
You are receiving this mail because:
You are on the CC list for the bug.=