From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Timothy Rundle <tgrundlesr@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: RTL8192CU continually reconnecting
Date: Mon, 09 Sep 2013 23:05:50 +0100 [thread overview]
Message-ID: <522E463E.4040701@ilande.co.uk> (raw)
In-Reply-To: <522E1B7D.5010107@lwfinger.net>
On 09/09/13 20:03, Larry Finger wrote:
> There were no secrets in that dump, but it did reveal a major clue.
>
> A response from your system for your AP was:
>
> mode 2, state 0, is_beacon 0, is_probe_resp 1, length 147
>
> For the number of beacons to be updated, the state has to be 2 or 3. My
> system has scan_ssid=1 in the wpa_supplicant configuration file. When
> the scan finishes, then a value of 2 is set into the mode variable.
>
> The attached updated patch should set the correct mode even if scanning
> is not enabled.
Aha! This patch is definitely a step in the right direction - with this
applied, wpa_supplicant now associates immediately with the AP without
the initial delay :)
However... I'm still seeing the same
"rtlwifi:rtl_watchdog_wq_callback():<0-0> AP off, try to reconnect now"
message appearing in dmesg after every 10s or so. I've uploaded the
updated dmesg output to
http://www.ilande.co.uk/tmp/rtl8192cu_patch-2-dmesg.txt for you to take
a look at.
I also tried another experiment which was to change your patch so that
instead of logging just the first 100 beacons to dmesg, log every 10th
beacon (count % 10) to dmesg instead. This showed that even when the
timeouts are occurring against the AP, I'm still seeing a continual
stream of beacons from other stations on the network.
This makes me wonder if Oleksij is correct in that the problem is that
not all the frames coming from the USB interface are being picked up by
the driver. Perhaps not all incoming USB RX buffers are being scanned
(causing some queued frames to be lost) or maybe USB transfers can
contain more than 1 frame and rtlwifi is only catching the first frame
within each notified transfer?
To double check whether it was a general ehci-pci problem, I tried
plugging in a spare zd1211rw dongle and that worked absolutely fine. So
I think that's a reasonable indication that general USB function is okay.
ATB,
Mark.
next prev parent reply other threads:[~2013-09-09 22:06 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
[not found] ` <522E0573.4000804@ilande.co.uk>
2013-09-09 19:03 ` Larry Finger
2013-09-09 22:05 ` Mark Cave-Ayland [this message]
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=522E463E.4040701@ilande.co.uk \
--to=mark.cave-ayland@ilande.co.uk \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--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).