>> So, I am building 3.2 with two patches: over/under-flow catcher (pity >that >> it seems to be on a multiple-times-per-second codepath and just leaving >the > > checks there for everyone is suboptimal) and allegedely proper fix. Both > > applied OK with a small offset. > > as per our assumption, we should not see those over/underflow errors, > with the patch > above mentioned. please let us know if you hit upon this warnings, > even after the proper fix. In my experience (and as I understand the situation) if garbage is writen to the "chan", it is caught by the check and device is dead-until-reboot anyway. On 3.0, even without checks device was dead-until-reboot, but no crash happened. All these checks do is converting "panic" to "WiFi broken" for 3.2. -- 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
