From: Uwe Wojak <uwe.wojak@gmx.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Atheros 9390 and AR_INTR_SYNC_HOST1_PERR
Date: Wed, 07 Dec 2011 15:17:41 +0100 [thread overview]
Message-ID: <4EDF7585.3000905@gmx.de> (raw)
In-Reply-To: <CAD2nsn2U9BzgMELpkynYpLn7UYLCkPhAb_ZGxFMw28SpcqtqmA@mail.gmail.com>
Am 07.12.2011 13:44, schrieb Mohammed Shafi:
> On Wed, Dec 7, 2011 at 5:29 PM, Mohammed Shafi<shafi.wireless@gmail.com> wrote:
>> On Wed, Dec 7, 2011 at 5:14 PM, Mohammed Shafi<shafi.wireless@gmail.com> wrote:
>>> On Wed, Dec 7, 2011 at 4:36 PM, Uwe Wojak<uwe.wojak@gmx.de> wrote:
>>>> Hallo,
>>>>
>>>> we use a mini PCIe card (9390) with a miniPCe to PCIe adapter on a X86
>>>> system and a system with a Xilinix Microblaze CPU.
>>>> As the performance on the Microblaze is bad (ping times up to 10 sec),
>>>> we examined the interrupt service routine.
>>>>
>>>> On Microblaze *and* on X86 we see about 10 "spurious" interrupts per
>>>> second.
>>>> In this cases in ar9003_hw_get_isr (ar9003_mac.c) the sync_cause bit
>>>> "AR_INTR_SYNC_HOST1_PERR" is set.
>>>> The driver ignores this.
> please try with the attached patch in latest compat wireless and see if it helps
>
>
Hallo Mohammed,
thank you for your patch. After applying it the chip is reset when the error occurs (i added debug output),
but the error still appears about 10 times a second.
Do you know what "AR_INTR_SYNC_HOST1_PERR" means ?
I feel that there is something wrong with our miniPCIe Adapters or with the network card
(but i see the effect on two different ones from different vendors).
May there be some chip setup missing for 9390 ?
Thank you for your help
Uwe
next prev parent reply other threads:[~2011-12-07 14:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 11:06 [ath9k-devel] Atheros 9390 and AR_INTR_SYNC_HOST1_PERR Uwe Wojak
2011-12-07 11:44 ` Mohammed Shafi
2011-12-07 11:59 ` Mohammed Shafi
2011-12-07 12:44 ` Mohammed Shafi
2011-12-07 14:17 ` Uwe Wojak [this message]
2011-12-08 6:43 ` Mohammed Shafi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EDF7585.3000905@gmx.de \
--to=uwe.wojak@gmx.de \
--cc=ath9k-devel@lists.ath9k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.