From owner-freebsd-bugs@FreeBSD.ORG Sat Jan 12 07:40:00 2013 Return-Path: Delivered-To: freebsd-bugs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A4A90BB0 for ; Sat, 12 Jan 2013 07:40:00 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 737A0965 for ; Sat, 12 Jan 2013 07:40:00 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r0C7e0Vu097324 for ; Sat, 12 Jan 2013 07:40:00 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r0C7e0fg097323; Sat, 12 Jan 2013 07:40:00 GMT (envelope-from gnats) Resent-Date: Sat, 12 Jan 2013 07:40:00 GMT Resent-Message-Id: <201301120740.r0C7e0fg097323@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Adrian Chadd Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 736D6AFC for ; Sat, 12 Jan 2013 07:38:08 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id 4E6C194C for ; Sat, 12 Jan 2013 07:38:08 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.5/8.14.5) with ESMTP id r0C7c8kh088285 for ; Sat, 12 Jan 2013 07:38:08 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.5/8.14.5/Submit) id r0C7c8jl088284; Sat, 12 Jan 2013 07:38:08 GMT (envelope-from nobody) Message-Id: <201301120738.r0C7c8jl088284@red.freebsd.org> Date: Sat, 12 Jan 2013 07:38:08 GMT From: Adrian Chadd To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Subject: misc/175227: [ath] beacon timers aren't necessarily reprogrammed after a chip reset X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jan 2013 07:40:00 -0000 >Number: 175227 >Category: misc >Synopsis: [ath] beacon timers aren't necessarily reprogrammed after a chip reset >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Jan 12 07:40:00 UTC 2013 >Closed-Date: >Last-Modified: >Originator: Adrian Chadd >Release: -HEAD >Organization: >Environment: >Description: When the chip is reset, the beacon programming in STA Mode needs to be re-done, else none of the registers will be programmed and thus no beacon miss events are generated. This has shown up when I add a hardware reset to ath_bmiss_proc(). After that ath_reset() call is finished, the beacon timers aren't re-programmed. So, I need to review the beacon miss handling and ath_reset() path; check whether the beacon timers are being reprogrammed or not. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: