Hi Mohammed, On Wed, Oct 12, 2011 at 06:40:06PM +0530, Mohammed Shafi wrote: > > please try this in case it helps anything > to debug the issue. With this, the previous instaces of 0xdeadbeaf are replaced with zeroes, and I do not get any non-zero traces for SYNC_CAUSE or ASYNC_CAUSE any more. > this should avoid dead beef and the interrupt when we access MAC > registers when the MAC is asleep. also i did not see MAC irq being not > triggerred in your case(AR_INTR_ASYNC_CAUSE should be 0x2) or may be > its not an interrupt triggered by the chip itself. thanks If it's not triggered by ath9k, I do wonder why it works if I suspend in connected mode, and why reloading the driver usually fixes the issue. Maybe there is something in the driver unloading code that we could look at? Clemens -- 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
