* Stuck packet in ath10k
@ 2014-03-18 22:20 Ben Greear
0 siblings, 0 replies; only message in thread
From: Ben Greear @ 2014-03-18 22:20 UTC (permalink / raw)
To: ath10k, linux-wireless@vger.kernel.org
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2014-03-18 22:20 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-03-18 22:20 Stuck packet in ath10k Ben Greear
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).