search

fedora-silverblue / issue-tracker

Fedora Silverblue issue tracker
https://fedoraproject.org/atomic-desktops/silverblue/
123 stars 3 forks source link

Regression: system wakes up immediately after suspend #435

Closed mrvladus closed 1 year ago

mrvladus commented 1 year ago

After update from commit 73028c7680c7acd755ab315093d379a0e83a56d07e1166d02f5a7478f8b327bf to d0035ee2b86a33c58f07c5e424a96a998aeed98bb1444da5f1769f6ac7f1c14e 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.

Changes between commits:

ostree diff commit from: 73028c7680c7acd755ab315093d379a0e83a56d07e1166d02f5a7478f8b327bf
ostree diff commit to:   d0035ee2b86a33c58f07c5e424a96a998aeed98bb1444da5f1769f6ac7f1c14e
Upgraded:
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

To Reproduce

  1. Upgrade to commit d0035ee2b86a33c58f07c5e424a96a998aeed98bb1444da5f1769f6ac7f1c14e
  2. Try suspend

Expected behavior System goes to sleep

OS version:

BootedDeployment:
● fedora:fedora/37/x86_64/silverblue
                  Version: 37.20230314.0 (2023-03-14T00:43:07Z)
                  Commit: 73028c7680c7acd755ab315093d379a0e83a56d07e1166d02f5a7478f8b327bf
                  GPGSignature: Valid signature by ACB5EE4E831C74BB7C168D27F55AD3FB5323552A

Additional context Laptop: HONOR MagicBook 15 APU: Ryzen 5500U Fedora version: 37 Wifi adapter: Qualcomm QCNFA765 Wireless Network Adapter

miabbott commented 1 year ago

This is unlikely a problem with Silverblue itself and is probably an issue in NetworkManager or linux-firmware (the source of nearly all the updates between the two commits).

Since the linux-firmware package is the one that changed, I would recommend filing a bug with that component with your issue:

https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=linux-firmware

If that ends up not being the root cause, your issue will get routed to the right team.