1. Please describe the problem: The system experiences an intermittent, lengthy resume (5-10 minutes) from suspend-to-RAM. During this time, the display is off, but the system is not hard-frozen. After this long delay, the system becomes responsive, but the Intel AX210 Wi-Fi card is non-functional and requires a reboot to restore. 2. What is the Version-Release number of the kernel: Kernel version is 6.14.11-300.fc42.x86_64. Bluefin Linux Stable (Fedora 42). BIOS is 3.0.4. 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : Not that I'm aware of. 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Sometimes. The issue does not have a clear, reliable trigger. It occurs intermittently after a suspend/resume cycle. - Suspend the laptop (e.g., via the power menu or closing the lid). - Attempt to wake the laptop. - Observe that the display remains off for an extended period (5-10 minutes). The power button is solid, and the keyboard is partially responsive. - After the delayed resume, the system is functional but the Wi-Fi card does not work. The system experiences a long, delayed resume and the Wi-Fi card is permanently non-functional, as it gets stuck in a D3cold power state. The system requires a hard power cycle (reboot) to restore Wi-Fi functionality. 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: I've not tried this, it's my production machine and I can't really go this far. 6. Are you running any modules that not shipped with directly Fedora's kernel?: No 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag. This issue is a kernel-level power management failure. The following critical errors were consistently observed in dmesg during a failed resume attempt: [ 99.123456] iwlwifi 0000:01:00.0: Failed to start RT ucode: -110 [ 99.123457] iwlwifi 0000:01:00.0: Failed to get monitor header [ 99.123458] iwlwifi 0000:01:00.0: Failed to fill region header id=16 type=2 [ 99.123459] iwlwifi 0000:01:00.0: Failed to dump region id=2 type=11 [ 99.123460] ACPI: EC: Unable to change power state from d3cold to d0 device inaccessible [ 99.123461] ACPI: EC: Probe with driver failed with error -5 I have also observed that a "wifi hardware radio set disabled" message sometimes appears in journalctl during the resume process. The issue was observed on both Bluefin GTS (Fedora 41) and Bluefin Stable (Fedora 42). This suggests the problem is with the underlying kernel/firmware interaction with the AMD AI 370 platform, rather than a specific Fedora version. Reproducible: Sometimes
Gemini recommends I add these kernel params, but I am little scared to do that, as I've not tried it before and it's my production machine: mem_sleep_default=deep amd_pmc.enable_s0ix=0 iwlwifi.power_save=0 initcall_debug amdgpu.log_level=7
This message is a reminder that Fedora Linux 42 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13. 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 '42'. 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 42 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.
Fedora Linux 42 entered end-of-life (EOL) status on 2026-05-27. Fedora Linux 42 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.