Redpine: firmware assert upon assoc timeout

Bug #1804360 reported by Siva Rebbagondla on 2018-11-21
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Medium
Unassigned
Xenial
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_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.

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.

Changed in linux (Ubuntu):
status: New → Incomplete
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
Brad Figg (brad-figg) wrote :

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: verification-needed-xenial
tags: added: verification-done-xenial
removed: verification-needed-xenial
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux - 4.4.0-141.167

---------------
linux (4.4.0-141.167) xenial; urgency=medium

  * linux: 4.4.0-141.167 -proposed tracker (LP: #1806569)

  * Redpine: firmware assert upon assoc timeout (LP: #1804360)
    - SAUCE: Redpine: fix for firmware assert upon assoc timeout

  * CVE-2018-12896
    - posix-timers: Sanitize overrun handling

  * CVE-2017-5753
    - ALSA: opl3: Hardening for potential Spectre v1
    - ALSA: asihpi: Hardening for potential Spectre v1
    - ALSA: hdspm: Hardening for potential Spectre v1
    - ALSA: rme9652: Hardening for potential Spectre v1
    - ALSA: control: Hardening for potential Spectre v1
    - usbip: vhci_sysfs: fix potential Spectre v1
    - libahci: Fix possible Spectre-v1 pmp indexing in ahci_led_store()

  * CVE-2018-18710
    - cdrom: fix improper type cast, which can leat to information leak.

  * CVE-2018-18690
    - xfs: don't fail when converting shortform attr to long form during
      ATTR_REPLACE

  * CVE-2017-18174
    - pinctrl: Add devm_ apis for pinctrl_{register, unregister}
    - pinctrl: amd: Use devm_pinctrl_register() for pinctrl registration

 -- Khalid Elmously <email address hidden> Wed, 05 Dec 2018 06:11:33 +0000

Changed in linux (Ubuntu Xenial):
status: Fix Committed → Fix Released
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers