All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wojciech Dubowik <Wojciech.Dubowik@neratec.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: start auth/assoc timeout on frame status
Date: Wed, 13 Feb 2013 15:23:33 +0100	[thread overview]
Message-ID: <511BA1E5.40402@neratec.com> (raw)
In-Reply-To: <1360765274.8868.13.camel@jlt4.sipsolutions.net>

On 02/13/2013 03:21 PM, Johannes Berg wrote:
> On Wed, 2013-02-13 at 14:41 +0100, Wojciech Dubowik wrote:
>> There is a regression introduced with this patch.
>> On my ath9k AP + ath9k STA I get timeout for
>> management frames even when they are acked.
>>
>> Attached syslog and iw event before and after
>> this patch.
>>
>> I have seen it before in my testing and it gets
>> a lot worse with system load.  Sometimes it can
>> retry auth/assoc frames for 10 seconds before
>> connecting.
>> Anyway it always looses the first authentication frame.
> I think I see what's happening -- can you try this patch?
>
> http://p.sipsolutions.net/61f4271fed0e446b.txt
>
I have tried and it doesn't do timeout anymore. I will continue
testing with more load.

Thanks,
Wojtek

  reply	other threads:[~2013-02-13 14:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-31 13:28 [PATCH] mac80211: start auth/assoc timeout on frame status Johannes Berg
2013-02-04 15:43 ` Johannes Berg
2013-02-13 13:41   ` Wojciech Dubowik
2013-02-13 14:21     ` Johannes Berg
2013-02-13 14:23       ` Wojciech Dubowik [this message]
2013-02-13 14:32         ` Johannes Berg
2013-02-13 14:39           ` Johannes Berg
2013-02-13 15:20             ` Wojciech Dubowik
2013-02-13 15:36               ` Sujith Manoharan
2013-02-13 15:41                 ` Wojciech Dubowik
2013-02-13 16:13                   ` Johannes Berg

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=511BA1E5.40402@neratec.com \
    --to=wojciech.dubowik@neratec.com \
    --cc=johannes@sipsolutions.net \
    --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.