Reopening for Jammy as the bug is not really fixed but the previous
commits reverted and the bot apparently looks at the bug references in
the changes file.
** Changed in: linux-firmware (Ubuntu Jammy)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2048977
Title:
WCN6856 Wi-FI Unavailable and no function during suspend stress
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-firmware source package in Jammy:
Triaged
Status in linux-firmware source package in Lunar:
Won't Fix
Status in linux-firmware source package in Mantic:
Fix Committed
Status in linux-firmware source package in Noble:
In Progress
Bug description:
[SRU Justification]
[Impact]
Due to a known silicon limitation, the following sequence is needed while
initialing the PCIE device on a certain devices with ASMedia chipset involved:
1. 'hot reset' assert
2. 2nd PCIe reset' assert
3. Asmedia 'hot reset' deassert
4. PT21 GPIO13 2nd PCIe reset' deassert.
In certain caes, the WIFI link training failed while system resumes from
suspend.
[Fix]
Upstream commits:
* 17509e53b97b ("ath11k: WCN6855 hw2.0: update to
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36")
* 324cc56975d7 ("ath11k: WCN6855 hw2.0: update board-2.bin")
And Jammy takes an additional commit d1dc30480fef ("ath11k: WCN6855 hw2.0:
update board-2.bin") to forfill git history dependency.
And while we pulled a firmware fix from github.com/kvalo/ath11k-firmware in
bug 2042534, it fails to clean cherry-pick of commit 17509e53b97b. Since Noble
has not yet accept the PR for bug 2042534, it has no such problem at this
moment.
[Test Case]
This can be reproduced with suspend/resume stress test.
$ checkbox-cli run com.canonical.certification::stress-
suspend-30-cycles-with-reboots-automated
[Where problems could occur]
Opaque firmware update. No known issue found yet after the update.
[Other Info]
This affects all series with WCN6855/WCN6856 support, Noble/Mantic/Lunar and
Jammy for oem-6.5 included.
========== original bug report ==========
Due to a known silicon limitation, the following sequence is needed
while initialing the PCIE device on a certain devices with ASMedia
chipset involved:
1. 'hot reset' assert
2. 2nd PCIe reset' assert
3. Asmedia 'hot reset' deassert
4. PT21 GPIO13 2nd PCIe reset' deassert.
In certain caes, the WIFI link training failed while system resumes
from suspend.
This can be reproduced with suspend/resume stress test.
$ checkbox-cli run com.canonical.certification::stress-
suspend-30-cycles-with-reboots-automated
The proposed fixes are:
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=17509e53b97baaefeb287b98d3358da8a6e1c199
- This FW include this LP ticket issue fix
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=324cc56975d7b5a375259a49667c24f2f5a4c8fe
- The FW is to support new China regulatory support.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2048977/+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
