>>> But still, the interrupts come. Note that according to >>> /proc/interrupts, the IRQ line is not shared with any other device. >>> I did not manage to determine which interrupt it is exactly, >>> because the device is not in a ready state (SC_OP_INVALID is set) >>> when they happen (in either scenario that triggers the IRQ storm). >>> And SC_OP_INVALID is cleared only much later in ath9k_start. >>> >>> So, I am at a loss. Any ideas? >> >> please provide the lspci -vvvxx. >> also looking at >> /sys/kernel/debug/ieee80211/phy0/ath9k$ sudo cat interrupt. > > hi, i think this will help, please get the message sudo modprobe ath9k > debug=0xffffffff. > few fatal PCI interrupt messages are based on ATH_DEBUG_ANY. > thanks. > we can also try to disable MIB interrupts though its handled properly now in ath9k http://www.kernel.org/pub/linux/kernel/people/mcgrof/patches/ath9k/2008-09-25/0001-ath9k-disable-MIB-interrupts-to-fix-interrupt-storm.patch -- shafi -- 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
