Olivier Crête wrote: > On Sat, 2011-07-16 at 18:09 -0500, Larry Finger wrote: >> On 07/16/2011 04:17 PM, Olivier Crête wrote: >>> 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? > > I can only reproduce it with torrents, downloading something with a > single TCP connection doesn't crash. So my guess it has something to do > with the upload side maybe or maybe with loading both directions at the > same time. > >> Please try to repeat with a 2.6.39 or 3.0 kernel. > > Alright, upgraded to 3.0-rc7 and I could still reproduce it in less than > 10 minutes. Do you have a SMP-machine (there are running more then one threads parallel)? If yes, there have been problems fixed in the rt2x00 driver, which showed similar problems as you described. I "forced" them with netperf to get them easily reproduced. Don't know, if these patches would address your problem, too. https://patchwork.kernel.org/patch/951132/ https://patchwork.kernel.org/patch/951222/ https://patchwork.kernel.org/patch/951192/ Unfortunately, there are more load-related problems in the WLAN stack, especially with hostapd / wpa_supplicant, which are just ignored by the programmer. Andreas -- 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
