On 21 October 2011 18:22, Clemens Buchacher <drizzd@xxxxxx> wrote: > It matches AR_SREV_9285, but it does not match AR_SREV_9285E_20. Ok. Well, I've read the ar9285 host documentation that I've gotten my hands on and I can't see anything obvious. All I can think of is that something else is throwing those interrupts - whether it's the NIC throwing the error, or whether its the bus itself throwing an error and you're seeing the AR9285 because it's the only thing attached. I however know next to nothing about PCI/PCIe and the various fruity behaviour seen. I assume you have disabled the NIC power save option. Not just APSM, etc, but the powersave options in iw. I don't know what they are, sorry, only that they exist. I suggest modifying ath_intr() so if there is an interrupt storm, disable _all_ sources of interrupts (ie, set sync_cause, async_cause to 0, set imr to 0, set ier to 0) and see if it continues occuring. If the interrupt storm continue occuring, try putting the whole NIC to sleep entirely (ie, call pcipowersave to put the NIC to sleep, then make sure the NIC -stays- asleep somehow, ie so nothing else tries waking it up - I don't know how to do this, likely you'll have to clear some interface flag so the rest of the ath9k and 802.11 stack thinks the nic is actually down for the count) and see if you're still getting spurious interrupts. If you are at this point, the only other possible thing I can think of doing involves a PCIe bus analyser, and you/I don't have access to those. :-) 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
