Latest dom0 update: sys-net is crashing

Thinkpad P1 Gen 5 on Qubes 4.2.4 (R4.2). Been running Qubes on this machine beautifully for i think 4 years now never had any issues. Actually, correction I had two issues initially many years ago first one was screen was glitchy and fixed by setting kernel to the latest and second was sound fromnspeaker was garbled which i fixed by disabling microphone in the bios.

Anyhoo, since then its been smooth sailing. I keep it updated reguarly and sincr the latest dom0 update from a few days ago my wifi in sys-net has become unreliable.

It will work but sometimes after an hour or a few hours it just stops working. when i click on the sys-net tray icon the wifi adapter will not even show. one time the other day it actually said something telling me i have enabled the wifi hardware kill switch (thinkpads dont have that). another time (last night) the whole system froze which is a first i had to hold down power switch for 30seconds to turn it off and even had to resync bios clock after that.

i have a very standard install i am using default templates (its now at fedora 42) and kernel is at 6.12.54.1-fc37

i expecting other topics to be posted because i assume would be wide spread issue people would start reporting but its been a few days and no topics on it created so i want to bring it up.

fyi sys-net is set to 800MB initial memory and 2 vcpu. private storage size set to 2GB i just increased to 5GB. not sure what else to do has been no changes to the system settings or templates i keep things pretty vanilla.

any help would be much appreciated

thank you

I see that you got no replies, so I will suggest some things, although I didn’t get any problem after the latest updates.

  1. try booting the previous kernel (in the initial grub menu)
  2. in addition to #1, try setting the kernel in sys-net to point to an older version.
  3. try getting some logs (dom0:/var/log/xen/console/guest-sys-net.log, “sudo dmesg” in sys-net) around the time when your WiFi adapter crashes/dissapears.

Hope this helps.
Another idea: There are ways to revert “dnf” transactions but I’ve never tried it in dom0. Running the/a previous kernel should suffice.