On Sat, Sep 20, 2008 at 1:57 PM, Luis R. Rodriguez <[EMAIL PROTECTED]> wrote: > So here's what we need to do -- try to zero on in what causes this IRQ > storm.
How is the best way to approach this? I assume ATH_DBG_INTERRUPT and pray like hell my /var partition doesn't fill up first? Maybe I'll just symlink /var/log/messages to a file on a substantially larger pattition... > Most likely its some strange event that triggers it, perhaps > some sort of noise which makes the device try to adapt and hits a path > we are not handling correctly yet. Can you provide the initial log of > when ath9k gets loaded? This tells us what card it is, like AR5416 or > AR9280, etc. [10238.347956] ath9k: 0.1 [10238.348028] vendor=8086 device=27d2 [10238.348033] ath9k 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [10238.348050] ath9k 0000:03:00.0: setting latency timer to 64 [10238.480781] phy1: Selected rate control algorithm 'ath9k_rate_control' [10238.483320] phy1: Atheros 5416: mem=0xffffc20000060000, irq=17 It claims to be a 5416, but I was under the impression that it was the 5418 that came with the MacBook Pro. _______________________________________________ ath9k-devel mailing list [email protected] https://lists.ath9k.org/mailman/listinfo/ath9k-devel
