Redpine: firmware assert upon assoc timeout
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Medium
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
SRU Justification
-----------------
Impact:
-------
firmware assert upon assoc timeout
Test Case:
----------
1) Bring up the Redpine Module in Coex mode 13.
2) Try to do roaming between two AP's.
3) At some point, When Association timeout happens and station tries to scan and
observed below firmware assert.
wlan0: authenticate with ac:a3:1e:a1:1e:85
wlan0: send auth to ac:a3:1e:a1:1e:85 (try 1/3)
wlan0: authenticated
wlan0: associate with ac:a3:1e:a1:1e:85 (try 1/3)
wlan0: associate with ac:a3:1e:a1:1e:85 (try 2/3)
wlan0: associate with ac:a3:1e:a1:1e:85 (try 3/3)
wlan0: association with ac:a3:1e:a1:1e:85 timed out
ven_rsi_91x: rsi_disable_ps: Cannot accept disable PS in PS_NONE state
ven_rsi_91x: rsi_interrupt_
ven_rsi_91x: rsi_interrupt_
IPv6: ADDRCONF(
RCA:
----
Root cause: When association starts, driver is sending station add peer
notify to firmware but when Association timeout happens, driver is not
sending station peer delete to Firmware. Hence, FW is going into DEEP SLEEP
in associated state, which is incorrect.
Fix:
----
Sending station delete peer notify when assoc timeout happens.
Regression potential:
-------
Ran roaming between two AP's for 20 hours and didn't see the issue.
This bug is for tracking purposes only, please don't triage.
CVE References
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
status: | Incomplete → Triaged |
Changed in linux (Ubuntu Xenial): | |
status: | New → In Progress |
Changed in linux (Ubuntu): | |
status: | Triaged → Invalid |
Changed in linux (Ubuntu Xenial): | |
status: | In Progress → Fix Committed |
summary: |
- Redpine: firmware assert upon assoc timeout + Redpine: firmware assert upon assoc timeout |
tags: |
added: verification-done-xenial removed: verification-needed-xenial |
tags: | added: cscc |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1804360
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.