This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

WL127X Producing Errors: wl12xx: "ERROR exceeded max RX BA sessions"

Prodigy 20 points

Replies: 3

Views: 1544

I'm running a device using a TiWi5 (WL1273L) with R5_SP7_01 drivers and 6.3.10.0.139 firmware.

When I operate the device in some locations, after authenticating with an AP, the device sometimes produces the following errors, every 3 seconds or so, even when the device is mostly idle:

 
wl12xx: ERROR exceeded max RX BA sessions

 
Because it happens some places and not others, I strongly believe it's triggered by the nature of the WiFi traffic in the area.  When it happens, it happens on multiple devices.

 
I don't seem to be losing any data, but the constant logging and underlying cause are a concern.
 
Do you have any suggestions?

 
I could simply try increasing RX_BA_MAX_SESSIONS in acx.h, but I'm worried the current value (3) needs to match the supported sessions in the firmware/chip.
 

I'd appreciate any help you can offer.  This is a fairly urgent issue for us.

3 Replies

  • Hi,

    You are right. The WL127x firmware supports max of 3 BA sessions. It cannot be increased.
    I think the problem here is the peer trying to initiate a 4th BA session (ADDBA request).

    It seems to me that the wl1271L is rejecting the request, but the peer keeps sending the request.

    Can you tell me what scenario you are trying? Which AP? Does this happen if you switch the AP? Can you share a sniffer log?

    Regards,
    Gigi Joseph.

  • In reply to Joseph Gigi:

    Joseph -

    Thank you for your quick reply.

    I'm at a site with multiple Aruba commercial APs.  I don't know the exact model, but I can find out.

    - When I was at the site 2 days ago, I tried connecting multiple device to at least 4 different Aruba APs.  All devices and connections produced the same error.

    - When I was at the same site 10 days ago, I didn't see this error at all, connecting to the same Aruba APs.

    - I also don't see the error connecting with APs at my office.

    I don't have any sniffer logs right now, but can gather some when I go back to the site next week.

    What's likely to happen if I just operate with this error?  (I might change the driver to reduce the logging frequency.)

    Regards,

    - Jeff

  • In reply to Jeffrey Wolinsky:

    Hi Jeff,

    You can just ignore this error, or better, downgrade it to a "DEBUG" message...

    Regards,
    Gigi Joseph.

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.