On Mon, 2009-05-04 at 09:19 +0200, Johannes Berg wrote: > On Mon, 2009-05-04 at 00:46 +0300, Maxim Levitsky wrote: > > Yes, sure > > For record I use iwlwifi.git commit > > 5a94b6d38100b7056a5a347e5c51359d924d305d > > Ok. > > > Logs attached. > > This bug can be reliably reproduced, happens every 5~10 times when I > > turn rfkill on/off, but today again this happened after resume from > > disk. > > Ah, rfkill. Hmm, unfortunately I don't have a system with rfkill. I > looked at ieee80211_scan_work but can't see how it would abort the > scan... Could you put some debugging into that function? Especially > printing out the state when it enters, whether it calls Hi, I can't seem to reproduce that ether. Maybe this got fixed (I have seen few suspicios commits in wireless-testing... althought I think this is a wishfull thinking) Anyway, I I have put printks in ieee80211_scan_work. Best regards, Maxim Levitsky -- 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
