From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>
Subject: QCA99XX, IBSS, and no transmitted frames?
Date: Tue, 26 Apr 2016 12:34:21 -0700 [thread overview]
Message-ID: <571FC2BD.6080602@candelatech.com> (raw)
Just curious if anyone has any ideas...I've been staring that this one
for days without much luck...
Test case is to bring up two 9990 NICs, using my kernel and firmware, and
then run 56kbps UDP traffic bi-directional.
It works for a bit, and then I see a case where one side cannot seem
to answer ARP. I still see beacons from it, and probe responses,
and I see it receive ARP and try to respond at the netdev level.
But, when sniffing the air, I do not see any ARP response on the air.
I've tried verifying the rate-ctrl logic is right and all of that.
Unless I'm really missing something, this is a firmware issue.
Any suggestions for what might be the issue? Anyone else see problems
where 9990 NICs go selectively silent on transmit?
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
reply other threads:[~2016-04-26 19:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=571FC2BD.6080602@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.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.