.. then I don't think it's specifically the NIC. >From what I understand, unless there are bus errors happening (and that'd occur with the NIC awake or having something being written to it) the NIC shouldn't be generating interrupts if: * sync/async cause are 0; * ier is 0; * imr is 0. Now maybe some part of ath9k is still trying to write to the NIC when it's asleep, but it would set some bits in sync_cause/async_cause. At this point I'd really suggest whacking other devices into the slot to see if they generate the same kind of behaviour. Adrian -- 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
