linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@openwrt.org>
To: Jurica Vukadin <u.ra604@googlemail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"John W. Linville" <linville@tuxdriver.com>,
	linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: regression, 3.2.2 stable: ath9k won't associate anymore
Date: Sun, 05 Feb 2012 20:53:07 +0100	[thread overview]
Message-ID: <4F2EDE23.5070505@openwrt.org> (raw)
In-Reply-To: <CANtv1eXSbOSp90BEfuWdL+6_7CFPJ5Hpn=Va3Jopbr7s011JLg@mail.gmail.com>

On 2012-02-05 8:45 PM, Jurica Vukadin wrote:
> Hi,
> 
> commit "b4a82a0 ath9k_hw: fix interpretation of the rx KeyMiss flag"
> caused my card to stop associating with the router.
> Reverting it fixes the issue. Encryption is WEP, if that matters; I
> haven't tried others.
> 
> The device is "10:00.0 Network controller: Atheros Communications Inc.
> AR9287 Wireless Network Adapter (PCI-Express) (rev 01)"
> 
> excerpt from dmesg before the revert:
> Feb  5 20:00:56 smaug kernel: [    7.468770] ath9k 0000:10:00.0: PCI
> INT A -> GSI 17 (level, low) -> IRQ 17
> Feb  5 20:00:56 smaug kernel: [    7.468787] ath9k 0000:10:00.0:
> setting latency timer to 64
> Feb  5 20:00:56 smaug kernel: [    7.558116] ath: EEPROM regdomain: 0x6a
> Feb  5 20:00:56 smaug kernel: [    7.558118] ath: EEPROM indicates we
> should expect a direct regpair map
> Feb  5 20:00:56 smaug kernel: [    7.558121] ath: Country alpha2 being used: 00
> Feb  5 20:00:56 smaug kernel: [    7.558122] ath: Regpair used: 0x6a
> Feb  5 20:00:56 smaug kernel: [    8.044750] ieee80211 phy0: Selected
> rate control algorithm 'ath9k_rate_control'
> Feb  5 20:00:56 smaug kernel: [    8.045371] Registered led device: ath9k-phy0
> Feb  5 20:01:01 smaug kernel: [   16.161078] wlan0: authenticate with
> 00:01:e3:4a:9e:be (try 1)
> Feb  5 20:01:01 smaug kernel: [   16.163159] wlan0: authenticated
> Feb  5 20:01:01 smaug kernel: [   16.197844] wlan0: associate with
> 00:01:e3:4a:9e:be (try 1)
> Feb  5 20:01:01 smaug kernel: [   16.200307] wlan0: RX AssocResp from
> 00:01:e3:4a:9e:be (capab=0x431 status=0 aid=4)
> Feb  5 20:01:01 smaug kernel: [   16.200312] wlan0: associated
> Feb  5 20:01:31 smaug kernel: [   46.185930] wlan0: deauthenticating
> from 00:01:e3:4a:9e:be by local choice (reason=3)
The issue is WEP specific, a fix has been found and confirmed. I'll
submit it for inclusion soon.

- Felix

      reply	other threads:[~2012-02-05 19:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-05 19:45 regression, 3.2.2 stable: ath9k won't associate anymore Jurica Vukadin
2012-02-05 19:53 ` Felix Fietkau [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F2EDE23.5070505@openwrt.org \
    --to=nbd@openwrt.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=u.ra604@googlemail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).