Fedora 36 kde randomly freezes on my laptop. Basically, before the system freezes the wifi stops working and the wifi icons turns red. It shows the wifi is connected but internet doesn’t works and then I click on the icon to disconnect wifi but this causes the latte dock to freeze. After few seconds the whole system freezes. At that time if I open the system monitor its doesn’t show any stats, like no processing graph, no RAM graph or any network history. And if I try to reboot system it stucks at stopping two processes ( network manager.service and wpa_supplicant.sevice ) forever and sometimes it also shows a PCIe bus error. I will attach more screenshots later on for better understanding.
https://imgur.com/a/tp4OaLA
having the same issue here. first i loose the internet connection while wifi is still on (it may show limited connectivity or not), then i turn wifi off and when i click to reconnect it immediately completely frezes the system. it is extremely consistent - i got the exact same outcome 3 or 4 times in a row in 10 minutes.
fedora 36, kde and x11. no major updates or changes to the system prior to first occurance.
ps:
i turn wifi off and when i click to reconnect it immediately completely frezes the system
it only frezes the system if there’s active loss of the internet connectivity. so, let’s say, now it seems to work normally and i can disconnect and reconnect to my wifi without any issues.
actually, now i can add that the wifi fails in several minutes if there’s intensive download going on. and to get a freeze you just need to disconnect and wait, it just happens when wifi networks are rescanned.
upd: tried to cheese my way around it and reboot right after wifi dropped. it just froze on reboot cycle on black screen with fedora logo.
Things were same with me, I had to reinstall Fedora.
so i was doing some extensive testing and found out that this actually happens at any dl speed - unlimited at around 22mbps or limited at 15-10-5 and even at 2mbps, the key factor is just constant data transfer.
however, turns out this bs is somehow qbittorrent-specific. i tried ktorrent and it works. so?..
It’s a shame, this is still not resolved in July 2023.
1 Like
4 months have passed without any other reports of this issue, and it was solved with a reinstall. If the marked solution (reinstall) does not work for you, please start a new topic instead of replying.
If you don’t have a robust backup/restore regime, reinstall may need extra work to ensure you don’t loose important data/documents. One reason a reinstall fixes problems is when the previous installation used 3rd party drivers that have since been replaced by better versions.
So the thing is, I just installed it 2 days ago. My laptop doesn’t use any proprietary drivers. The only things I have installed are some themes and icons. And a few flatpaks.
This is my first time using Fedora/KDE, previously an all time Linux mint user. Unless I am doing something wrong with not enabling some rpmfusion repos, I really don’t think any reinstall will help.
The saddest part is that the system freezes so badly that we can’t even open a TTY screen. If it was just a plasmashell freeze, then we could kill and start over in TTY. We can’t even get any logs as the only thing left to do is simply power off.
Actually, I forgot to mention, the issue continued even after reinstallation. It worked for a few days, and again it started happening, even on a live boot of any distro.
I figured out that the main problem was with my network card (MediaTek MT7921LEN), I replaced it with a new (Intel AX210NGW). And since then I haven’t encountered any issue regarding it.
Please do not mark this as a solution as it’s not possible for most people to replace their network cards.
Do you have any idea if this is happening only on KDE Fedora or also on GNOME Fedora? If it’s happening in both places then it’s a Fedora issue as nothing of this sort has ever happened on any of my Ubuntu or Arch installs so far. In my opinion I think it’s a Fedora issue as I was also trying KDE Neon and Kubuntu for some time.
As i said, it was even happening in live boot (fedora KDE, fedora gnome, garuda, pop-os, linux mint).
My friend was also facing a similar issue in a windows installation with the same MediaTek card, but sometimes it happens, sometimes it doesn’t.
Can you tell which network card you are using, as I can only think of this as a reasonable cause.
I see similar events.
I have
04:00.0 Network controller [0280]: Qualcomm Atheros AR93xx Wireless Network Adapter [168c:0030] (rev 01)
Subsystem: Qualcomm Atheros Device [168c:3112]
Kernel driver in use: ath9k
and my wifi drops and reconnects at about 5 minute intervals with frequent (at least daily but sometimes much more often) an MCE kernel event causing a freeze and reboot.
I have ordered an intel AX210 card and will post after it has been installed with an update.
I had absolutely no issues with this while running kernels 6.2.X and below but it started when the kernels were updated to the 6.3 release.
1 Like
I found out why wifi was disconnecting.
With part of the power saving features done in Fedora 38 wifi was configured to disconnect when idle. Mine was not idle and I don’t know how much time it had to be idle but I found that the file /etc/NetworkManager/conf.d/00-wifi-powersave.conf contained the following
[connection]
wifi.powersave=2
I changed that line to wifi-powersave=0 and it quit disconnecting at <5 minute intervals.
Note that in the man page NetworkManager.conf one does not find the meaning of the different values for that parameter. I guessed that the 0 would mean to ignore or not apply power saving. It will take more research to determine exactly what each valid value means.
I also replaced my qualcomm wifi adapter with an intel AX210NGW m.2 card (wifi 6e) as I stated was in progress earlier and we will see if these 2 changes halt the errors that were causing the MCE events. Hopefully so.
There is some discussion about the wifi.powersave at
but I am not convinced the values given have the results shown in that table.
@sayantanrc can you test this out and report us back here, if it fixes your problem then I will try it myself on a new install. Then i will mark it as the solution.
The /etc/NetworkManager/conf.d/ directory is empty on both my F38 systems. Many discussions of wifi power management propose similar files, but I have not found one that points to the upstream documentation.
As of right now my system has gone 24 hrs without a machine check.
It has for quite some time shown OOPS and MCE errrors, with the OOPs always a result of a stuck cpu.
So far I am leaning toward the belief that the stuck cpu events may have been caused by the network disconnecting in the middle of some transaction on the internet. Many were directly linked to using my browser when the system froze then rebooted (it happened when the system was in use and the logs showed the wifi disconnecting then reconnecting at least once every 5 minutes)
Since I made that change in the file noted It has shown NO DISCONNECTS except those expected when the lease needed renewed. (approximately 4 hour intervals). There have also been no crashes in the same period.
Prior to the change in /etc/NetworkManager/conf.d/00-wifi-powersave.conf this is an example of what I was seeing related to wifi connections.
Jul 20 18:26:48 eagle.home.domain NetworkManager[1590]: <info> [1689895608.5095] device (wlp5s0): driver supports Access Point (AP) mode
Jul 20 18:26:48 eagle.home.domain NetworkManager[1590]: <info> [1689895608.5099] manager: (wlp5s0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)
Jul 20 18:26:48 eagle.home.domain NetworkManager[1590]: <info> [1689895608.5101] device (wlp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jul 20 18:26:48 eagle.home.domain NetworkManager[1590]: <info> [1689895608.8159] device (wlp5s0): set-hw-addr: set MAC address to FE:0B:24:78:8E:63 (scanning)
Jul 20 18:26:49 eagle.home.domain NetworkManager[1590]: <info> [1689895609.0919] device (lo): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
Jul 20 18:26:49 eagle.home.domain NetworkManager[1590]: <info> [1689895609.0920] device (lo): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
Jul 20 18:26:49 eagle.home.domain NetworkManager[1590]: <info> [1689895609.0921] device (lo): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
Jul 20 18:26:49 eagle.home.domain NetworkManager[1590]: <info> [1689895609.0925] device (lo): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
Jul 20 18:26:49 eagle.home.domain NetworkManager[1590]: <info> [1689895609.0931] modem-manager: ModemManager available
Jul 20 18:26:49 eagle.home.domain NetworkManager[1590]: <info> [1689895609.0934] device (lo): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
Jul 20 18:26:49 eagle.home.domain NetworkManager[1590]: <info> [1689895609.0935] device (lo): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
Jul 20 18:26:49 eagle.home.domain NetworkManager[1590]: <info> [1689895609.0937] device (lo): Activation: successful, device activated.
Jul 20 18:26:49 eagle.home.domain NetworkManager[1590]: <info> [1689895609.1247] device (wlp5s0): supplicant interface state: internal-starting -> disconnected
Jul 20 18:26:49 eagle.home.domain NetworkManager[1590]: <info> [1689895609.1248] Wi-Fi P2P device controlled by interface wlp5s0 created
Jul 20 18:26:49 eagle.home.domain NetworkManager[1590]: <info> [1689895609.1249] manager: (p2p-dev-wlp5s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/4)
Jul 20 18:26:49 eagle.home.domain NetworkManager[1590]: <info> [1689895609.1250] device (p2p-dev-wlp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jul 20 18:26:49 eagle.home.domain NetworkManager[1590]: <info> [1689895609.1252] device (wlp5s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Jul 20 18:26:49 eagle.home.domain NetworkManager[1590]: <info> [1689895609.1254] device (p2p-dev-wlp5s0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Jul 20 18:26:51 eagle.home.domain NetworkManager[1590]: <info> [1689895611.1988] agent-manager: agent[e677cf0e8d8dc09c,:1.40/org.gnome.Shell.NetworkAgent/42]: agent registered
Jul 20 18:26:55 eagle.home.domain NetworkManager[1590]: <info> [1689895615.0884] manager: startup complete
Jul 20 18:26:55 eagle.home.domain systemd[1]: Finished NetworkManager-wait-online.service - Network Manager Wait Online.
Jul 20 18:26:55 eagle.home.domain systemd[1]: Reached target network-online.target - Network is Online.
Jul 20 18:26:55 eagle.home.domain systemd[1]: Started boinc-client.service - Berkeley Open Infrastructure Network Computing Client.
Jul 20 18:26:59 eagle.home.domain systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Jul 20 18:27:12 eagle.home.domain NetworkManager[1590]: <info> [1689895632.1388] agent-manager: agent[5d0f8596cf30f09d,:1.93/org.gnome.Shell.NetworkAgent/1000]: agent registered
Jul 20 18:27:24 eagle.home.domain packagekitd[1967]: Failed to get cache filename for NetworkManager-openconnect-gnome
Jul 20 18:30:57 eagle.home.domain NetworkManager[1590]: <info> [1689895857.2164] device (wlp5s0): Activation: starting connection 'My-Linksys_5GHz' (6b7655ba-fca4-44b0-a590-af7a4c153b43)
Jul 20 18:30:57 eagle.home.domain NetworkManager[1590]: <info> [1689895857.2169] device (wlp5s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jul 20 18:30:57 eagle.home.domain NetworkManager[1590]: <info> [1689895857.2170] manager: NetworkManager state is now CONNECTING
Jul 20 18:30:57 eagle.home.domain NetworkManager[1590]: <info> [1689895857.2354] device (wlp5s0): set-hw-addr: reset MAC address to 64:49:7D:E5:D3:5A (preserve)
Jul 20 18:30:57 eagle.home.domain NetworkManager[1590]: <info> [1689895857.2391] device (wlp5s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jul 20 18:30:57 eagle.home.domain NetworkManager[1590]: <info> [1689895857.2393] device (wlp5s0): Activation: (wifi) access point 'My-Linksys_5GHz' has security, but secrets are required.
Jul 20 18:30:57 eagle.home.domain NetworkManager[1590]: <info> [1689895857.2393] device (wlp5s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jul 20 18:30:57 eagle.home.domain NetworkManager[1590]: <info> [1689895857.2405] device (wlp5s0): supplicant interface state: disconnected -> inactive
Jul 20 18:30:57 eagle.home.domain NetworkManager[1590]: <info> [1689895857.2405] device (p2p-dev-wlp5s0): supplicant management interface state: disconnected -> inactive
Jul 20 18:31:06 eagle.home.domain NetworkManager[1590]: <info> [1689895866.5319] device (wlp5s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jul 20 18:31:06 eagle.home.domain NetworkManager[1590]: <info> [1689895866.5320] device (wlp5s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jul 20 18:31:06 eagle.home.domain NetworkManager[1590]: <info> [1689895866.5322] device (wlp5s0): Activation: (wifi) connection 'My-Linksys_5GHz' has security, and secrets exist. No new secrets needed.
Jul 20 18:31:06 eagle.home.domain NetworkManager[1590]: <info> [1689895866.5322] Config: added 'ssid' value 'My-Linksys_5GHz'
Jul 20 18:31:06 eagle.home.domain NetworkManager[1590]: <info> [1689895866.5322] Config: added 'scan_ssid' value '1'
Jul 20 18:31:06 eagle.home.domain NetworkManager[1590]: <info> [1689895866.5322] Config: added 'bgscan' value 'simple:30:-70:86400'
Jul 20 18:31:06 eagle.home.domain NetworkManager[1590]: <info> [1689895866.5322] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
Jul 20 18:31:06 eagle.home.domain NetworkManager[1590]: <info> [1689895866.5322] Config: added 'auth_alg' value 'OPEN'
Jul 20 18:31:06 eagle.home.domain NetworkManager[1590]: <info> [1689895866.5322] Config: added 'psk' value '<hidden>'
Jul 20 18:31:06 eagle.home.domain NetworkManager[1590]: <info> [1689895866.5416] device (wlp5s0): supplicant interface state: inactive -> scanning
Jul 20 18:31:06 eagle.home.domain NetworkManager[1590]: <info> [1689895866.5416] device (p2p-dev-wlp5s0): supplicant management interface state: inactive -> scanning
Jul 20 18:31:09 eagle.home.domain NetworkManager[1590]: <info> [1689895869.3176] device (wlp5s0): supplicant interface state: scanning -> authenticating
Jul 20 18:31:09 eagle.home.domain NetworkManager[1590]: <info> [1689895869.3177] device (p2p-dev-wlp5s0): supplicant management interface state: scanning -> authenticating
Jul 20 18:31:09 eagle.home.domain NetworkManager[1590]: <info> [1689895869.3573] device (wlp5s0): supplicant interface state: authenticating -> associating
Jul 20 18:31:09 eagle.home.domain NetworkManager[1590]: <info> [1689895869.3573] device (p2p-dev-wlp5s0): supplicant management interface state: authenticating -> associating
Jul 20 18:31:09 eagle.home.domain NetworkManager[1590]: <info> [1689895869.4267] device (wlp5s0): supplicant interface state: associating -> completed
Jul 20 18:31:09 eagle.home.domain NetworkManager[1590]: <info> [1689895869.4267] device (wlp5s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "My-Linksys_5GHz"
Jul 20 18:31:09 eagle.home.domain NetworkManager[1590]: <info> [1689895869.4267] device (p2p-dev-wlp5s0): supplicant management interface state: associating -> completed
Jul 20 18:31:09 eagle.home.domain NetworkManager[1590]: <info> [1689895869.4335] device (wlp5s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jul 20 18:31:09 eagle.home.domain NetworkManager[1590]: <info> [1689895869.4338] dhcp4 (wlp5s0): activation: beginning transaction (timeout in 45 seconds)
Jul 20 18:31:10 eagle.home.domain NetworkManager[1590]: <info> [1689895870.4632] dhcp4 (wlp5s0): state changed new lease, address=192.168.4.60
Jul 20 18:31:10 eagle.home.domain NetworkManager[1590]: <info> [1689895870.4634] policy: set 'My-Linksys_5GHz' (wlp5s0) as default for IPv4 routing and DNS
Jul 20 18:31:10 eagle.home.domain NetworkManager[1590]: <info> [1689895870.4666] device (wlp5s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jul 20 18:31:10 eagle.home.domain systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service...
Jul 20 18:31:10 eagle.home.domain systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service.
Jul 20 18:31:10 eagle.home.domain NetworkManager[1590]: <info> [1689895870.4909] device (wlp5s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jul 20 18:31:10 eagle.home.domain NetworkManager[1590]: <info> [1689895870.4910] device (wlp5s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jul 20 18:31:10 eagle.home.domain NetworkManager[1590]: <info> [1689895870.4911] manager: NetworkManager state is now CONNECTED_SITE
Jul 20 18:31:10 eagle.home.domain NetworkManager[1590]: <info> [1689895870.4915] device (wlp5s0): Activation: successful, device activated.
Jul 20 18:31:10 eagle.home.domain NetworkManager[1590]: <info> [1689895870.7978] manager: NetworkManager state is now CONNECTED_GLOBAL
Jul 20 18:31:11 eagle.home.domain NetworkManager[1590]: <info> [1689895871.1776] policy: set 'My-Linksys_5GHz' (wlp5s0) as default for IPv6 routing and DNS
Jul 20 18:31:20 eagle.home.domain systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Jul 20 18:32:22 eagle.home.domain NetworkManager[1590]: <info> [1689895942.7002] device (wlp5s0): state change: activated -> deactivating (reason 'connection-removed', sys-iface-state: 'managed')
Jul 20 18:32:22 eagle.home.domain NetworkManager[1590]: <info> [1689895942.7004] manager: NetworkManager state is now DISCONNECTING
Jul 20 18:32:22 eagle.home.domain systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service...
Jul 20 18:32:22 eagle.home.domain systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service.
Jul 20 18:32:22 eagle.home.domain NetworkManager[1590]: <info> [1689895942.8041] device (wlp5s0): supplicant interface state: completed -> disconnected
Jul 20 18:32:22 eagle.home.domain NetworkManager[1590]: <info> [1689895942.8042] device (p2p-dev-wlp5s0): supplicant management interface state: completed -> disconnected
Jul 20 18:32:22 eagle.home.domain NetworkManager[1590]: <info> [1689895942.8043] device (wlp5s0): state change: deactivating -> disconnected (reason 'connection-removed', sys-iface-state: 'managed')
Jul 20 18:32:22 eagle.home.domain NetworkManager[1590]: <info> [1689895942.8216] dhcp4 (wlp5s0): canceled DHCP transaction
Jul 20 18:32:22 eagle.home.domain NetworkManager[1590]: <info> [1689895942.8216] dhcp4 (wlp5s0): activation: beginning transaction (timeout in 45 seconds)
Jul 20 18:32:22 eagle.home.domain NetworkManager[1590]: <info> [1689895942.8216] dhcp4 (wlp5s0): state changed no lease
Jul 20 18:32:22 eagle.home.domain NetworkManager[1590]: <info> [1689895942.8401] device (wlp5s0): set-hw-addr: set MAC address to BA:23:34:BD:E0:8D (scanning)
Jul 20 18:32:22 eagle.home.domain NetworkManager[1590]: <info> [1689895942.8870] manager: NetworkManager state is now DISCONNECTED
Jul 20 18:32:22 eagle.home.domain NetworkManager[1590]: <info> [1689895942.8874] device (wlp5s0): supplicant interface state: disconnected -> interface_disabled
Jul 20 18:32:22 eagle.home.domain NetworkManager[1590]: <info> [1689895942.8874] device (p2p-dev-wlp5s0): supplicant management interface state: disconnected -> interface_disabled
Jul 20 18:32:22 eagle.home.domain NetworkManager[1590]: <info> [1689895942.8875] device (wlp5s0): supplicant interface state: interface_disabled -> disconnected
Jul 20 18:32:22 eagle.home.domain NetworkManager[1590]: <info> [1689895942.8875] device (p2p-dev-wlp5s0): supplicant management interface state: interface_disabled -> disconnected
Jul 20 18:32:28 eagle.home.domain NetworkManager[1590]: <info> [1689895948.4314] device (wlp5s0): Activation: starting connection 'My-Linksys_5GHz' (d0224c16-31e9-4af5-9a05-7649abb56865)
Jul 20 18:32:28 eagle.home.domain NetworkManager[1590]: <info> [1689895948.4320] device (wlp5s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jul 20 18:32:28 eagle.home.domain NetworkManager[1590]: <info> [1689895948.4321] manager: NetworkManager state is now CONNECTING
Jul 20 18:32:28 eagle.home.domain NetworkManager[1590]: <info> [1689895948.4606] device (wlp5s0): set-hw-addr: reset MAC address to 64:49:7D:E5:D3:5A (preserve)
Jul 20 18:32:28 eagle.home.domain NetworkManager[1590]: <info> [1689895948.4660] device (wlp5s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jul 20 18:32:28 eagle.home.domain NetworkManager[1590]: <info> [1689895948.4662] device (wlp5s0): Activation: (wifi) access point 'My-Linksys_5GHz' has security, but secrets are required.
Jul 20 18:32:28 eagle.home.domain NetworkManager[1590]: <info> [1689895948.4662] device (wlp5s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jul 20 18:32:28 eagle.home.domain NetworkManager[1590]: <info> [1689895948.4667] device (wlp5s0): supplicant interface state: disconnected -> interface_disabled
Jul 20 18:32:28 eagle.home.domain NetworkManager[1590]: <info> [1689895948.4667] device (p2p-dev-wlp5s0): supplicant management interface state: disconnected -> interface_disabled
Jul 20 18:32:28 eagle.home.domain NetworkManager[1590]: <info> [1689895948.4848] device (wlp5s0): supplicant interface state: interface_disabled -> disconnected
Jul 20 18:32:28 eagle.home.domain NetworkManager[1590]: <info> [1689895948.4848] device (p2p-dev-wlp5s0): supplicant management interface state: interface_disabled -> disconnected
Jul 20 18:32:32 eagle.home.domain systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Jul 20 18:32:41 eagle.home.domain NetworkManager[1590]: <info> [1689895961.2982] device (wlp5s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jul 20 18:32:41 eagle.home.domain NetworkManager[1590]: <info> [1689895961.2984] device (wlp5s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jul 20 18:32:41 eagle.home.domain NetworkManager[1590]: <info> [1689895961.2987] device (wlp5s0): Activation: (wifi) connection 'My-Linksys_5GHz' has security, and secrets exist. No new secrets needed.
Jul 20 18:32:41 eagle.home.domain NetworkManager[1590]: <info> [1689895961.2987] Config: added 'ssid' value 'My-Linksys_5GHz'
Jul 20 18:32:41 eagle.home.domain NetworkManager[1590]: <info> [1689895961.2987] Config: added 'scan_ssid' value '1'
Jul 20 18:32:41 eagle.home.domain NetworkManager[1590]: <info> [1689895961.2987] Config: added 'bgscan' value 'simple:30:-70:86400'
Jul 20 18:32:41 eagle.home.domain NetworkManager[1590]: <info> [1689895961.2987] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
Jul 20 18:32:41 eagle.home.domain NetworkManager[1590]: <info> [1689895961.2987] Config: added 'auth_alg' value 'OPEN'
Jul 20 18:32:41 eagle.home.domain NetworkManager[1590]: <info> [1689895961.2987] Config: added 'psk' value '<hidden>'
Jul 20 18:32:41 eagle.home.domain NetworkManager[1590]: <info> [1689895961.3081] device (wlp5s0): supplicant interface state: disconnected -> scanning
Jul 20 18:32:41 eagle.home.domain NetworkManager[1590]: <info> [1689895961.3081] device (p2p-dev-wlp5s0): supplicant management interface state: disconnected -> scanning
Jul 20 18:32:43 eagle.home.domain NetworkManager[1590]: <info> [1689895963.6332] device (wlp5s0): supplicant interface state: scanning -> authenticating
Jul 20 18:32:43 eagle.home.domain NetworkManager[1590]: <info> [1689895963.6332] device (p2p-dev-wlp5s0): supplicant management interface state: scanning -> authenticating
Jul 20 18:32:43 eagle.home.domain NetworkManager[1590]: <info> [1689895963.6751] device (wlp5s0): supplicant interface state: authenticating -> associating
Jul 20 18:32:43 eagle.home.domain NetworkManager[1590]: <info> [1689895963.6751] device (p2p-dev-wlp5s0): supplicant management interface state: authenticating -> associating
Jul 20 18:32:43 eagle.home.domain NetworkManager[1590]: <info> [1689895963.7616] device (wlp5s0): supplicant interface state: associating -> completed
Jul 20 18:32:43 eagle.home.domain NetworkManager[1590]: <info> [1689895963.7617] device (wlp5s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "My-Linksys_5GHz"
Jul 20 18:32:43 eagle.home.domain NetworkManager[1590]: <info> [1689895963.7617] device (p2p-dev-wlp5s0): supplicant management interface state: associating -> completed
Jul 20 18:32:43 eagle.home.domain NetworkManager[1590]: <info> [1689895963.7696] device (wlp5s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jul 20 18:32:43 eagle.home.domain NetworkManager[1590]: <info> [1689895963.7699] dhcp4 (wlp5s0): activation: beginning transaction (timeout in 45 seconds)
Jul 20 18:32:43 eagle.home.domain NetworkManager[1590]: <info> [1689895963.7802] dhcp4 (wlp5s0): state changed new lease, address=192.168.4.111
Jul 20 18:32:43 eagle.home.domain NetworkManager[1590]: <info> [1689895963.7804] policy: set 'My-Linksys_5GHz' (wlp5s0) as default for IPv4 routing and DNS
Jul 20 18:32:43 eagle.home.domain NetworkManager[1590]: <info> [1689895963.7855] device (wlp5s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jul 20 18:32:43 eagle.home.domain systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service...
Jul 20 18:32:43 eagle.home.domain systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service.
Jul 20 18:32:43 eagle.home.domain NetworkManager[1590]: <info> [1689895963.8081] device (wlp5s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jul 20 18:32:43 eagle.home.domain NetworkManager[1590]: <info> [1689895963.8082] device (wlp5s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jul 20 18:32:43 eagle.home.domain NetworkManager[1590]: <info> [1689895963.8084] manager: NetworkManager state is now CONNECTED_SITE
Jul 20 18:32:43 eagle.home.domain NetworkManager[1590]: <info> [1689895963.8098] device (wlp5s0): Activation: successful, device activated.
Jul 20 18:32:44 eagle.home.domain NetworkManager[1590]: <info> [1689895964.0825] manager: NetworkManager state is now CONNECTED_GLOBAL
Jul 20 18:32:45 eagle.home.domain NetworkManager[1590]: <info> [1689895965.3323] policy: set 'My-Linksys_5GHz' (wlp5s0) as default for IPv6 routing and DNS
Jul 20 18:32:54 eagle.home.domain systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Jul 20 18:42:00 eagle.home.domain sudo[6547]: jvian : TTY=pts/0 ; PWD=/home/jvian ; USER=root ; COMMAND=/usr/bin/vim /etc/NetworkManager/conf.d/00-wifi-powersave.conf
Note that begins with bootup after installing the new wifi adapter and ends with editing the noted file.
There have been no entries from NetworkManager since that file in conf.d was edited and in the ~6 minutes shown from that log there were 2 times the wifi was disabled and reconnected. (A total of 5 times, with 2 causing a crash in the first 12 hours, on that date)
Years ago a system was crashing and the problem went away after replacing an improperly crimped 10base-T cable (I assume making intermittent loss of connection). A batch of cables had the same bad crimps, but only one system was affected to the point of crashing, while others had reduced thruput. I suppose we need a device that randomly disconnects one network wire to insure that the network software handles such conditions.
It does not appear that NetworkManager caused the crash directly, but that the frequent disconnect and reconnect interrupted communications in such a way that apps attempting to communicate through that device caused a cpu hang which resulted in the crash with an MCE event.
In most cases there were one or two OOPSes logged showing a cpu stuck for 26 or 54 or even more than 80 seconds followed by the MCE and crash.
Just to confirm the test I will restore the content of that file and see if the errors and crashes resume.
I would be interested to hear from @sayantanrc & @xeo32 and @malarkos to know if they have tried this type of fix and what the results may have been.
Just a quick update.
I restored the content of /etc/NetworkManager/conf.d/00-wifi-powersave.conf to what it contained originally.
[connection]
wifi.powersave=2
I have had absolutely no wifi interrupts nor crashes since.
This leads me to conclude that the previously installed qualcomm adapter was either failing or the driver has a problem. The intel AX210NGW card installed now has no problems at all and it totally stopped the frequent freezes and crashes.
For those having similar freezes with wifi I would strongly suggest that one consider replacing the wifi adapter with one that has known good support with fedora.
Note that my qualcomm adapter worked well with earlier kernels (6.2.X and earlier) but began acting up after installing the 6.3 kernels
It is money well spent supporting a vendor that makes linux drivers a priority. For a business, the cost of replacing problematic hardware is often much less than the cost of lost time using unreliable hardware.
See List of Supported Intel WiFi Devices along with information on firmware and a link to known issues, including a section on “Platform Noise” that may surprise some users.