On 07/16/2011 04:17 PM, Olivier Crête wrote:
Hello,
It's a regularly reproducible bug: under some load, like a couple
torrents running, but not enough to saturate the wireless link (and not
even enough to saturate the ADSL link on the other side), the card stops
sending or receiving any packet. Unloading and reloading the rtl8187
driver fixes the problem.
Kernel version is 2.6.38, but it also happened with older versions, and
I haven't bothered testing new ones since there are no changes in that
driver.
This assumption may not be valid as there have been a lot of changes in
mac80211, which might fix this.
I get this on my dmesg:
ieee80211 phy0: wlan0: No probe response from AP 00:0f:66:e2:5f:dd after 500ms, disconnecting.
cfg80211: Calling CRDA to update world regulatory domain
wlan0: authenticate with 00:0f:66:e2:5f:dd (try 1)
wlan0: authenticate with 00:0f:66:e2:5f:dd (try 2)
wlan0: authenticate with 00:0f:66:e2:5f:dd (try 3)
wlan0: authentication with 00:0f:66:e2:5f:dd timed out
The wireless card is the one built-in a Asus P5K-E/wifi-ap motherboard.
And the router is a WRT54G v2 running the latest OpenWRT.
This bit of dmesg output may also be useful:
usb 1-3: reset high speed USB device using ehci_hcd and address 2
cfg80211: Calling CRDA to update world regulatory domain
ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
ieee80211 phy0: hwaddr 00:15:af:37:19:b3, RTL8187vB (default) V1 + rtl8225z2, rfkill mask 2
I have the same device as you as shown in the following:
ieee80211 phy1: hwaddr 00:1b:2f:a2:07:ca, RTL8187vB (default) V1 + rtl8225z2,
rfkill mask 2
I have run this card extensively in the past several months and have not seen
any problems. One of my APs is a WRT54GL running a fairly recent openWRT.
Does this only happen when running torrents, or does it happen with a different
heavy load?
Please try to repeat with a 2.6.39 or 3.0 kernel.
Larry
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
