Bug 2180027 - System wakes up immediately after suspend
Summary: System wakes up immediately after suspend
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: linux-firmware
Version: 37
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: David Woodhouse
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-20 15:11 UTC by Vlad
Modified: 2024-01-12 23:16 UTC (History)
8 users (show)

Fixed In Version: linux-firmware-20230404-149.fc38 linux-firmware-20230404-149.fc37
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-01-12 23:16:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Linux Kernel 217239 0 P1 ASSIGNED ath11k: WCN6855: firmware update breaks suspend 2023-08-06 15:04:10 UTC

Description Vlad 2023-03-20 15:11:52 UTC
I am using Fedora Silverblue.
After update system wakes up immediately after suspend if NetworkManager.service is working. Turning off NetworkManager.service or turning on airplane mode before suspend fixes the issue, but it worked fine before the update.

Updated packages:
amd-gpu-firmware 20230210-147.fc37 -> 20230310-148.fc37
intel-gpu-firmware 20230210-147.fc37 -> 20230310-148.fc37
iwl100-firmware 39.31.5.1-147.fc37 -> 39.31.5.1-148.fc37
iwl1000-firmware 1:39.31.5.1-147.fc37 -> 1:39.31.5.1-148.fc37
iwl105-firmware 18.168.6.1-147.fc37 -> 18.168.6.1-148.fc37
iwl135-firmware 18.168.6.1-147.fc37 -> 18.168.6.1-148.fc37
iwl2000-firmware 18.168.6.1-147.fc37 -> 18.168.6.1-148.fc37
iwl2030-firmware 18.168.6.1-147.fc37 -> 18.168.6.1-148.fc37
iwl3160-firmware 1:25.30.13.0-147.fc37 -> 1:25.30.13.0-148.fc37
iwl3945-firmware 15.32.2.9-147.fc37 -> 15.32.2.9-148.fc37
iwl4965-firmware 228.61.2.24-147.fc37 -> 228.61.2.24-148.fc37
iwl5000-firmware 8.83.5.1_1-147.fc37 -> 8.83.5.1_1-148.fc37
iwl5150-firmware 8.24.2.2-147.fc37 -> 8.24.2.2-148.fc37
iwl6000-firmware 9.221.4.1-147.fc37 -> 9.221.4.1-148.fc37
iwl6000g2a-firmware 18.168.6.1-147.fc37 -> 18.168.6.1-148.fc37
iwl6000g2b-firmware 18.168.6.1-147.fc37 -> 18.168.6.1-148.fc37
iwl6050-firmware 41.28.5.1-147.fc37 -> 41.28.5.1-148.fc37
iwl7260-firmware 1:25.30.13.0-147.fc37 -> 1:25.30.13.0-148.fc37
iwlax2xx-firmware 20230210-147.fc37 -> 20230310-148.fc37
libertas-usb8388-firmware 2:20230210-147.fc37 -> 2:20230310-148.fc37
linux-firmware 20230210-147.fc37 -> 20230310-148.fc37
linux-firmware-whence 20230210-147.fc37 -> 20230310-148.fc37
nvidia-gpu-firmware 20230210-147.fc37 -> 20230310-148.fc37
webp-pixbuf-loader 0.2.1-1.fc37 -> 0.2.2-1.fc37

Additional info:
Laptop: HONOR MagicBook 15
APU: Ryzen 5500U
Wifi adapter: Qualcomm QCNFA765 Wireless Network Adapter
Kernel: 6.1.18-200.fc37.x86_64

Bug present on both: Fedora 37 and 38.

Comment 1 Vlad 2023-03-24 09:39:43 UTC
Problem seems to be with ath11k_pci driver. Unloading it with modprobe -r ath11k_pci before suspend let system successfully suspend.

Comment 2 Fedora Update System 2023-04-19 09:44:47 UTC
FEDORA-2023-ffeecefff7 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-ffeecefff7

Comment 3 Fedora Update System 2023-04-19 09:44:53 UTC
FEDORA-2023-1cf0937309 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-1cf0937309

Comment 4 Fedora Update System 2023-04-19 09:44:58 UTC
FEDORA-2023-460849706f has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2023-460849706f

Comment 5 Fedora Update System 2023-04-20 04:29:37 UTC
FEDORA-2023-1cf0937309 has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-1cf0937309`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-1cf0937309

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2023-04-20 05:42:43 UTC
FEDORA-2023-460849706f has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-460849706f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-460849706f

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2023-04-20 06:08:35 UTC
FEDORA-2023-ffeecefff7 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-ffeecefff7`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-ffeecefff7

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2023-04-22 00:48:16 UTC
FEDORA-2023-1cf0937309 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2023-04-22 21:47:42 UTC
FEDORA-2023-ffeecefff7 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Vlad 2023-04-23 10:49:24 UTC
After update same problem still exists. Only works if wifi disabled. I reported this bug couple weeks ago here: https://bugzilla.kernel.org/show_bug.cgi?id=217239 and switching driver to a previous version worked. But problem seems to be persist for now.

Comment 11 Vlad 2023-04-23 12:42:01 UTC
I checked it is still the same version of firmware with regression: WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.23
It wasn't changed, so bug is still present.
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.23 is working version.

Comment 12 Vlad 2023-04-23 12:44:53 UTC
> I checked it is still the same version of firmware with regression:
> WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.23
> It wasn't changed, so bug is still present.
> WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.23 is working
> version.

Sorry, WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.16 is working version not 23.

Comment 13 Aoife Moloney 2023-11-23 01:31:29 UTC
This message is a reminder that Fedora Linux 37 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '37'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 37 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 14 Aoife Moloney 2024-01-12 23:16:43 UTC
Fedora Linux 37 entered end-of-life (EOL) status on 2023-12-05.

Fedora Linux 37 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.