Date: Sat, 12 Jan 2013 07:38:08 GMT From: Adrian Chadd <adrian@FreeBSD.org> To: freebsd-gnats-submit@FreeBSD.org Subject: misc/175227: [ath] beacon timers aren't necessarily reprogrammed after a chip reset Message-ID: <201301120738.r0C7c8jl088284@red.freebsd.org> Resent-Message-ID: <201301120740.r0C7e0fg097323@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>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:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201301120738.r0C7c8jl088284>