Hi Maxim, > > > > I probably should work more to did these bugs out myself, but anyway I > > > > want to let you know what I currently see. > > > > > > > > First system oopses just after NM starts up, happens always, and after > > > > planting few test points bug happens somewhere in following lines. > > > > > > We are discussing a bug in the scan state machine in another thread, > > > which could have nasty consequences in not caught. And I don't quite > > > understand why my system was catching it immediately, maybe because I'm > > > using gcc 4.4, which has array bounds checking. > > Yea, there are two patches with same title for this, I applied the > > newer. > > > > Currently thanks to Johannes Berg, the patch > > [PATCH] nl80211: add missing parameter clearing > > Fixes this nasty oops, now wireless more or less works, but plenty of > > problems still, first it oopses on reconnect as inilialized from > > wpa_supplicant, second iwconfig misses most of its settings, and > > probably thus NM think signal level is zero. If I switch to good old > > wext in wpa_supplicant, it works just fine and none of above problems > > present (I recheck this again to be sure) > Except very frequent reconnects, > "[ 919.250097] No probe response from AP 00:1b:9e:d8:77:02 after 200ms, disconnecting." I have the same issue with my Intel 5350 card and if the signal strength of the AP gets a little bit weaker. Regards Marcel -- 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
