rtl8187 drops connection
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Invalid
|
Medium
|
|||
linux (Ubuntu) |
In Progress
|
Medium
|
Unassigned | ||
lynx (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
I have a ASUS P5K motherboard with integrated wireless based on rtl8187. In Hardy (haven't tried other Ubuntu versions) the connection often suddenly fails, with the software not noticing anything.
Nothing is logged in dmesg or syslog except for (sometimes): WEP decrypt failed (ICV)
I have noticed this string also appears in the log at times when the interface does _not_ fail.
The computer continues on oblivious to the fact that it has just lost its network connection (networkmanager is not installed, but gnome's network monitor applet indicates a good connection). In fact, a wireshark dump indicates that the computer still thinks it is sending 802.11 frames, but monitoring from another computer (with a reliable wireless driver) indicates that nothing is being sent from the affected computer, even while the AP is chugging along trying to contact a host which has mysteriously dropped offline. I have noticed this problem across kernel images (2.6.24-3-generic and 2.6.24-4-generic to be specific). In one instance, I found that modprobing the module out and back in again fixed it, while another time this caused modprobe to use 100% CPU and become unresponsive, even to kill signals (Yeah, the kill -9 kind).
If any more information is necessary please ask and I'll do my best.
This also effects Intrepid Ibex/2.
description: | updated |
Changed in linux: | |
status: | Unknown → Confirmed |
Changed in linux: | |
status: | Confirmed → Incomplete |
Changed in linux: | |
status: | Incomplete → Invalid |
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
tags: | added: iso-testing |
Changed in linux: | |
importance: | Unknown → Medium |
Hi Josh,
Thank you for taking the time to report this bug and helping to make Ubuntu better. Per the kernel team's bug policy, can you please attach the following information. Please be sure to attach each file as a separate attachment.
* uname -a > uname-a.log signature > version.log
* cat /proc/version_
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log
For more information regarding the kernel team bug policy, please refer to https:/ /wiki.ubuntu. com/KernelTeamB ugPolicies . Thanks again and we appreciate your help and feedback.