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 <linux-wireless@vger.kernel.org>
Subject: Re: RTL8192CU continually reconnecting
Date: Tue, 10 Sep 2013 10:14:31 -0500	[thread overview]
Message-ID: <522F3757.8030600@lwfinger.net> (raw)
In-Reply-To: <522EB51A.2080004@ilande.co.uk>

On 09/10/2013 12:58 AM, Mark Cave-Ayland wrote:
>
> No worries - disk space is reasonably cheap these days ;)
>
> dmesg output:
> http://www.ilande.co.uk/tmp/rtl8192cu_patch-4-dmesg.txt
>
> wpa_supplicant output:
> http://www.ilande.co.uk/tmp/rtl8192cu_patch-4-wpa_supplicant.txt
>
> I noticed that I got several re-authentication attempts in the dmesg output
> without the corresponding rtl_watchdog_wq_callback() line being emitted - this
> is again something I don't see with zd1211rw and iwlwifi. Once these drivers are
> associated, they seem to stay in that state for hours.

Those disconnects do happen for reasons that I do not understand. They will be 
worse on your system without a network manager as it appears that you need to 
manually reconnect at that point, or at least it took a long time for the system 
to react. With NetworkManager, that reconnect is automatic, and relatively quick.

> Whilst checking various parts of my kernel, I noticed for the first time during
> testing that my current kernel configuration doesn't have SMP enabled. This got
> me thinking that perhaps there are other build options which could have an
> effect on the driver. Hence I also uploaded a copy of my .config file to
> http://www.ilande.co.uk/tmp/rtl8192cu-config in the hope that maybe this can
> help you recreate the issue locally?

As I have a dual-core CPU, thus I always have SMP set. That should not be a 
problem. In fact, the concurrent operation of 2 CPUs usually causes more 
problems. I will review that configuration.

You can now disable the logging. When the watchdog reports that contact with the 
AP has been lost, that is certainly true, and the watchdog is doing its job. In 
addition, nothing was received from any AP, which leads me to conclude that the 
receiver has locked up for some reason. I need to check to see what the code 
does to recover. Perhaps that will help me understand the problem. In my current 
run that has run for 20 hours, I have had two disconnects for Reason 3, but more 
importantly, I have had two watchdog restarts. It does happen on my system, just 
a lot less frequently. BTW, my ping loss rate is about 3%. That is too high, but 
not as bad as yours.

Larry



  reply	other threads:[~2013-09-10 15:14 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
2013-09-10  2:52                     ` Larry Finger
2013-09-10  5:58                       ` Mark Cave-Ayland
2013-09-10 15:14                         ` Larry Finger [this message]
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=522F3757.8030600@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).