From: Wojciech Dubowik <Wojciech.Dubowik@neratec.com>
To: "Magnus Cederlöf" <mcider@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Possible bug with probe_send_count set to 0 and then checked if greater than 0
Date: Thu, 14 Feb 2013 13:09:11 +0100 [thread overview]
Message-ID: <511CD3E7.50900@neratec.com> (raw)
In-Reply-To: <CAND6uNnMB0i9fvVSmqHtCMkf4XVr8dHUz+m1m3CxDCT+j2XD5Q@mail.gmail.com>
On 02/14/2013 12:58 PM, Magnus Cederlöf wrote:
> In net/mac80211/mlme.c function ieee80211_sta_tx_notify:
> If a null frame was acked, ieee80211_sta_reset_conn_monitor is called.
> This function sets probe_send_count to 0.
> After the call to ieee80211_sta_reset_conn_monitor, it is checked if
> probe_set_count is > 0.
> This means that ieee80211_queue_work will not be called even though
> the nullfunc was successful.
>
> The symptom of this error is that when using power save, it will take
> 500ms to enter power save again after a successfully acked null frame.
I am looking at it now and I see that it happens without power save
as well. I have just started putting printk around so I am not so far.
Wojtek
> What case will the check for 'probe_send_count > 0' cover?
>
> Regards,
> Magnus Cederlöf
> --
> 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-14 12:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 11:58 Possible bug with probe_send_count set to 0 and then checked if greater than 0 Magnus Cederlöf
2013-02-14 12:09 ` 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=511CD3E7.50900@neratec.com \
--to=wojciech.dubowik@neratec.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcider@gmail.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).