[TRACKING] Kernel regression: WiFi-related hangs, fails to suspend with kernel 6.6.5 - fixed in 6.6.6

[dimitris]

@Dave_Chalk

I’m experiencing wifi hang on 6.5.6 and 6.6.6

Can you confirm that you’re running 6.6.6 or later? uname -r

Because F39 seems to have an (installation-time?) bug whereby the configuration is not bootstrapped to turn on “when installing kernel version make it the default”

See thread right about here:

Fedora 39 on the Framework Laptop 13

I wish I could say this worked for me, but unfortunately GRUB still seems to be defaulting to the oldest kernel for me. $ rpm -qa kernel kernel-6.5.6-300.fc39.x86_64 kernel-6.6.4-200.fc39.x86_64 kernel-6.6.6-200.fc39.x86_64 $ uname -r 6.5.6-300.fc39.x86_64 $ cat /etc/default/grub GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR=“$(sed ‘s, release .*$,g’ /etc/system-release)” GRUB_SAVEDEFAULT=true GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true GRUB_TERMINAL_OUTPUT=“console” GRUB_CMDLINE_LINUX=“r…

If you’re hitting that issue, after fixing/creating the config file referenced there, you can either reinstall 6.6.6

sudo dnf reinstall kernel{,-core,-modules,-modules-core,-modules-extra}-6.6.6

or go for 6.6.7 which is already looking good in updates-testing

sudo dnf --enablerepo updates-testing --refresh --setopt=fastestmirror=true up 'kernel*'

To trigger the make-default logic.

[dimitris]

@Dave_Chalk

the hang remains

Just to be clear, what is the symptom of the hang, other than the logs?

NetworkManager-dispatcher and packagekit are also exiting successfully here. As far as nm-d goes, that’s how I always remember it, it’s used on network changes IIRC. I never paid much attention to packagekit in the logs. It’s normal for some systemd units to run just once, or periodically, or on some other trigger, they’re not all “classic” daemons.

$ systemctl status NetworkManager-dispatcher.service 
○ NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager-dispatcher.service; enabled; preset: enabled)
...
Dec 17 19:03:49 angua systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service.
Dec 17 19:04:03 angua systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.

$ systemctl status packagekit.service 
○ packagekit.service - PackageKit Daemon
     Loaded: loaded (/usr/lib/systemd/system/packagekit.service; static)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: inactive (dead)

Dec 17 13:21:05 angua systemd[1]: packagekit.service: Deactivated successfully.
Dec 17 19:04:09 angua systemd[1]: Starting packagekit.service - PackageKit Daemon...
Dec 17 19:04:09 angua PackageKit[22717]: daemon start
Dec 17 19:04:09 angua systemd[1]: Started packagekit.service - PackageKit Daemon.
Dec 17 19:04:10 angua PackageKit[22717]: get-updates transaction /5438_ddbabdbc from uid 1000 finished with success after 641ms
Dec 17 19:04:10 angua PackageKit[22717]: get-updates transaction /5439_daaccacb from uid 1000 finished with success after 77ms
Dec 17 19:04:39 angua PackageKit[22717]: get-updates transaction /5440_caaebcbe from uid 1000 finished with success after 78ms
Dec 17 19:04:39 angua PackageKit[22717]: get-updates transaction /5441_abdbdebb from uid 1000 finished with success after 77ms
Dec 17 19:09:44 angua PackageKit[22717]: daemon quit
Dec 17 19:09:44 angua systemd[1]: packagekit.service: Deactivated successfully.

NetworkManager.service on the other hand is a long-running daemon

$ systemctl status NetworkManager.service 
● NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; preset: enabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Sun 2023-12-17 09:51:46 PST; 9h ago
...