Hi,
We are working on wl12xx chipset.
we experience issues in the areas with poor WiFi coverage.
In these cases we get the following log from the driver with subsequent firmware reboot.
We have a number of questions:
1. Is it the expected behavior of the driver/firmware?
2. What can prevent driver from reboot in case longer timeout won’t help?
[12132.165344] wl1271: ERROR ELP wakeup timeout!
[12132.170074] wl1271: Reading FW panic log
[12132.680480] wl1271: ERROR ELP wakeup timeout!
[12132.687286] First address of fwlogger = 0x2603
[12132.693786] wl1271: Hardware recovery in progress. FW ver: Rev 6.3.3.0.79 pc: 0x0
[12132.701721] wl1271: down
[12132.708038] Powering off wl12xx
[12132.711273] ieee80211 phy0: Hardware restart was requested
[12132.743408] Powering on wl12xx
[12133.613250] wl1271: firmware booted (Rev 6.3.3.0.79)
[12133.618743] wl1271: Driver version: R4_SP2_02_03
[12133.672790] wl1271: Association completed.
[12133.680328] wl1271: ERROR no active RX BA session on tid: 0
[12133.686248] HW problem - can not stop rx aggregation for tid 0
Thanks,
Devang