PCI wifi adapter unrecognized after dom0's kernel update to 6.12

[unwatched-wasabi-roving-renounce-trash]

How to file a helpful issue

Qubes OS release

R4.2.3, kernel 6.12.5-2

Brief summary

After the dom0 kernel update to 6.12, the PCI device Network controller: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter wasn't recognized and sys-net crash at boot.

Steps to reproduce

Update dom0 kernel to 6.12 and use Network controller: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter as hardware.

Expected behavior

PCI device should be available

Actual behavior

See Brief summary.

Fix

Rollback to 6.11 kernel

Notes

I am unsure if this bug should be reported upstream.

[marmarek]

I am unsure if this bug should be reported upstream.

Probably yes. Can you share the crash message?

[unwatched-wasabi-roving-renounce-trash]

logs-sys-net.txt

Hi !
Sorry for the delay, here are the logs.

[marmarek]

And where is the problem? I don't see any wifi driver crash there, and there is even message it successfully associated to the wifi network.

[unwatched-wasabi-roving-renounce-trash]

I'm sorry, I didn't see any error and I though I was missing something.

I ran egrep -i "error|failed" /var/log/xen/console/guest-sys-net* to filter directly, not many errors appear :

/var/log/xen/console/guest-sys-net-dm.log:[2025-01-05 15:13:45] tsc: Fast TSC calibration failed
/var/log/xen/console/guest-sys-net-dm.log:[2025-01-05 19:04:49] tsc: Fast TSC calibration failed
/var/log/xen/console/guest-sys-net-dm.log:[2025-01-05 21:33:44] tsc: Fast TSC calibration failed
/var/log/xen/console/guest-sys-net-dm.log:[2025-01-06 10:15:48] tsc: Fast TSC calibration failed
/var/log/xen/console/guest-sys-net-dm.log:[2025-01-09 10:08:04] tsc: Fast TSC calibration failed
/var/log/xen/console/guest-sys-net.log:[2025-01-05 00:22:50] [.[0;1;31mFAILED.[0m] Failed unmounting .[0;1;39musr-lib-…ules.mount.[0m - /usr/lib/modules.
/var/log/xen/console/guest-sys-net.log:[2025-01-05 15:13:48] [    0.661324] RAS: Correctable Errors collector initialized.
/var/log/xen/console/guest-sys-net.log:[2025-01-05 15:13:50] [    2.304690] Error: Driver 'pcspkr' is already registered, aborting...
/var/log/xen/console/guest-sys-net.log:[2025-01-05 15:14:18] [   30.778029] traps: light-locker[1095] trap int3 ip:71f2a61407d7 sp:7ffccd069500 error:0 in libglib-2.0.so.0.7400.6[5b7d7,71f2a6102000+8d000]
/var/log/xen/console/guest-sys-net.log:[2025-01-05 16:45:04] [.[0;1;31mFAILED.[0m] Failed unmounting .[0;1;39musr-lib-…ules.mount.[0m - /usr/lib/modules.
/var/log/xen/console/guest-sys-net.log:[2025-01-05 19:04:52] [    0.691784] RAS: Correctable Errors collector initialized.
/var/log/xen/console/guest-sys-net.log:[2025-01-05 19:04:54] [    2.610078] Error: Driver 'pcspkr' is already registered, aborting...
/var/log/xen/console/guest-sys-net.log:[2025-01-05 19:05:19] [   27.233624] traps: light-locker[1104] trap int3 ip:7d1affac67d7 sp:7fffeea8a6e0 error:0 in libglib-2.0.so.0.7400.6[5b7d7,7d1affa88000+8d000]
/var/log/xen/console/guest-sys-net.log:[2025-01-05 20:02:34] [.[0;1;31mFAILED.[0m] Failed unmounting .[0;1;39musr-lib-…ules.mount.[0m - /usr/lib/modules.
/var/log/xen/console/guest-sys-net.log:[2025-01-05 21:33:47] [    0.892944] RAS: Correctable Errors collector initialized.
/var/log/xen/console/guest-sys-net.log:[2025-01-05 21:33:49] [    2.715973] Error: Driver 'pcspkr' is already registered, aborting...
/var/log/xen/console/guest-sys-net.log:[2025-01-05 21:34:34] [   48.355506] traps: light-locker[1023] trap int3 ip:78bd0aa607d7 sp:7ffd8ad2cd80 error:0 in libglib-2.0.so.0.7400.6[5b7d7,78bd0aa22000+8d000]
/var/log/xen/console/guest-sys-net.log:[2025-01-05 22:39:26] [.[0;1;31mFAILED.[0m] Failed unmounting .[0;1;39musr-lib-…ules.mount.[0m - /usr/lib/modules.
/var/log/xen/console/guest-sys-net.log:[2025-01-06 10:15:52] [    0.856960] RAS: Correctable Errors collector initialized.
/var/log/xen/console/guest-sys-net.log:[2025-01-06 10:15:55] [    3.676629] Error: Driver 'pcspkr' is already registered, aborting...
/var/log/xen/console/guest-sys-net.log:[2025-01-06 10:16:24] [   33.241854] traps: light-locker[1116] trap int3 ip:7956d7ac67d7 sp:7ffe999beb00 error:0 in libglib-2.0.so.0.7400.6[5b7d7,7956d7a88000+8d000]
/var/log/xen/console/guest-sys-net.log:[2025-01-06 16:49:59] [.[0;1;31mFAILED.[0m] Failed unmounting .[0;1;39musr-lib-…ules.mount.[0m - /usr/lib/modules.
/var/log/xen/console/guest-sys-net.log:[2025-01-09 10:08:07] [    0.792133] RAS: Correctable Errors collector initialized.
/var/log/xen/console/guest-sys-net.log:[2025-01-09 10:08:11] [    4.443992] Error: Driver 'pcspkr' is already registered, aborting...
/var/log/xen/console/guest-sys-net.log:[2025-01-09 10:08:33] [   26.128996] traps: light-locker[1099] trap int3 ip:7af6963407d7 sp:7fff89c72fa0 error:0 in libglib-2.0.so.0.7400.6[5b7d7,7af696302000+8d000]

[unwatched-wasabi-roving-renounce-trash]

I may need to reboot to check the error directly, but I can't use my computer during this operation.

[unwatched-wasabi-roving-renounce-trash]

$ qvm-start sys-net
PCI device dom0:01_00.0 does not exist

-> in journalctl -f
Jan 10 14:19:43 dom0 qubesd[6195]: vm.sys-net: Starting sys-net
Jan 10 14:19:43 dom0 qubesd[6195]: vm.sys-net: Start failed: PCI device dom0:01_00.0 does not exist

$ lspci | grep -i network
01:00.0 Network controller: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter

$ qvm-pci | grep -i network
{empty}

$ qvm-pci ls sys-net
BACKEND:DEVID DESCRIPTION USED BY
dom0:01_00.0 Unknown device sys-net

$ sudo dmesg | grep -i iwlwifi
{empty}

$ sudo dmesg | egrep -i "mt7922"
{empty}

After inspecting more closely the guest's xen-console logs, they have nothing to do with the error I'm describing as sys-net can't boot when the PCI device isn't recognized.

[marmarek]

$ qvm-pci ls sys-net
BACKEND:DEVID DESCRIPTION USED BY
dom0:01_00.0 Unknown device sys-net

This is interesting. Check if restarting qubesd service helps. Do you see some errors related to this device in dom0? Something suggesting it was detected only later, not during initial PCI devices enumeration?

[unwatched-wasabi-roving-renounce-trash]

I'll try restarting qubesd service!

I don't see any other error that I reported, but maybe I need to look in the right place?

I'm not familiar enough with Xen and QubesOS to know what I should look for but I'm willing to learn, any logs you want me to look for or command that you want me to run to help the diagnosis ?