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 <khalid.elmou...@canonical.com> Wed, 05 Dec 2018
06:11:33 +0000
--
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:
Invalid
Status in linux source package in Xenial:
Fix Released
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
