From: Ben Greear <greearb@candelatech.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: ath10k <ath10k@lists.infradead.org>
Subject: Re: Anyone seeing tx-credits 'hang'?
Date: Mon, 19 Jan 2015 20:34:33 -0800 [thread overview]
Message-ID: <54BDDAD9.4010405@candelatech.com> (raw)
In-Reply-To: <CA+BoTQniiBEYnQYSp4H7yFQPT8sxG4kb3kiHsUB7SniyU_zorA@mail.gmail.com>
Ok, so I think I've mostly got this figured out...at least enough to
work around the problem.
It seems that the firmware and/or NIC hardware stops doing CE interrupts
for the WMI rings (at least). If I force a poll of
the rings, then packets are found and may be processed.
In one case I looked at closely, it seems IRQs went away for around 30 seconds,
and then for no obvious reason IRQs for the rings started being delivered and
processed again. ~20 WMI messages were processed due to polling CE rings in this
interval.
The combination of WMI keep-alive messages sent from host, and
timer to check for timeouts (and do CE polling at higher intervals
when timeout is detected) appears to be enough. I also check
for the IRQ working again and stop the polling at that time.
I plan to clean the firmware changes up and commit them to my
own repo...but it will require host changes to enable the keep-alive
to fully work around this problem. Probably none of this will make
it upstream....
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2015-01-20 4:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 21:24 Anyone seeing tx-credits 'hang'? Ben Greear
2015-01-09 10:34 ` Michal Kazior
2015-01-09 16:55 ` Ben Greear
2015-01-12 8:06 ` Michal Kazior
2015-01-12 16:51 ` Ben Greear
2015-01-13 19:07 ` Ben Greear
2015-01-14 9:45 ` Michal Kazior
2015-01-14 17:57 ` Ben Greear
[not found] ` <54B6D67C.4090006@qca.qualcomm.com>
[not found] ` <54B6DE13.1080609@candelatech.com>
2015-01-15 1:54 ` Peter Oh
2015-01-15 7:48 ` Michal Kazior
2015-01-15 17:17 ` Ben Greear
2015-01-20 4:34 ` Ben Greear [this message]
2015-01-21 7:22 ` Michal Kazior
2015-01-21 15:42 ` Ben Greear
2015-01-22 6:11 ` Michal Kazior
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=54BDDAD9.4010405@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=michal.kazior@tieto.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox