On Tue, Jun 07, 2011 at 09:23:00PM +0200, Paul Bolle wrote: > On Tue, 2011-06-07 at 16:54 +0200, Stanislaw Gruszka wrote: > > That could be useful hint, we do not scan chan by chan, but we > > have thing called "plcp check health", which "restart radio" > > by requesting one channel scan. So perhaps disabling that could > > help. > > At this moment I'm interested in something (a script, some sequence of > actions, whatever) that (somewhat) reliably triggers this error. Because > right now I have no clue what triggers it. Having reliable reproducer will be definitely something that is nice to have. But bug could be some kind of race condition that happen in code flow once per 10000000000 cases ... > Is your patch in that category or is it a (crude) fix? If it's a fix, > I'm not sure it is of much help at this stage. It could be possible fix. Why you can not simply patch and see if errors are still there? If after a week or so there will be no errors, we could consider bug fixed, otherwise well ... still will need looking around for fix. I just posted patch that remove these "plcp health check" and related code on -next anyway, because I don't think this is something that we need. Stanislaw -- 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
