From owner-freebsd-net@FreeBSD.ORG Fri Jul 30 01:20:05 2010 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 290B2106566C for ; Fri, 30 Jul 2010 01:20:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 14AEE8FC0A for ; Fri, 30 Jul 2010 01:20:05 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o6U1K4pg053113 for ; Fri, 30 Jul 2010 01:20:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o6U1K4sX053112; Fri, 30 Jul 2010 01:20:04 GMT (envelope-from gnats) Date: Fri, 30 Jul 2010 01:20:04 GMT Message-Id: <201007300120.o6U1K4sX053112@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Troye Johnson Cc: Subject: Re: kern/148112: [ath] Atheros 9285 cannot register with wifi AP (timeout) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Troye Johnson List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jul 2010 01:20:05 -0000 The following reply was made to PR kern/148112; it has been noted by GNATS. From: Troye Johnson To: bug-followup@FreeBSD.org, izaera@gmail.com Cc: Subject: Re: kern/148112: [ath] Atheros 9285 cannot register with wifi AP (timeout) Date: Thu, 29 Jul 2010 21:18:48 -0400 --000e0cd6aca20b7b9c048c90a29c Content-Type: text/plain; charset=ISO-8859-1 Well as from what I can tell the wifi card does associate, but shortly there after the device hangis and the kernel resets it. So when the device hangs, I cannot do "dhclient wlan0" to get the IP as the device as been reset (and simultaneously disassociated from AP). Maintainer has been paged/contacted in addition to this PR. --- Proud N00b --000e0cd6aca20b7b9c048c90a29c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Well as from what I can tell the wifi card does=A0 associate, but shortly t= here after the device hangis and the kernel resets it. So when the device h= angs, I cannot do "dhclient wlan0" to get the IP as the device as= been reset (and simultaneously disassociated from AP). Maintainer has been= paged/contacted in addition to this PR.

---
Proud N00b
--000e0cd6aca20b7b9c048c90a29c--