Vladimir Senkov wrote: > My client machine (running wireless-testing kernel updated with git > today) panics when connecting to a hostapd access point (also running > ath9k) only when 802.11n is enabled on the access point. > More specifically, here is the hostapd configuration that causes the > client to crash: > ieee80211n=0 > ht_capab=[HT40+][SHORT-GI-40][DSSS_CCK-40] ieee80211n should be 1 to enable 11n. > If I disable 802.11n on the access point everything works ok. > Interesting enough, access point machine never crashes. At one point > both access point and client machine ran identical code and client > would always crash while the access point box would stay up. So > upgraded client to the latest and greatest and tried a few versions in > between, this panic has been very consistent. It always panics right > after 1st attempt to associate. > > I was able to narrow down the panic to this assert ath_rc_ratefind_ht() in rc.c: > ASSERT((rate_table->info[rate].valid && !ath_rc_priv->single_stream) || > (rate_table->info[rate].valid_single_stream && > ath_rc_priv->single_stream)); > When I ifdef'ed this assert panic went away and everything sort of > worked (haven't tested it heavily), but the performance dropped to > about 700Kbps. I usually get 10x when 802.11n is off and there is no > panic. > > Has anyone else seen this? A couple of bugs were fixed dealing with this issue, but looks like more lurk around. Can you attach the hostapd.conf, hostapd logs (hostapd -d), client side kernel logs [1] ?, from loading the driver to the point when you associate and get the panic. [1]: See http://wireless.kernel.org/en/users/Drivers/ath9k on how to enable debug. Sujith -- 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
