0bda:8178 RTL8192CU continually reconnecting

Bug #1220007 reported by Timothy G. Rundle
104
This bug affects 23 people
Affects Status Importance Assigned to Milestone
Linux
New
Undecided
Unassigned
linux (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

When using the built in rtl8192cu driver, it continually disconnects/reconnects every couple of seconds making network use unusable.

WORKAROUND: The proprietary driver works just fine.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-4-generic 3.11.0-4.9
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic x86_64
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: timothy 1977 F.... pulseaudio
 /dev/snd/controlC1: timothy 1977 F.... pulseaudio
 /dev/snd/controlC0: timothy 1977 F.... pulseaudio
 /dev/snd/pcmC0D0p: timothy 1977 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Date: Mon Sep 2 10:18:23 2013
MachineType: System manufacturer System Product Name
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic root=UUID=9d909d71-fead-4686-9fdd-87c6c7c8ae4d ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-4-generic N/A
 linux-backports-modules-3.11.0-4-generic N/A
 linux-firmware 1.113
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to saucy on 2013-05-23 (102 days ago)
dmi.bios.date: 08/23/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2801
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M3A78-CM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2801:bd08/23/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3A78-CM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Timothy G. Rundle (tgrundle) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Re: RTL8192CU continually reconnecting

Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of the introduction of a regression, and when this regression was introduced. If this is a regression, we can perform a kernel bisect to identify the commit that introduced the problem.

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Timothy G. Rundle (tgrundle) wrote : Re: [Bug 1220007] Re: RTL8192CU continually reconnecting
Download full text (3.8 KiB)

The built in rtl8192cu driver has never worked for me. I only got the
device 4-5 months ago and at first I couldn't even connect I believe
that issue was related to LP#852190
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/852190/comments/170).
I switched to the native driver with some patches i found online setup
via dkms. That has worked well, but I figured I should report the
issue with the rtl8192cu driver.

I did test the mainline kernel last night (9/2) and the issue was still present.

On Tue, Sep 3, 2013 at 1:28 PM, Joseph Salisbury
<email address hidden> wrote:
> Did this issue start happening after an update/upgrade? Was there a
> kernel version where you were not having this particular problem? This
> will help determine if the problem you are seeing is the result of the
> introduction of a regression, and when this regression was introduced.
> If this is a regression, we can perform a kernel bisect to identify the
> commit that introduced the problem.
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1220007
>
> Title:
> RTL8192CU continually reconnecting
>
> Status in “linux” package in Ubuntu:
> Incomplete
>
> Bug description:
> When using the built in rtl8192cu driver, it continually
> disconnects/reconnects every couple of seconds making network use
> unusable. The proprietary driver works just fine.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 13.10
> Package: linux-image-3.11.0-4-generic 3.11.0-4.9
> ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
> Uname: Linux 3.11.0-4-generic x86_64
> ApportVersion: 2.12.1-0ubuntu3
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC2: timothy 1977 F.... pulseaudio
> /dev/snd/controlC1: timothy 1977 F.... pulseaudio
> /dev/snd/controlC0: timothy 1977 F.... pulseaudio
> /dev/snd/pcmC0D0p: timothy 1977 F...m pulseaudio
> CRDA: Error: [Errno 2] No such file or directory: 'iw'
> Date: Mon Sep 2 10:18:23 2013
> MachineType: System manufacturer System Product Name
> MarkForUpload: True
> ProcEnviron:
> TERM=xterm
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcFB: 0 radeondrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic root=UUID=9d909d71-fead-4686-9fdd-87c6c7c8ae4d ro quiet splash
> RelatedPackageVersions:
> linux-restricted-modules-3.11.0-4-generic N/A
> linux-backports-modules-3.11.0-4-generic N/A
> linux-firmware 1.113
> RfKill:
> 0: phy0: Wireless LAN
> Soft blocked: no
> Hard blocked: no
> SourcePackage: linux
> UpgradeStatus: Upgraded to saucy on 2013-05-23 (102 days ago)
> dmi.bios.date: 08/23/2010
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: 2801
> dmi.board.asset.tag: To Be Filled By O.E.M.
> dmi.board.name: M3A78-CM
> dmi.board.vendor: ASUSTeK Computer...

Read more...

Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Re: RTL8192CU continually reconnecting

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

Changed in linux (Ubuntu):
status: Incomplete → Triaged
tags: added: kernel-bug- reported-upstream
Revision history for this message
Timothy G. Rundle (tgrundle) wrote :

I have emailed the mailing list. I did find two other people having a similar issue [0] and [1]. Hopefully there will be a resolution soon. The latest mainline kernel breaks the proprietary driver, which I have been using as a fallback.

[0] http://article.gmane.org/gmane.linux.kernel.wireless.general/111880
[1] http://article.gmane.org/gmane.linux.kernel.wireless.general/112372

Revision history for this message
Timothy G. Rundle (tgrundle) wrote :

I received a response from upstream [0]. He believed the issue is "a bad interaction with the Ubuntu front-end to wireless." Doesn't Ubuntu just use Network-Manager? Are there any Ubuntu specific modifications?

A patch was provided, but it is not expected to correct the issue. I am going to attempt to get the latest source, apply the patch, and compile the module myself.

[0] http://article.gmane.org/gmane.linux.kernel.wireless.general/112817

Revision history for this message
Olivier Reuland (olivier-reuland) wrote :
Download full text (44.1 KiB)

Hello,

I'm greatly impacted by this as well. I'm going to try to provide some more details, which is a pain as my connection goes down every few minutes because of this problem...

1) here is a "successful disconnect cycle": It should not disconnect in the first place, but at least is reconnects... (I'm not in Germany, so not certain why it tries to set "cfg80211: Calling CRDA for country: DE" )

Sep 15 19:15:58 desktop kernel: [ 1506.404665] wlan0: Connection to AP 9c:c7:a6:1c:dc:a5 lost
Sep 15 19:15:58 desktop wpa_supplicant[3920]: wlan0: CTRL-EVENT-DISCONNECTED bssid=9c:c7:a6:1c:dc:a5 reason=4
Sep 15 19:15:58 desktop kernel: [ 1506.475413] cfg80211: Calling CRDA to update world regulatory domain
Sep 15 19:15:58 desktop NetworkManager[791]: <info> (wlan0): supplicant interface state: completed -> disconnected
Sep 15 19:15:58 desktop kernel: [ 1506.481584] cfg80211: World regulatory domain updated:
Sep 15 19:15:58 desktop kernel: [ 1506.481590] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Sep 15 19:15:58 desktop kernel: [ 1506.481596] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Sep 15 19:15:58 desktop kernel: [ 1506.481600] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Sep 15 19:15:58 desktop kernel: [ 1506.481604] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Sep 15 19:15:58 desktop kernel: [ 1506.481607] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Sep 15 19:15:58 desktop kernel: [ 1506.481612] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Sep 15 19:15:58 desktop NetworkManager[791]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Sep 15 19:16:05 desktop wpa_supplicant[3920]: wlan0: SME: Trying to authenticate with 9c:c7:a6:1c:dc:a5 (SSID='MyWiFi' freq=2462 MHz)
Sep 15 19:16:05 desktop kernel: [ 1512.972643] wlan0: authenticate with 9c:c7:a6:1c:dc:a5
Sep 15 19:16:05 desktop kernel: [ 1512.985470] wlan0: send auth to 9c:c7:a6:1c:dc:a5 (try 1/3)
Sep 15 19:16:05 desktop NetworkManager[791]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Sep 15 19:16:05 desktop kernel: [ 1513.091927] wlan0: send auth to 9c:c7:a6:1c:dc:a5 (try 2/3)
Sep 15 19:16:05 desktop wpa_supplicant[3920]: wlan0: Trying to associate with 9c:c7:a6:1c:dc:a5 (SSID='MyWiFi' freq=2462 MHz)
Sep 15 19:16:05 desktop kernel: [ 1513.106938] wlan0: authenticated
Sep 15 19:16:05 desktop kernel: [ 1513.107890] wlan0: associate with 9c:c7:a6:1c:dc:a5 (try 1/3)
Sep 15 19:16:05 desktop NetworkManager[791]: <info> (wlan0): supplicant interface state: authenticating -> associating
Sep 15 19:16:05 desktop wpa_supplicant[3920]: wlan0: Associated with 9c:c7:a6:1c:dc:a5
Sep 15 19:16:05 desktop kernel: [ 1513.131214] wlan0: RX AssocResp from 9c:c7:a6:1c:dc:a5 (capab=0x431 status=0 aid=1)
Sep 15 19:16:05 desktop kernel: [ 1513.131270] wlan0: associated
Sep 15 19:16:05 desktop kernel: [ 1513.131428] cfg80211: Calling CRDA for country: DE
Sep 15 19:16:05 desktop NetworkManager[791]: <info> (wlan0): supplicant interface state: associating -> associated
Sep 15 19:16:05 desktop kernel: [ 1...

Revision history for this message
Timothy G. Rundle (tgrundle) wrote :

Upstream has provided me a patch. It it only for the 3.11 kernel as there have been significant changes between 3.8 and 3.11 to the rtlwifi drivers. I wasn't given a timeline as to when the patch would be committed. There was also provided updated firmware.

For those that like me that have never patch a kernel module here are the steps I took:

As root:
    apt-get install linux-source
    cd /usr/src
    tar -xf linux-source-3.11.0.tar.bz2
    cd linux-source-3.11.0
    patch -p1 < /path-to/master_patch_09_24.txt
    cp /lib/modules/`uname -r`/build/Module.symvers .
    make clean
    make oldconfig
    make prepare
    make modules_prepare
    make SUBDIRS=scripts/mod
    make SUBDIRS=drivers/net/wireless/rtlwifi
    for i in `find . -name '*.ko'`; do cp $i /lib/modules/`uname -r`/kernel/$i;done;
    #make sure to unblacklist the modules if you have blacklisted them and to blacklist the vendor 8192cu if installed
    reboot

To rollback:
    apt-get --reinstall install linux-image-`uname -r`

Revision history for this message
Timothy G. Rundle (tgrundle) wrote :

Updated firmware. Goes in /lib/firmware/rtlwifi

tags: added: patch
penalvch (penalvch)
description: updated
summary: - RTL8192CU continually reconnecting
+ 0bda:8178 RTL8192CU continually reconnecting
tags: added: kernel-bug-reported-upstream latest-bios-2801
removed: kernel-bug- reported-upstream
Revision history for this message
Sundance (sundance-greydragon) wrote :

Meanwhile, maybe you will find this useful. It's the Realtek 8192cu driver ported for Ubuntu 13.10: https://github.com/pvaret/rtl8192cu-fixes

Revision history for this message
Aaron Peromsik (aperomsik) wrote :

+tgrundle does that patch from #9 work for you? It's not working for me. I built per your instructions-- thanks for spelling it out like that. Now I see in dmesg that it is loading the new firmware, but then it repeatedly gets either "authenticating with ... timed out" or, when it does manage to authenticate, "associating with ... timed out" instead.

Revision history for this message
Timothy G. Rundle (tgrundle) wrote :

Yes, I have been using the patched rtl8192cu driver for a month without any issues.

The guys on the linux-wireless team were really good to work with. I suggest opening your own bug on launchpad and then follow the directions in comment #5.

Revision history for this message
Juergen Scholz (juergen.scholz) wrote :

I am affected by this, too.

It looks like this for me in dmesg:
[ 1751.552607] wlan0: authenticate with 58:6d:8f:89:bc:29
[ 1751.576584] wlan0: send auth to 58:6d:8f:89:bc:29 (try 1/3)
[ 1751.582066] wlan0: authenticated
[ 1751.584186] wlan0: associate with 58:6d:8f:89:bc:29 (try 1/3)
[ 1751.597243] wlan0: RX AssocResp from 58:6d:8f:89:bc:29 (capab=0x431 status=0 aid=4)
[ 1751.597390] wlan0: associated
[ 1751.597486] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 1754.603862] wlan0: deauthenticated from 58:6d:8f:89:bc:29 (Reason: 2)
[ 1754.620940] cfg80211: Calling CRDA to update world regulatory domain
[ 1754.628321] cfg80211: World regulatory domain updated:
[ 1754.628331] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 1754.628338] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 1754.628344] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 1754.628349] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 1754.628354] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 1754.628358] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 2175.469567] wlan0: authenticate with 58:6d:8f:89:bc:29
[ 2175.482960] wlan0: send auth to 58:6d:8f:89:bc:29 (try 1/3)
[ 2175.492290] wlan0: authenticated
[ 2175.492655] wlan0: associate with 58:6d:8f:89:bc:29 (try 1/3)
[ 2175.504294] wlan0: RX AssocResp from 58:6d:8f:89:bc:29 (capab=0x431 status=0 aid=4)
[ 2175.504396] wlan0: associated
[ 2178.510676] wlan0: deauthenticated from 58:6d:8f:89:bc:29 (Reason: 2)
[ 2178.529384] cfg80211: Calling CRDA to update world regulatory domain
[ 2178.536350] cfg80211: World regulatory domain updated:
[ 2178.536359] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 2178.536367] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 2178.536373] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 2178.536378] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 2178.536382] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 2178.536387] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)

mmedt (mhmtylkn)
no longer affects: linux
Revision history for this message
intialonso (intialonso) wrote :

OK, bug reported in 2013... is now march of 2017 and Im suffering. Pretty sad situation.
USB WIfi: TL-WN8200ND

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.