Networking fails and long boot times after waking from sleep with 6.19.x (AI 7 350), perfectly okay with 6.18.13

Framework Laptop 13 Linux
1

Which Linux distro are you using?

  • Fedora 42 KDE Plasma

Which kernel are you using?

  • 6.19.x causes issues.
  • Currently running 6.18.13. No problems.

Which BIOS version are you using?

  • 3.05

Which Framework Laptop 13 model are you using?

  • Ryzen 7 AI 350

After updating kernel to 6.19.x, my machine started to take ~10 seconds to wake from sleep and would lose network functionality. No WiFi, no BT.

At the time, I had an AX200 as my network card. I replaced the AX200 with an AX210 hoping that would fix things. Unfortunately, when running a new kernel and an AX210, the screen would never display anything no matter how long I waited after opening the lid.

A warm boot (restart/reboot) did not restore network functionality, only cold boots from shutdown would bring WiFi back.

I have unsuccessfully tried:

  • modprobe iwlwifi and modprobe -r, does nothing
  • systemctl restart NetworkManager, does nothing
  • tried disabling WiFi powersaving via /etc/modprobe.d/iwlwifi.conf, does nothing useful
  • appending pcie_aspm=off, pcie_port_pm=off, mem_sleep_default=deep, iwlwifi.power_save=0, and iwlwifi.d0i3_disable=1 to GRUB_CMDLINE_LINUX in /etc/default/grub, didn’t help, reverted

I’ve since re-downloaded 6.18.13 and it has behaved exactly as it should with both the AX200 and AX210. (Open lid, log in, wait a second or two for WiFi to reconnect, done.) I understand holding on an old kernel in Fedora isn’t best practice, but it’s the only way I can keep using my 13 daily for now.

Logs below:

Mar 16 13:12:47 fw-13 NetworkManager[1318]: [1773619967.6284] agent-manager: agent[75c05075d806819c,:1.86/org.kde.plasma.networkmanagement/1000]: agent registered
Mar 16 13:12:48 fw-13 NetworkManager[1318]: [1773619968.2566] audit: op=“statistics” interface=“wlp192s0” ifindex=2 args=“500” pid=3312 uid=1000 result=“success”
Mar 16 13:13:10 fw-13 NetworkManager[1318]: [1773619990.8600] manager: sleep: sleep requested (sleeping: no enabled: yes)
Mar 16 13:13:10 fw-13 NetworkManager[1318]: [1773619990.8604] device (wlp192s0): state change: unavailable → unmanaged (reason ‘unmanaged-sleeping’, managed-type: ‘full’)
Mar 16 13:13:10 fw-13 NetworkManager[1318]: [1773619990.8921] manager: NetworkManager state is now ASLEEP
Mar 16 13:16:27 fw-13 NetworkManager[1318]: [1773620187.6874] manager: sleep: wake requested (sleeping: yes enabled: yes)
Mar 16 13:16:27 fw-13 NetworkManager[1318]: [1773620187.6878] device (wlp192s0): state change: unmanaged → unavailable (reason ‘managed’, managed-type: ‘external’)
Mar 16 13:16:27 fw-13 NetworkManager[1318]: [1773620187.6885] platform-linux: do-change-link[2]: failure 1 (Operation not permitted)
Mar 16 13:16:27 fw-13 NetworkManager[1318]: [1773620187.6891] manager: NetworkManager state is now CONNECTED_LOCAL

[OZH@fw-13]~% lspci | grep -i network
c0:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)
[OZH@fw-13]~% echo 1 | sudo tee /sys/bus/pci/devices/0000:c0:00.0/reset
1
tee: ‘/sys/bus/pci/devices/0000:c0:00.0/reset’: Inappropriate ioctl for device
[OZH@fw-13]~%

[OZH@fw-13]~% uname -r
6.19.8-100.fc42.x86_64
[OZH@fw-13]~% dmesg | grep iwlwifi
dmesg: read kernel buffer failed: Operation not permitted
[OZH@fw-13]~% sudo dmesg | grep iwlwifi
[ 6.035435] iwlwifi 0000:c0:00.0: enabling device (0000 → 0002)
[ 6.047305] iwlwifi 0000:c0:00.0: Detected crf-id 0x3617, cnv-id 0x100530 wfpm id 0x80000000
[ 6.047340] iwlwifi 0000:c0:00.0: PCI dev 2723/0080, rev=0x340, rfid=0x10a100
[ 6.047342] iwlwifi 0000:c0:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz
[ 6.075938] iwlwifi 0000:c0:00.0: loaded firmware version 77.f39cc7f9.0 cc-a0-77.ucode op_mode iwlmvm
[ 6.416273] iwlwifi 0000:c0:00.0: Detected RF HR B3, rfid=0x10a100
[ 6.490961] iwlwifi 0000:c0:00.0: base HW address: 60:f2:62:3d:ba:44
[ 6.517515] iwlwifi 0000:c0:00.0 wlp192s0: renamed from wlan0
[ 65.336517] WARNING: drivers/net/wireless/intel/iwlwifi/pcie/gen1_2/trans.c:2387 at __iwl_trans_pcie_grab_nic_access+0xf1/0x150 [iwlwifi], CPU#4: kworker/u64:44/4353
[ 65.336606] snd_hda_codec_hdmi intel_rapl_common snd_soc_core snd_hda_intel snd_compress mac80211 snd_hda_codec ac97_bus edac_mce_amd uvcvideo snd_pcm_dmaengine snd_hda_core snd_rpl_pci_acp6x uvc kvm_amd snd_intel_dspcfg btusb libarc4 snd_acp_pci videobuf2_vmalloc snd_intel_sdw_acpi btmtk snd_amd_acpi_mach snd_hwdep videobuf2_memops leds_cros_ec kvm snd_acp_legacy_common videobuf2_v4l2 btrtl snd_seq iwlwifi cros_kbd_led_backlight cros_ec_sysfs hid_sensor_als led_class_multicolor cros_ec_chardev gpio_cros_ec cros_charge_control cros_ec_hwmon snd_pci_acp6x videobuf2_common btbcm snd_seq_device hid_sensor_trigger snd_pci_acp5x btintel hid_sensor_iio_common snd_pcm amd_pmf irqbypass cros_ec_dev snd_rn_pci_acp3x industrialio_triggered_buffer snd_timer videodev cfg80211 bluetooth amdtee rapl spd5118 kfifo_buf snd_acp_config snd industrialio mc cros_ec_lpcs i2c_piix4 pcspkr snd_soc_acpi wmi_bmof k10temp amd_sfh cros_ec soundcore rfkill snd_pci_acp3x i2c_smbus tee cros_ec_proto amd_pmc platform_profile joydev loop nfnetlink
[ 65.336706] RIP: 0010:__iwl_trans_pcie_grab_nic_access+0xf7/0x150 [iwlwifi]
[ 65.336745] iwl_trans_pcie_grab_nic_access+0x1f/0x50 [iwlwifi]
[ 65.336756] iwl_write_prph_delay+0x1f/0x60 [iwlwifi]
[ 65.336768] iwl_pcie_rx_stop+0x2f/0xc0 [iwlwifi]
[ 65.336782] iwl_trans_pcie_gen2_stop_device+0x357/0x370 [iwlwifi]
[ 65.336801] iwl_trans_stop_device+0x3e/0xd0 [iwlwifi]
[ 65.336817] ? iwl_fw_dbg_stop_sync+0x25/0x50 [iwlwifi]
[ 65.336859] _iwl_pci_resume.isra.0+0x9f/0x1d0 [iwlwifi]
[ 65.336876] iwl_pci_resume+0x10/0x20 [iwlwifi]
[ 65.336942] iwlwifi 0000:c0:00.0: iwlwifi transaction failed, dumping registers
[ 65.336944] iwlwifi 0000:c0:00.0: iwlwifi device config registers:
[ 65.336946] iwlwifi 0000:c0:00.0: Read failed at 0x0
[ 67.148587] iwlwifi 0000:c0:00.0: Error, can not clear persistence bit
[ 67.148739] snd_hda_codec_hdmi intel_rapl_common snd_soc_core snd_hda_intel snd_compress mac80211 snd_hda_codec ac97_bus edac_mce_amd uvcvideo snd_pcm_dmaengine snd_hda_core snd_rpl_pci_acp6x uvc kvm_amd snd_intel_dspcfg btusb libarc4 snd_acp_pci videobuf2_vmalloc snd_intel_sdw_acpi btmtk snd_amd_acpi_mach snd_hwdep videobuf2_memops leds_cros_ec kvm snd_acp_legacy_common videobuf2_v4l2 btrtl snd_seq iwlwifi cros_kbd_led_backlight cros_ec_sysfs hid_sensor_als led_class_multicolor cros_ec_chardev gpio_cros_ec cros_charge_control cros_ec_hwmon snd_pci_acp6x videobuf2_common btbcm snd_seq_device hid_sensor_trigger snd_pci_acp5x btintel hid_sensor_iio_common snd_pcm amd_pmf irqbypass cros_ec_dev snd_rn_pci_acp3x industrialio_triggered_buffer snd_timer videodev cfg80211 bluetooth amdtee rapl spd5118 kfifo_buf snd_acp_config snd industrialio mc cros_ec_lpcs i2c_piix4 pcspkr snd_soc_acpi wmi_bmof k10temp amd_sfh cros_ec soundcore rfkill snd_pci_acp3x i2c_smbus tee cros_ec_proto amd_pmc platform_profile joydev loop nfnetlink
[ 67.149330] snd_hda_codec_hdmi intel_rapl_common snd_soc_core snd_hda_intel snd_compress mac80211 snd_hda_codec ac97_bus edac_mce_amd uvcvideo snd_pcm_dmaengine snd_hda_core snd_rpl_pci_acp6x uvc kvm_amd snd_intel_dspcfg btusb libarc4 snd_acp_pci videobuf2_vmalloc snd_intel_sdw_acpi btmtk snd_amd_acpi_mach snd_hwdep videobuf2_memops leds_cros_ec kvm snd_acp_legacy_common videobuf2_v4l2 btrtl snd_seq iwlwifi cros_kbd_led_backlight cros_ec_sysfs hid_sensor_als led_class_multicolor cros_ec_chardev gpio_cros_ec cros_charge_control cros_ec_hwmon snd_pci_acp6x videobuf2_common btbcm snd_seq_device hid_sensor_trigger snd_pci_acp5x btintel hid_sensor_iio_common snd_pcm amd_pmf irqbypass cros_ec_dev snd_rn_pci_acp3x industrialio_triggered_buffer snd_timer videodev cfg80211 bluetooth amdtee rapl spd5118 kfifo_buf snd_acp_config snd industrialio mc cros_ec_lpcs i2c_piix4 pcspkr snd_soc_acpi wmi_bmof k10temp amd_sfh cros_ec soundcore rfkill snd_pci_acp3x i2c_smbus tee cros_ec_proto amd_pmc platform_profile joydev loop nfnetlink
[ 67.176532] iwlwifi 0000:c0:00.0: Error, can not clear persistence bit
[ 67.180930] iwlwifi 0000:c0:00.0: Error, can not clear persistence bit
[ 67.181295] iwlwifi 0000:c0:00.0: Error, can not clear persistence bit
[ 77.790582] iwlwifi 0000:c0:00.0: Error, can not clear persistence bit
[ 77.790911] iwlwifi 0000:c0:00.0: Error, can not clear persistence bit
[ 83.149993] iwlwifi 0000:c0:00.0: Error, can not clear persistence bit
[ 83.150321] iwlwifi 0000:c0:00.0: Error, can not clear persistence bit
[ 83.158237] iwlwifi 0000:c0:00.0: Error, can not clear persistence bit
[ 83.158540] iwlwifi 0000:c0:00.0: Error, can not clear persistence bit
[ 93.791060] iwlwifi 0000:c0:00.0: Error, can not clear persistence bit
[ 93.791359] iwlwifi 0000:c0:00.0: Error, can not clear persistence bit
[ 103.790547] iwlwifi 0000:c0:00.0: Error, can not clear persistence bit
[ 103.790794] iwlwifi 0000:c0:00.0: Error, can not clear persistence bit
[ 113.790739] iwlwifi 0000:c0:00.0: Error, can not clear persistence bit
[ 113.790922] iwlwifi 0000:c0:00.0: Error, can not clear persistence bit
[ 123.790417] iwlwifi 0000:c0:00.0: Error, can not clear persistence bit
[ 123.790601] iwlwifi 0000:c0:00.0: Error, can not clear persistence bit
[ 133.790426] iwlwifi 0000:c0:00.0: Error, can not clear persistence bit
[ 133.790647] iwlwifi 0000:c0:00.0: Error, can not clear persistence bit
[OZH@fw-13]~% journalctl -b -1 | grep iwlwifi
Mar 17 18:40:00 fw-13 kernel: iwlwifi 0000:c0:00.0: enabling device (0000 → 0002)
Mar 17 18:40:00 fw-13 kernel: iwlwifi 0000:c0:00.0: Detected crf-id 0x400410, cnv-id 0x400410 wfpm id 0x80000000
Mar 17 18:40:00 fw-13 kernel: iwlwifi 0000:c0:00.0: PCI dev 2725/0024, rev=0x420, rfid=0x10d000
Mar 17 18:40:00 fw-13 kernel: iwlwifi 0000:c0:00.0: Detected Intel(R) Wi-Fi 6E AX210 160MHz
Mar 17 18:40:00 fw-13 kernel: iwlwifi 0000:c0:00.0: loaded firmware version 89.123cf747.0 ty-a0-gf-a0-89.ucode op_mode iwlmvm
Mar 17 18:40:00 fw-13 kernel: iwlwifi 0000:c0:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20
Mar 17 18:40:00 fw-13 kernel: iwlwifi 0000:c0:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
Mar 17 18:40:00 fw-13 kernel: iwlwifi 0000:c0:00.0: WFPM_AUTH_KEY_0: 0x90
Mar 17 18:40:00 fw-13 kernel: iwlwifi 0000:c0:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0
Mar 17 18:40:00 fw-13 kernel: iwlwifi 0000:c0:00.0: Detected RF GF, rfid=0x10d000
Mar 17 18:40:00 fw-13 kernel: iwlwifi 0000:c0:00.0: base HW address: 40:d1:33:58:28:57
Mar 17 18:40:00 fw-13 kernel: iwlwifi 0000:c0:00.0 wlp192s0: renamed from wlan0
Mar 17 18:40:01 fw-13 NetworkManager[1311]: [1773726001.9655] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:02.3/0000:c0:00.0/ieee80211/phy0/rfkill1) (driver iwlwifi)
Mar 17 18:40:02 fw-13 kernel: iwlwifi 0000:c0:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20
Mar 17 18:40:02 fw-13 kernel: iwlwifi 0000:c0:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
Mar 17 18:40:02 fw-13 kernel: iwlwifi 0000:c0:00.0: WFPM_AUTH_KEY_0: 0x90
Mar 17 18:40:02 fw-13 kernel: iwlwifi 0000:c0:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0
Mar 17 18:40:02 fw-13 kernel: iwlwifi 0000:c0:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20
Mar 17 18:40:02 fw-13 kernel: iwlwifi 0000:c0:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
Mar 17 18:40:02 fw-13 kernel: iwlwifi 0000:c0:00.0: WFPM_AUTH_KEY_0: 0x90
Mar 17 18:40:02 fw-13 kernel: iwlwifi 0000:c0:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0
Mar 17 18:42:24 fw-13 kernel: iwlwifi 0000:c0:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20
Mar 17 18:42:24 fw-13 kernel: iwlwifi 0000:c0:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
Mar 17 18:42:24 fw-13 kernel: iwlwifi 0000:c0:00.0: WFPM_AUTH_KEY_0: 0x90
Mar 17 18:42:24 fw-13 kernel: iwlwifi 0000:c0:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0
Mar 17 18:42:25 fw-13 kernel: iwlwifi 0000:c0:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20
Mar 17 18:42:25 fw-13 kernel: iwlwifi 0000:c0:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
Mar 17 18:42:25 fw-13 kernel: iwlwifi 0000:c0:00.0: WFPM_AUTH_KEY_0: 0x90
Mar 17 18:42:25 fw-13 kernel: iwlwifi 0000:c0:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0

2

I suggest you bisect the kernel to figure out what caused this and then report your results. Otherwise the iwlwifi driver maintainers might have no indication there is such an issue.

3

A strange development has prevented me from bisecting the kernel, now seemingly all kernels, including my previously safe 6.18.13 have started exhibiting my issues. Even a Timeshift restore to before I started bisecting doesn’t fix the issue.

I’m at a loss, to be honest.

4

linux-firmware regression perhaps?

5

Definitely seems like it but I currently can’t put the work into finding the commit where it started/collecting evidence as it will compromise my studies. I’ve been able to restore 6.18.13 functionality now by reinstalling the kernel and appending all the stuff to GRUB_CMDLINE_LINUX. I was apparently wrong before about that not doing anything.

What else can I collect to help the linux-firmware maintainers fix the issue?

I’ve also been thinking about fresh installing Fedora 43 onto my system, since I can’t get the 42 to 43 upgrade working anyway. That’s got a chance of fixing it right?

6

You should be able to look at your package install history and see if the problems started when you had an upgrade to the firmware package. If so - you will know the specific firmware package to roll back and check.