On Mon, Feb 6, 2012 at 1:33 PM, Johannes Berg <johannes.berg@xxxxxxxxx> wrote: > On Mon, 2012-02-06 at 22:27 +0100, Alexander Schnaidt wrote: > >> > I think you probably had something like "options iwlagn >> 11n_disable=1" or so in /etc/modprobe.d/ somewhere. This caused the >> problem to happen only with the driver called "iwlwifi", since >> "iwlagn" would get 11n disabled. > >> You're almost spot on!, somewhere along the bisect I put swcrypto=1 into >> modprobe.conf... so much for scientific reproducibility. Sorry for that. >> >> I redid the whole bisect with no options in modprobe.conf which defaults >> to swcrypto=0 on >=3.0 if I'm not mistaken. > > ... > >> If my interpretation is right the culprit would be: >> >> commit 5a3d9882b84edf5fa8e8ca33a5d6df25e2e727a5 >> Author: Johannes Berg <johannes.berg@xxxxxxxxx> >> Date: Fri Jul 15 13:03:12 2011 -0700 >> >> iwlagn: rewrite HW crypto > >> To me it makes sense considering that swcrypto=1 fixes >> my problems all the way up till kernel 3.3.0-rc2. >> >> ps.: 11n_disable=1 as suggested by Wey-Yi does not >> change the faulty behavior. >> >> Again I apologize for my blunder and thanks for the effort. > > Ok this makes sense. A few other people also recently reported this. I'm > currently (still) away from home so I can't reproduce this issue, and I > didn't find anything by just looking at the code. Traces for mac80211 > and iwlwifi subsystems would be useful to look at in this case, I think, > if you want to record the failure case see: > http://wireless.kernel.org/en/developers/Documentation/mac80211/tracing > (-e mac80211 -e iwlwifi). If you do record it, please don't send the > traces to the list, bzip2 it and send it to me directly. I just reproduced the problem (or at least the similar problem affecting me) with swcrypto=1. I'll try to get a trace. --Andy -- 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
