| Summary: | Disconnect problems with new RTL8192SE driver in kernel 2.6.40 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jussi Eloranta <eloranta> |
| Component: | NetworkManager | Assignee: | Dan Williams <dcbw> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 15 | CC: | dcbw, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, sangu.fedora |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | rtlwifi | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-08-07 16:03:13 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Jussi Eloranta
2011-08-05 11:17:32 UTC
I killed networkmanager and configure everything by hand. No more disconnects / hickups. So this probably has something to do with networkmanager. The link speed is also 58 mbs. It looks like you've roamed between several different access points, so NM is probably just picking the one with the strongest signal, and jumping to it. I don't believe the kernel driver will do that itself. Dan ? I don't think this is a kernel driver issue directly (?). Somehow networkmanager keeps roaming back and forth causing the connection to stall. Also the N-mode probably works fine since everything was OK when manually configuring the connection. I can see that, for some odd reason, the signal strength was about 70/70 with manual configuration and somewhere between 50 - 70 / 70 with network manager. Could it be that there are several access points with similar signal strengths and networkmanager can't decide which to keep using? Also dmesg shows that there are complaints about timeouts, which could have something to do with the kernel driver. Reason code 2 is "previous authentication no longer valid". (Sometimes I wonder if we should just embed these reason codes text strings in the kernel.) I agree w/ Dave, it seems like the driver is basically just doing what NM is telling it to do. The /var/adm/messages info suggests that the Wifi-Residents network has a number of APs and NM is trying to roam between them. The Reason code suggests that authentication info is not being properly shared between the APs on the Wifi-Residents network, so the Reassociation requests that are part of the roaming effort are failing. Maybe NM has some settings that can influence this behaviour? Or maybe NM needs to try roaming with Associations rather than Reassociations? Dunno... I'm going to move this to NetworkManager for now, until Dan or some other NM person can tell me how I'm getting it all wrong... :-) This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |