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: Tue, 12 Feb 2013 11:24:39 +0100 [thread overview]
Message-ID: <511A1867.6060708@neratec.com> (raw)
In-Reply-To: <877gmdbzkc.fsf@purkki.adurom.net>
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.
next prev parent reply other threads:[~2013-02-12 10:30 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 [this message]
2013-02-12 10:46 ` Wojciech Dubowik
2013-02-13 12:45 ` Wojciech Dubowik
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=511A1867.6060708@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.