linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: Timothy Rundle <tgrundlesr@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: RTL8192CU continually reconnecting
Date: Mon, 09 Sep 2013 12:04:03 -0500	[thread overview]
Message-ID: <522DFF83.6000605@lwfinger.net> (raw)
In-Reply-To: <522DE8CA.9010008@ilande.co.uk>

[-- Attachment #1: Type: text/plain, Size: 2038 bytes --]

On 09/09/2013 10:27 AM, Mark Cave-Ayland wrote:
> On 09/09/13 15:57, Larry Finger wrote:
>
>> I think your user space is exactly the problem. As I am writing this, my
>> device, which lsusb reports as "ID 7392:7811 Edimax Technology Co., Ltd
>> EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS]" has been up for
>> a little over 20 hours. During that time, there have been 23
>> deauthentications for reason 7, but 0 of the "connection to AP lost"
>> variety.
>
> I've just tried building wpa_supplicant 2.0 from source and it sadly doesn't
> make any difference here.
>
> I do still however see the following in dmesg output:
>
> rtlwifi:rtl_watchdog_wq_callback():<0-0> AP off, try to reconnect now
>
> Briefly looking through the code in rtlwifi/base.c I see that the watchdog
> message above is triggered by the condition (rtlpriv->link_info.bcn_rx_inperiod
> + rtlpriv->link_info.num_rx_inperiod) == 0).
>
> The bcn_rx_inperiod value is only incremented by rtl_beacon_statistic() in
> base.c, which is in turn called from _rtl_usb_rx_process_noagg() (but not
> _rtl_usb_rx_process_agg() for some reason?). Shall I try adding some debugging
> printk() statements in there to get a feel for what is going on? Or would it be
> better to attempt a trace with debug=0x5?

Debug level 5 will inundate you with so much info that you will not get much 
feeling for the results. Even the Realtek engineers never ask for level 5. Try 
the attached patch. That will let us know if rtl_beacon_statistic() is being 
called, and what parameters it is getting.

I have added the call to rtl_beacon_statistic() to _rtl_usb_rx_process_agg(), 
which should be the routine used in my connection to an AP using WPA2, which 
allows aggregation. As I write this, the revised driver has been running for 
only 1800 seconds, but I have not seen any of the "AP off" messages.

>> I will switch my system from NM to manual control to see what happens.
>
> Interesting. Did it make any difference in the end?

In 3 hours, it made no difference.

Larry



[-- Attachment #2: rtl8192cu_dump_AP_off --]
[-- Type: text/plain, Size: 1235 bytes --]

Index: wireless-testing-save/drivers/net/wireless/rtlwifi/base.c
===================================================================
--- wireless-testing-save.orig/drivers/net/wireless/rtlwifi/base.c
+++ wireless-testing-save/drivers/net/wireless/rtlwifi/base.c
@@ -1287,7 +1287,13 @@ void rtl_beacon_statistic(struct ieee802
 {
 	struct rtl_priv *rtlpriv = rtl_priv(hw);
 	struct ieee80211_hdr *hdr = (struct ieee80211_hdr *)skb->data;
+	static int count;
 
+	if (count++ < 100) {
+		pr_info("mode %d, state %d, is_beacon %d, is_probe_resp %d, length %d, MAC %pM\n",
+			rtlpriv->mac80211.opmode, rtlpriv->mac80211.link_state, ieee80211_is_beacon(hdr->frame_control),
+			ieee80211_is_probe_resp(hdr->frame_control), skb->len, hdr->addr3);
+	}
 	if (rtlpriv->mac80211.opmode != NL80211_IFTYPE_STATION)
 		return;
 
diff --git a/drivers/net/wireless/rtlwifi/usb.c b/drivers/net/wireless/rtlwifi/usb.c
index e56778c..ba9844a 100644
--- a/drivers/net/wireless/rtlwifi/usb.c
+++ b/drivers/net/wireless/rtlwifi/usb.c
@@ -484,6 +484,8 @@ static void _rtl_usb_rx_process_agg(struct ieee80211_hw *hw,
 			if (unicast)
 				rtlpriv->link_info.num_rx_inperiod++;
 		}
+		/* static bcn for roaming */
+		rtl_beacon_statistic(hw, skb);
 	}
 }
 


  reply	other threads:[~2013-09-09 17:04 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-08 11:53 RTL8192CU continually reconnecting Timothy Rundle
2013-09-08 23:16 ` Larry Finger
2013-09-09 14:16   ` Mark Cave-Ayland
2013-09-09 14:57     ` Larry Finger
2013-09-09 15:08       ` Oleksij Rempel
2013-09-09 15:27       ` Mark Cave-Ayland
2013-09-09 17:04         ` Larry Finger [this message]
     [not found]           ` <522E0573.4000804@ilande.co.uk>
2013-09-09 19:03             ` Larry Finger
2013-09-09 22:05               ` Mark Cave-Ayland
2013-09-09 23:04                 ` Larry Finger
2013-09-09 23:45                   ` Mark Cave-Ayland
2013-09-10  2:52                     ` Larry Finger
2013-09-10  5:58                       ` Mark Cave-Ayland
2013-09-10 15:14                         ` Larry Finger
2013-09-10 20:04                           ` Mark Cave-Ayland
2013-09-11 20:09                             ` Larry Finger
2013-09-12 23:02                               ` Timothy Rundle
2013-09-13  9:01                               ` Mark Cave-Ayland
     [not found]                               ` <CALa3VXbxQ1Z2J5weV7rQ16c53D1MQyDL1YGQrV6EkCJYfh=uYA@mail.gmail.com>
2013-09-13 17:52                                 ` Larry Finger
2013-09-19  0:42                                   ` Timothy Rundle
2013-09-19  6:48                                     ` Mark Cave-Ayland
2013-09-19 10:45                                       ` Timothy Rundle
2013-09-19 14:24                                         ` Larry Finger
2013-09-15  8:17           ` Olivier Reuland
2013-09-15 13:50             ` Larry Finger
2013-09-15 17:48               ` Mark Cave-Ayland
2013-09-15 20:26                 ` Larry Finger

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=522DFF83.6000605@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=tgrundlesr@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).