On Sat, 2009-07-25 at 17:10 +0300, Maxim Levitsky wrote: > 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. I have also seen two oopses in the code unrelated to wireless networking, one of which lead to my .bash_history becoming empty. So please be extra careful. It would be great if somebody could test the current kernel extensively with kmemcheck an other options and bisect the bad commit, whether it's wireless related or not. -- Regards, Pavel Roskin -- 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
