Public bug reported:

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_handler: ==> FIRMWARE Assert <==
   ven_rsi_91x: rsi_interrupt_handler: Firmware Status is 0xa
   IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

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.

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1804360

Title:
   Redpine: firmware assert upon assoc   timeout

Status in linux package in Ubuntu:
  New

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_handler: ==> FIRMWARE Assert <==
     ven_rsi_91x: rsi_interrupt_handler: Firmware Status is 0xa
     IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804360/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to