From: Wojciech Dubowik <Wojciech.Dubowik@neratec.com>
To: Kalle Valo <kvalo@adurom.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Subject: Re: [BUG] Beacon loss event every second
Date: Wed, 13 Feb 2013 13:45:02 +0100 [thread overview]
Message-ID: <511B8ACE.4040408@neratec.com> (raw)
In-Reply-To: <511A1D88.6080406@neratec.com>
On 02/12/2013 11:46 AM, Wojciech Dubowik wrote:
> On 02/12/2013 11:24 AM, Wojciech Dubowik wrote:
>> On 02/12/2013 11:23 AM, Kalle Valo wrote:
>>> Wojciech Dubowik <Wojciech.Dubowik@neratec.com> writes:
>>>
>>>> I have a test pc with 3x AR9590 and 2x AR9390. Machine is based on i7
>>>> and hyperthreading is on so I have 8 cores.
>>>> I am using latest wireless testing ath9k and 3.8rc7 kernel.
>>>>
>>>> What I see is that for some extended periods odf time beacons are not
>>>> processed in ieee80211_rx_mgmt_beacon
>>>> and that's why I get beacon loss. I am using 30ms beacon period.
>>>>
>>>>
>>>> What is really funny, that I get this beacon loss message every
>>>> second. Like is sth was locking ifmgd->mtx mutex
>>>> at constant intervals.
>>>>
>>>>
>>>> I will try to disable all cores and run in again to see if it's rcu
>>>> problem.
>>> You could also try wireless-next or wireless-testing to pinpoint if the
>>> problem is in wireless code or not.
>>>
>> I see it on wireless-testing and mac80211-next. I will try with other
>> driver later today.
>>
>> I can see also other problem like authentication frame always timing
>> out the first time
>> but I will handle it later.
> It has turned out that I had bad irq, switch to polling problem.
> Without interrupts for wireless
> cards I will for sure see such problems.
After solving the bad irq problems I can still see the issue.
It has turned out that when I set beacon interval to less than 40ms I
get beacon loss events.
My setup is ath9k AP and ath9k STA on the same pc connected with rf
cable and 40dB attenuator.
I have seen this problem also with earlier versions of wireless testing
and next.
Wojtek
>
> Sorry for spamming.
>
> Wojtek
>> --
>> To unsubscribe from this list: send the line "unsubscribe
>> linux-wireless" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> --
> To unsubscribe from this list: send the line "unsubscribe
> linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-02-13 12:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 13:47 [BUG] Beacon loss event every second Wojciech Dubowik
2013-02-11 14:27 ` Johannes Berg
2013-02-11 14:42 ` Wojciech Dubowik
2013-02-12 10:04 ` Kalle Valo
2013-02-12 10:13 ` Wojciech Dubowik
2013-02-12 10:23 ` Kalle Valo
2013-02-12 10:24 ` Wojciech Dubowik
2013-02-12 10:46 ` Wojciech Dubowik
2013-02-13 12:45 ` Wojciech Dubowik [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=511B8ACE.4040408@neratec.com \
--to=wojciech.dubowik@neratec.com \
--cc=johannes@sipsolutions.net \
--cc=kvalo@adurom.com \
--cc=linux-wireless@vger.kernel.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).