Re: [ath9k-devel] ath9k: massive unexplained latency in 2.6.27 (rc5, rc6, probably others)

From: Steven Noonan
Date: Thu Sep 18 2008 - 15:01:06 EST


On Thu, Sep 18, 2008 at 11:42 AM, Luis R. Rodriguez
<lrodriguez@xxxxxxxxxxx> wrote:
> On Thu, Sep 18, 2008 at 11:34 AM, Luis R. Rodriguez
>> irqpoll is a monster of evil and that should make your system crawl to
>> its knees. I would advise instead we work with you fixing the the
>> missed interrupts issue upon rmmod.
>
> Also, please provide the output of
>
> cat /proc/interrupts

Note that the problem necessitating use of irqpoll in the first place
seems to only happen under certain conditions. I am unsure what these
conditions are. Before 'ath9k: connectivity is lost after Group
rekeying is done', I had used rmmod/modprobe as my solution to the
issue, which triggered the IRQ issue.

alcarin steven # cat /proc/interrupts
CPU0 CPU1
0x0: 63227 0 IO-APIC-edge hpet
0x8: 1 0 IO-APIC-edge rtc0
0x9: 13080 0 IO-APIC-fasteoi acpi
0xe: 8195 0 IO-APIC-edge ide0
0xf: 0 0 IO-APIC-edge ide1
0x10: 36 0 IO-APIC-fasteoi uhci_hcd:usb5
0x11: 10645 0 IO-APIC-fasteoi ath
0x12: 42 0 IO-APIC-fasteoi uhci_hcd:usb4
0x17: 919 0 IO-APIC-fasteoi ehci_hcd:usb1, uhci_hcd:usb2
0x13: 32885 0 IO-APIC-fasteoi uhci_hcd:usb3,
ata_piix, ohci1394
0x200100: 1 0 PCI-MSI-edge eth0
0x16: 223 0 IO-APIC-fasteoi HDA Intel
NMI: 0 0 Non-maskable interrupts
LOC: 78087 95718 Local timer interrupts
RES: 11576 16384 Rescheduling interrupts
CAL: 6862 8889 Function call interrupts
TLB: 54 41 TLB shootdowns
TRM: 0 0 Thermal event interrupts
THR: 0 0 Threshold APIC interrupts
SPU: 0 0 Spurious interrupts
ERR: 0


>
> and also please do not cross post to all these lists, just use
> linux-wireless or ath9k.
>

Sorry, but in the past I've posted to linux-wireless, ath9k-devel, and
all the maintainers of ath9k and didn't get a single response (except
a 'me too' from a fellow ath9k user). I didn't just want to hear
crickets this time.

- Steven
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/