Re: Frames acknowledged and silently discarded in firmware

On Wed, Mar 14, 2018 at 9:47 AM, Ben Greear wrote: > On 03/13/2018 05:52 PM, Thomas Pedersen wrote: >> >> Javier, >> >> On Tue, Mar 13, 2018 at 4:42 PM, Javier Cardona wrote: >>> >>> Hi, >>> >>> We have resolved this issue. I'm sharing the details in

Re: Frames acknowledged and silently discarded in firmware

On 03/13/2018 05:52 PM, Thomas Pedersen wrote: Javier, On Tue, Mar 13, 2018 at 4:42 PM, Javier Cardona wrote: Hi, We have resolved this issue. I'm sharing the details in case that might help others. The description of the problem was accurate EXCEPT that the acks that we

Re: Frames acknowledged and silently discarded in firmware

Hi Adrian, On 3/13/18, 5:21 PM, "Adrian Chadd" wrote: HI, What were the mac addresses? Why were they so dissimilar? The addresses on the pre-cal files were 12:34:56:78:90:12 We changed them to manufacturer assigned macs. Thanks! Javier -adrian

Re: Frames acknowledged and silently discarded in firmware

Thomas, On 3/13/18, 5:53 PM, "Thomas Pedersen" wrote: Javier, On Tue, Mar 13, 2018 at 4:42 PM, Javier Cardona wrote: > Hi, > > We have resolved this issue. I'm sharing the details in case that might help others. > > The

Re: Frames acknowledged and silently discarded in firmware

Javier, On Tue, Mar 13, 2018 at 4:42 PM, Javier Cardona wrote: > Hi, > > We have resolved this issue. I'm sharing the details in case that might help > others. > > The description of the problem was accurate EXCEPT that the acks that we > observed on the sniffer were not

Re: Frames acknowledged and silently discarded in firmware

HI, What were the mac addresses? Why were they so dissimilar? -adrian ___ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k

Re: Frames acknowledged and silently discarded in firmware

On 03/13/2018 04:42 PM, Javier Cardona wrote: Hi, We have resolved this issue. I'm sharing the details in case that might help others. The description of the problem was accurate EXCEPT that the acks that we observed on the sniffer were not being sent by the failed station (MAP2, in the

Re: Frames acknowledged and silently discarded in firmware

Hi, We have resolved this issue. I'm sharing the details in case that might help others. The description of the problem was accurate EXCEPT that the acks that we observed on the sniffer were not being sent by the failed station (MAP2, in the context of my original e-mail) but by a third

Re: Frames acknowledged and silently discarded in firmware

Hi, Yeah, it's possible it's being dropped in the HTT notification path - the hardware afaik is doing the ACKing there. I think pktlog is the primary way I'd try to debug this but yeah, there's no open pktlog tool iirc for even just looking at the packet data.. -adrian

Re: Frames acknowledged and silently discarded in firmware

Hi Adrian, We do not have access to firmware source, nor to any other QCA proprietary tools at this time. The logs were collected by enabling ATH10K_DBG_DATA in debug_mask. AFICT, those messages are generated inside ath10k_htt_rx_h_deliver(), and the only place where the frames could be

Re: Frames acknowledged and silently discarded in firmware

hi, do you have firmware source at the current gig? or access to the pktlog tools? Have you verified that the frames weren't at all indicated up via HTT? Like are they absolutely NOT coming up via HTT, or are they coming up via HTT but being thrown out before the driver is ready to pass them up.

Frames acknowledged and silently discarded in firmware

Hi, We have observed a problem where, under certain conditions, the ath10k firmware will acknowledge frames but not send them up to the driver. Frames are sent by a mesh access point (MAP1) to a second mesh AP (MAP2) at MCS 9/NSS-3, which at that distance is probably marginal. Since frames