esp-idf: AP mode, got error wifi: ampdu: ignore deleting tx BA0
Environment
- Development Kit: [ESP32-PICO-D4]
- Kit version: self made
- Module or chip used: [ESP32-PICO-D4|ESP32]
- IDF version: v4.0-dev-1346-g1b6010b
- Build System: [idf.py]
- Compiler version (run
xtensa-esp32-elf-gcc --versionto find it): xtensa-esp32-elf-gcc (crosstool-NG esp32-2019r1) 8.2.0 - Operating System: [Linux-ubuntu16.04]
- Power Supply: [Battery->dc-dc->3.3v]
Problem Description
I got losts of error like this: I (614270) wifi: ampdu: ignore deleting tx BA0 I (614270) wifi: ampdu: ignore deleting tx BA0 I (614270) wifi: ampdu: ignore deleting tx BA0 I (615270) wifi: ampdu: ignore deleting tx BA0
Hello, I am using a PICO D4, and trying the example of AP mode. So far, I don’t have the problem in sta mode. When this error comes up, the data transfering is impossible. This problem is random. Most of the time, ESP32 works well.
Someone else have the same problem. https://www.esp32.com/viewtopic.php?f=13&t=10839&p=44403&hilit=wifi%3A+ampdu%3A+ignore+deleting+tx+BA0&sid=4bb8f22bbe5efb2d3911586f0131c3e6#p44403
re-produce the error:
- example: softap
- combine another example http server
- make some “post” or “get” data transfer, or just reflesh the home page you set for http server , ESP32 should work well. Wait a few mintues, the error may come up.
I guess, this is not about my code, it is about driver or hardware, or wrong config in Kconfig. But I am not sure what is wrong, and how to fix it.
Thank you, any suggestion will be appreciated
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 15 (1 by maintainers)
@gabrielrbeiro the fix now is in reviewing status, it will be merged into IDF this month.
We are debugging the
delete tx BAissue recently , and we will solve it as soon as possible.The current implementation of AMPDU in the ESP32 seems to be wrong as it causes problems with some network adapters. Using UDP over AP causes massive packet drops and TCP over AP causes packet looses and socket timeouts.
I solved this issue disabling AMPDU on the sdkconfig.h as a workaround: