From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Stuck packet in ath10k
Date: Tue, 18 Mar 2014 15:20:24 -0700 [thread overview]
Message-ID: <5328C6A8.5000002@candelatech.com> (raw)
I've been debugging tx flush issues in ath10k. It seems that
quite often a packet is not flushed within the 3-second timeout,
but sometimes it may be flushed later if one is patient.
I printed out one of the packets in hex, but it does not appear to
have any data, and I'm getting confused trying to decode it by hand.
(Would be lovely if wireshark would let one type in a packet in hex
and then decode it!)
48 01 00 00 # ??
04 f0 21 03 38 99 # Addr of AP
00 f0 21 0e 02 fe # Addr of sending station
04 f0 21 03 38 99 # Addr of AP
00 11 # Seq number?
Anyone know what this packet is and/or have an idea why it would take
a long time to be dealt with by the firmware?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
reply other threads:[~2014-03-18 22:20 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=5328C6A8.5000002@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).