On Tue, Jun 2, 2009 at 6:13 PM, Luis R. Rodriguez > Here's an attempt to lock the ath9k rc private data but I > get a lockdep complaint on this and not sure how to resolve it yet. As it turns out the locking of the rate control private are *does* not resolve the incorrect rate table issue we were seeing. In fact the device works with it but every now and then would see issues with DMA, the laptop I can reproduce this on is at home and I forgot to send me the log. I'll try to send that tonight, but at least this indicates some other incorrect assumption is being made in the rate control code or driver. If it helps the traces of WARN_ON indicate this happens mostly when sending the null func, not sure why. This needs some further review and because of this until then we'll just have to down grade that ASSERT. Luis -- 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
