Bug 676840

Summary: RTL8180L connection and performance problems
Product: [Fedora] Fedora Reporter: Huub <huubvanniekerk>
Component: kernelAssignee: Stanislaw Gruszka <sgruszka>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 16CC: gansalmon, itamar, jonathan, kernel-maint, kkelley64, madhu.chinakonda, sgruszka
Target Milestone: ---   
Target Release: ---   
Hardware: athlon   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-04-04 21:59:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Output of "dmesg | grep wlan0" none

Description Huub 2011-02-11 14:02:23 UTC
Description of problem:
Kernel crash; wireless network not functioning

Version-Release number of selected component (if applicable):
2.6.35.6-45.fc4.i686

How reproducible:
Accessing the wireless network using either RTL8180L or RT2561/RT61. (No problem on Fedora 13)

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
WARNING: at net/wireless/scan.c:580 cfg80211_inform_bss_frame +0x5b/0x13c [cfg80211]()

Comment 1 Kearn Kelley 2011-02-18 02:52:32 UTC
I'm getting the same error with a zd1211 based adapter

Comment 2 Stanislaw Gruszka 2011-04-06 21:31:40 UTC
We have updated kernel to 2.6.35.12
http://koji.fedoraproject.org/koji/buildinfo?buildID=236995
perhaps it fix that problem, please check out.

If not, can we get full dmesg of failure?

Comment 3 Huub 2011-04-07 20:10:42 UTC
Unfortunately it is not working for me. I checked extensively with the RT61 card (pcmcia) which does work. This is the dmesg on the RTL card:
[   39.114788] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  123.960007] wlan0: deauthenticating from 00:1e:e5:f9:a2:6d by local choice (reason=3)
[  124.209056] wlan0: authenticate with 00:1e:e5:f9:a2:6d (try 1)
[  124.213058] wlan0: authenticated
[  124.233273] wlan0: associate with 00:1e:e5:f9:a2:6d (try 1)
[  124.253481] wlan0: RX AssocResp from 00:1e:e5:f9:a2:6d (capab=0x411 status=0 aid=2)
[  124.253489] wlan0: associated
[  124.255170] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[  135.122036] wlan0: no IPv6 routers present
[  278.897973] wlan0: deauthenticating from 00:1e:e5:f9:a2:6d by local choice (reason=3)
[  284.363490] wlan0: deauthenticating from 00:1e:e5:f9:a2:6d by local choice (reason=3)
[  284.593096] wlan0: authenticate with 00:1e:e5:f9:a2:6d (try 1)
[  284.594751] wlan0: authenticated
[  284.614058] wlan0: associate with 00:1e:e5:f9:a2:6d (try 1)
[  284.634053] wlan0: RX AssocResp from 00:1e:e5:f9:a2:6d (capab=0x411 status=0 aid=2)
[  284.634059] wlan0: associated
[ 1260.944566] wlan0: deauthenticating from 00:1e:e5:f9:a2:6d by local choice (reason=3)
[ 1375.477097] wlan0: deauthenticating from 00:1e:e5:f9:a2:6d by local choice (reason=3)
[ 1375.707079] wlan0: authenticate with 00:1e:e5:f9:a2:6d (try 1)
[ 1375.708576] wlan0: authenticated
[ 1375.728056] wlan0: associate with 00:1e:e5:f9:a2:6d (try 1)
[ 1375.748060] wlan0: RX AssocResp from 00:1e:e5:f9:a2:6d (capab=0x411 status=0 aid=2)
[ 1375.748067] wlan0: associated
[ 1534.221696] wlan0: deauthenticating from 00:1e:e5:f9:a2:6d by local choice (reason=3)
[ 1626.650163] wlan0: deauthenticating from 00:1e:e5:f9:a2:6d by local choice (reason=3)
[ 1626.880109] wlan0: authenticate with 00:1e:e5:f9:a2:6d (try 1)
[ 1626.881702] wlan0: authenticated
[ 1626.901053] wlan0: associate with 00:1e:e5:f9:a2:6d (try 1)
[ 1626.921087] wlan0: RX AssocResp from 00:1e:e5:f9:a2:6d (capab=0x411 status=0 aid=2)
[ 1626.921100] wlan0: associated
[ 1686.180183] wlan0: deauthenticating from 00:1e:e5:f9:a2:6d by local choice (reason=3)

It does connect to the WLAN, but somehow it fails to receive data. Don't know about sending.

Comment 4 Stanislaw Gruszka 2012-01-21 18:20:22 UTC
Is this issue still present in F-16 and/or F-15 ?

Comment 5 Huub 2012-01-22 08:26:19 UTC
(In reply to comment #4)
> Is this issue still present in F-16 and/or F-15 ?

Using F16, the issue has been kind-of resolved. The RTL does have connection now, but it is not stable. Some websites load reasonably fast, others indicate the connection is made but do not load. Of the websites that don not load. some keep loading, some time out. Using the RT61, everything is as fast as should be.

Comment 6 Huub 2012-01-22 08:28:58 UTC
Created attachment 556751 [details]
Output of "dmesg | grep wlan0"

This is the output of "dmesg | grep wlan0"

Comment 7 Huub 2012-02-01 08:01:29 UTC
With the latest F16 kernel update, kernel-3.2.2-1.fc16.i686, my wireless (both RT61 and RTL) does not start. Going back to kernel-3.2.1-3.fc16.i686 my wireless works as described previously.

Comment 8 Stanislaw Gruszka 2012-02-01 08:22:26 UTC
3.2.2-1 has problem with eeprom module (bug 785393), this should be fixed soon.

Comment 9 Dave Jones 2012-03-22 16:45:58 UTC
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 10 Dave Jones 2012-03-22 16:50:34 UTC
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 11 Dave Jones 2012-03-22 17:00:30 UTC
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 12 Huub 2012-03-23 07:35:06 UTC
Did the requested retesting. The performance has clearly improved, but compared to the RT61 not up to speed yet. While the ping command delivers a reasonably acceptable result, loading webpages still takes too long. An average page takes well over 10 seconds to load, while the RT61 loads the same page in 5 seconds or less.

Comment 13 Stanislaw Gruszka 2012-04-04 21:59:32 UTC
I'm sorry, but I will not fix this bug, rtl8180L is old device and I have some more serious issues on more recent hardware.

Comment 14 Stanislaw Gruszka 2012-04-04 22:00:27 UTC
Changing the topic to reflect the problem.