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: Tue, 10 Sep 2013 00:45:07 +0100 [thread overview]
Message-ID: <522E5D83.9060103@ilande.co.uk> (raw)
In-Reply-To: <522E5416.4010901@lwfinger.net>
On 10/09/13 00:04, Larry Finger wrote:
>> 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.
>
> Looking at only every 10th one could be systematically missing the ones
> from your AP.
Oh sure - what I was looking to prove was whether it was all beacons
that weren't getting through, or just the ones from the AP when the
timeout occurred.
>> 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?
>
> None of those suppositions make any sense.
Well I freely admit that I don't have much knowledge of the kernel USB
layers (only from some old embedded systems years ago), so it was really
just a case of thinking out loud...
>> 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.
>
> I do not suspect any USB problem unless it is in rtl8192cu.
Okay.
> Could you please run the attached patch? It will only print messages for
> your AP, and print enough to still be getting them when the AP timeout
> occurs.
Done.
dmesg output:
http://www.ilande.co.uk/tmp/rtl8192cu_patch-3-dmesg.txt
wpa_supplicant output:
http://www.ilande.co.uk/tmp/rtl8192cu_patch-3-wpa_supplicant.txt
Now the interesting part was as you can see from the logs, I managed to
get a reasonably long association to the AP towards the end so I tried
running dhclient against the wlan1 interface - this was slow, taking
about 60s to complete, but it did eventually return with an IP address.
With that in place, I tried pinging 8.8.8.8 and ended up with a very
poor connection, with the ping exit banner reporting 87% packet loss :(
ATB,
Mark.
next prev parent reply other threads:[~2013-09-09 23:46 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
2013-09-09 23:04 ` Larry Finger
2013-09-09 23:45 ` Mark Cave-Ayland [this message]
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=522E5D83.9060103@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 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.