Bug 2386262 - [AMD Ryzen AI 370] Wi-Fi (AX210) fails to resume from suspend with D3cold power state error
Summary: [AMD Ryzen AI 370] Wi-Fi (AX210) fails to resume from suspend with D3cold pow...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 42
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-08-04 10:38 UTC by Tom Inglis
Modified: 2025-08-04 10:41 UTC (History)
13 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Tom Inglis 2025-08-04 10:38:21 UTC
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

Comment 1 Tom Inglis 2025-08-04 10:41:45 UTC
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


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