Peter Osterlund wrote: > I could do some trial-and-error debugging myself, but it's quite > annoying when I have to wait several hours to know if the kernel is > good or bad. I was thinking of changing this line > > schedule_delayed_work(&bcm->periodic_work, HZ * 15); > > in do_periodic_work so that the function runs more often, in the hope > that the bug would then trigger faster. Do you think changing the time > to say 1 second would cause other problems which would invalidate my > tests?
I'm not sure how touchy the system is about stuff like that. I suspect that the solution will come from thinking about interactions rather than from debugging experiments. At the moment, I have set BADNESS_LIMIT to 20 to see if that cures the instances when my interface just goes offline with nothing in the log. Usually an ifdown/ifup sequence will clear it, but once in a while I have to unload bcm43xx and reload it. Larry _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
