From: Mohammed Shafi <shafi.wireless@gmail.com>
To: Ben Greear <greearb@candelatech.com>
Cc: Michael Leun <lkml20120218@newton.leun.net>,
casteyde.christian@free.fr,
Kelly Anderson <kelly@silka.with-linux.com>,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@venema.h4ckr.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Felix Fietkau <nbd@openwrt.org>,
linux-wireless Mailing List <linux-wireless@vger.kernel.org>
Subject: Re: [ath9k-devel] 3.3.1 ath9k regression
Date: Fri, 6 Apr 2012 10:41:53 +0530 [thread overview]
Message-ID: <CAD2nsn16AozFF2QhiY063-48bKiXdyQLmSqJLLHPpsZ3H3JtHQ@mail.gmail.com> (raw)
In-Reply-To: <4F7DE3A4.1040705@candelatech.com>
Hi Ben,
On Thu, Apr 5, 2012 at 11:55 PM, Ben Greear <greearb@candelatech.com> wrote:
> I see the regression on my WPEA-127N systems as well.
>
> With the patch applied to 3.3.1, I see never ending stream of
> auth timeouts (this log is watching 'iw event' output)
>
> power-management is OFF on my system, and using nohwcrypt,
> in case that matters.
>
> This is with 10 virtual stations.
>
> 2012-04-05 11:16:14.155 1.1: sta5 (phy #0): scan finished: 2412 2417 2422
> 2427 2432 2437 2442 2447 2452 2457 2462 2467 2472 5180 5200 5220 5240 5260
> 5280 5300 5320 5500 5520 5540 5560 5580 5600 5620 5640 5660 5680 5700 5745
> 5765 5785 5805 5825, ""
> 2012-04-05 11:16:15.266 1.1: sta0 (phy #0): auth: timed out
> 2012-04-05 11:16:15.266 1.1: sta1 (phy #0): auth: timed out
> 2012-04-05 11:16:15.266 1.1: sta2 (phy #0): auth: timed out
> 2012-04-05 11:16:15.266 1.1: sta3 (phy #0): auth: timed out
> 2012-04-05 11:16:15.266 1.1: sta4 (phy #0): auth: timed out
> 2012-04-05 11:16:15.266 1.1: sta6 (phy #0): auth: timed out
> 2012-04-05 11:16:15.266 1.1: sta7 (phy #0): auth: timed out
> 2012-04-05 11:16:15.266 1.1: sta8 (phy #0): auth: timed out
> 2012-04-05 11:16:15.266 1.1: sta9 (phy #0): auth: timed out
> 2012-04-05 11:16:15.266 1.1: sta5 (phy #0): auth: timed out
> 2012-04-05 11:16:19.400 1.1: sta0 (phy #0): scan started
> 2012-04-05 11:16:23.302 1.1: sta0 (phy #0): scan finished: 2412 2417 2422
> 2427 2432 2437 2442 2447 2452 2457 2462 2467 2472 5180 5200 5220 5240 5260
> 5280 5300 5320 5500 5520 5540 5560 5580 5600 5620 5640 5660 5680 5700 5745
> 5765 5785 5805 5825, ""
> 2012-04-05 11:16:24.406 1.1: sta1 (phy #0): auth: timed out
> 2012-04-05 11:16:24.406 1.1: sta2 (phy #0): auth: timed out
> 2012-04-05 11:16:24.406 1.1: sta3 (phy #0): auth: timed out
> 2012-04-05 11:16:24.406 1.1: sta4 (phy #0): auth: timed out
> 2012-04-05 11:16:24.406 1.1: sta5 (phy #0): auth: timed out
> 2012-04-05 11:16:24.406 1.1: sta6 (phy #0): auth: timed out
> 2012-04-05 11:16:24.406 1.1: sta7 (phy #0): auth: timed out
> 2012-04-05 11:16:24.406 1.1: sta8 (phy #0): auth: timed out
> 2012-04-05 11:16:24.406 1.1: sta9 (phy #0): auth: timed out
> 2012-04-05 11:16:24.406 1.1: sta0 (phy #0): auth: timed out
>
> I reverted the patch and then it associates immediately.
>
> Occasionally, I would see things associate and run OK with the patch
> in place, but it always took a lot of re-tries to associate
> even when it did work.
i think its best for me try to download the 3.3.1 stable kernel and
see if this issue happens,
i am going to start it now, Ben does this happens with latest
wireless testing tree?
its quite weird 3.4-rc1 works as some user reported and while 3.3.1 does not.
i will try to come with some suggestion patches
>
> I can easily test patches or try things if anyone has any ideas.
>
> Thanks,
> Ben
>
>
> --
> Ben Greear <greearb@candelatech.com>
> Candela Technologies Inc http://www.candelatech.com
>
--
thanks,
shafi
next prev parent reply other threads:[~2012-04-06 5:11 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 5:46 3.3.1 ath9k regression Kelly Anderson
2012-04-03 6:01 ` Ben Greear
2012-04-03 6:26 ` [ath9k-devel] " Mohammed Shafi
2012-04-03 6:49 ` Kelly Anderson
2012-04-03 7:16 ` Mohammed Shafi
2012-04-03 7:46 ` Kelly Anderson
2012-04-03 7:52 ` Mohammed Shafi
2012-04-03 8:04 ` Mohammed Shafi
2012-04-03 8:38 ` Kelly Anderson
2012-04-03 18:03 ` Michael Leun
2012-04-04 7:29 ` Mohammed Shafi
2012-04-04 15:03 ` Mohammed Shafi
2012-04-04 21:51 ` Michael Leun
2012-04-05 6:16 ` Mohammed Shafi
2012-04-05 13:53 ` Michael Leun
2012-04-05 18:25 ` Ben Greear
2012-04-06 5:11 ` Mohammed Shafi [this message]
2012-04-06 20:31 ` Ben Greear
2012-04-08 23:08 ` 3.4-rc ath9k regression (Re: [ath9k-devel] 3.3.1 ath9k regression) Michael Leun
2012-04-09 6:28 ` Mohammed Shafi
2012-04-09 8:45 ` Sergio Correia
2012-04-09 10:25 ` Michael Leun
2012-04-09 14:03 ` Michael Leun
2012-04-09 14:22 ` Mohammed Shafi
2012-04-09 15:29 ` Michael Leun
2012-04-10 5:48 ` Mohammed Shafi
2012-04-10 10:05 ` [ath9k-devel] 3.4-rc ath9k regression (Re: " Mohammed Shafi
2012-04-12 13:46 ` 3.4-rc ath9k regression (Re: [ath9k-devel] " Felix Fietkau
2012-04-12 13:58 ` Felipe Contreras
2012-04-12 15:35 ` Michael Leun
2012-04-12 18:11 ` Felix Fietkau
2012-04-12 19:28 ` Sergio Correia
2012-04-14 21:15 ` Felipe Contreras
2012-04-12 22:01 ` Michael Leun
2012-04-09 19:12 ` [ath9k-devel] 3.4-rc ath9k regression (Re: " Sujith Manoharan
2012-04-09 21:21 ` Michael Leun
2012-04-09 6:52 ` [ath9k-devel] 3.3.1 ath9k regression Mohammed Shafi
2012-04-04 10:40 ` Mantas M.
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=CAD2nsn16AozFF2QhiY063-48bKiXdyQLmSqJLLHPpsZ3H3JtHQ@mail.gmail.com \
--to=shafi.wireless@gmail.com \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=casteyde.christian@free.fr \
--cc=greearb@candelatech.com \
--cc=kelly@silka.with-linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lkml20120218@newton.leun.net \
--cc=nbd@openwrt.org \
/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).