[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f488382f0809181325u1a02aa4dp85214c003df45336@mail.gmail.com>
Date: Thu, 18 Sep 2008 13:25:58 -0700
From: "Steven Noonan" <steven@...inklabs.net>
To: "Justin Mattock" <justinmattock@...il.com>
Cc: "Luis R. Rodriguez" <lrodriguez@...eros.com>,
LKML <linux-kernel@...r.kernel.org>,
"Ingo Molnar" <mingo@...e.hu>,
linux-wireless <linux-wireless@...r.kernel.org>,
"ath9k-devel@...ts.ath9k.org" <ath9k-devel@...ts.ath9k.org>
Subject: Re: [ath9k-devel] ath9k: massive unexplained latency in 2.6.27 (rc5, rc6, probably others)
On Thu, Sep 18, 2008 at 1:18 PM, Justin Mattock <justinmattock@...il.com> wrote:
> On Thu, Sep 18, 2008 at 12:23 PM, Steven Noonan <steven@...inklabs.net> wrote:
>> On Thu, Sep 18, 2008 at 12:00 PM, Steven Noonan <steven@...inklabs.net> wrote:
>>> On Thu, Sep 18, 2008 at 11:42 AM, Luis R. Rodriguez
>>> <lrodriguez@...eros.com> 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.
>>
>> I wonder if this is related:
>>
>> alcarin ~ # dmesg | grep GPE
>> [ 0.166806] ACPI: EC: GPE = 0x17, I/O: command/status = 0x66, data = 0x62
>> [ 685.409077] ACPI: EC: GPE storm detected, disabling EC GPE
>
> FWIW, you might want to try this pach
> in this thread:
> http://www.gossamer-threads.com/lists/linux/kernel/966076
> I was receiving a disable irq #23 this patch"knock on wood",
> seems to help with this issue.
>
Both the patches there affect EHCI, though. If I was having a USB
controller fink out with "IRQ X: nobody cared", then that patch would
probably indeed be applicable.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists