2010/6/29 Björn Smedman <bjorn.smedman@xxxxxxxxxxx>: > Yes, hw reset is due to reg = 0x01702400 every 4 - 40 seconds or so: > ... When the chip is really stuck, does 'reg' (at 'return false') change over time? If I add a second requirement that ath9k_hw_check_alive() must fail three times in a row (in different invocations of ath9k_tasklet()) before we reset the chip the ap seems fine. I sometimes get several of these reg = 0x01702400 every second but only one or at the max two in a row. Under load I sometimes see some reg = 0x00f02400 as well. I also see an occasional reset now and then (about once a minute) that must be caused by something else. Any insight into what these reg values mean? Do you think they can safely be ignored as per above? /Björn -- 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
