WSL2 Mirrored networking mode reproducibly triggers 0x9F DRIVER_POWER_STATE_FAILURE (Intel BE200 Wi-Fi) at every boot
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 25/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- cpp, linux
- Ambito
- networking
Direzione di ricerca
Start by reviewing the attached minidump and event log alongside the reported kernel dump stack, focusing on the blocked power IRP in the Wi-Fi miniport stop path. Compare boot behavior with Mirrored and NAT networking modes; done means Mirrored mode boots without the 0x9F bugcheck or hard hang on the reported Intel BE200 setup.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Windows Version
Windows 11 Pro, build 26100 (24H2)
WSL Version
WSL: 3.0.3.0
Are you using WSL 1, WSL 2, or WSLC?
- WSL 2
- WSL 1
- WSLC
Kernel Version
6.18.54.1-1
Distro Version
Ubuntu-22.04
Other Software
None. The issue reproduces with WSL alone - no Docker, VS Code, or third-party software involved.
Repro Steps
rerequisite: Intel Wi-Fi 7 BE200 wireless adapter (M.2 CNVi), WSL 2.
-
Set %USERPROFILE%.wslconfig to:
[wsl2]
networkingMode=Mirrored
firewall=false -
Run
wsl --shutdown, then reboot the machine. -
No user action needed after reboot. The failure occurs 8-13 seconds after boot,
immediately after the Wi-Fi driver logs "Wi-Fi Driver Enabled"
(Netwaw18/Netwaw20 event 7010 in the System log).
Result: 100% reproducible - every single boot with Mirrored mode.
Control test (same machine, same steps, only networkingMode changed):
- networkingMode=NAT -> boots cleanly every time, zero failures
Expected Behavior
The system should boot normally with WSL Mirrored networking mode enabled.
The Hyper-V virtual switch should bind to the physical Wi-Fi adapter without
destabilizing the host, and WSL should start and function normally - exactly
as it does with networkingMode=NAT.
Actual Behavior
Two failure modes, both requiring a forced power-off (long-press power button)
to recover - a normal shutdown hangs:
Mode A - Bugcheck:
BugCheck 0x0000009F DRIVER_POWER_STATE_FAILURE
Arg1: 0x0000000000000003 (a device object has been blocking an IRP too long)
Arg2: 0xffff820a0474e060 (Physical Device Object of the stack)
Arg3: 0xffffe1874bd8f5d0 (nt!TRIAGE_9F_POWER)
Arg4: 0xffff820a198b9050 (the blocked IRP)
MEMORY.DMP is written.
Mode B - Hard hang:
No bugcheck, no dump. System becomes unresponsive; Event 6008 records
"the previous system shutdown ... was unexpected".
After forced reboot the adapter recovers, usually after a period of degraded
connectivity (WLAN-AutoConfig event 4003 "limited connectivity").
Event-log timeline from a crashed boot (Mirrored mode):
15:02:33 Kernel-Boot events (system start)
15:02:36 VfpExt / Hyper-V-VmSwitch burst: 40 events <- mirrored-mode switch binding
15:02:38 Netwaw18 7010 "Wi-Fi Driver Enabled"
15:02:46 CRASH (13 s after boot)
15:02:48 MEMORY.DMP written; WER 1001 reports 0x9F
15:02:50 VfpExt / Hyper-V-VmSwitch burst: 22 events <- WSL auto-start
15:03:23 WLAN-AutoConfig 4003 "limited connectivity"
15:03:24 Netwaw18 8000 "Miniport Halt" + re-initialization
Kernel dump stack - the power IRP is blocked in the miniport stop path:
nt!PopIrpWorker
Wdf01000!FxPkgFdo::DispatchDeviceSetPower
Wdf01000!FxPkgPnp::PowerGotoDx
WifiCx!EvtCxDevicePostSelfManagedIoSuspendEx
-> DeletePortTypes -> NetAdapterStop
ndis!ndisPnPStopDevice / ndisPnPRemoveDevice
tcpip!FlpWaitForMiniportToReturnTransmittedPackets <- blocked indefinitely
Diagnostic Logs
KEY FINDING 1 - Controlled experiment (only variable is networkingMode):
Mirrored : boot-time VfpExt/VmSwitch burst = 40 events, overlapping BE200
driver initialization -> crash at EVERY boot
NAT : boot-time burst = 2 events -> completely stable
(no crash, no miniport halt, no 4003 across multiple reboots,
sleep/wake cycles and WSL start/stop cycles)
KEY FINDING 2 - Not driver-version specific:
Reproduced on both 24.70.0.3 (Netwaw18.sys) and 24.80.0.2 (Netwaw20.sys).
KEY FINDING 3 - Not hardware:
HP Support Assistant wireless diagnostic = PASS; the adapter works fine
under NAT mode. The failure is deterministic and purely software-triggered.
Workaround: networkingMode=NAT is completely stable.
Attached files:
- Kernel minidump from a crash (9.8 MB)
- System event log export (CSV) covering multiple crash timestamps
Root-cause analysis: Mirrored mode binds the Hyper-V extensible switch to the
PHYSICAL Wi-Fi adapter during boot, forcing the BE200 miniport through a
stop/remove cycle that races with the adapter's own initialization. The driver
never returns outstanding TX packets, so the power IRP never completes.
Requests:
- WSL team: can the vSwitch binding to physical adapters be deferred until
the host network stack is fully initialized at boot, instead of racing
with adapter initialization? - Intel: Netwaw*.sys should complete power IRPs within the timeout even
with in-flight TX packets.
- Lingua principale
- C++
- Stelle
- 34.4k
- Fork
- 1.9k
- Merge medio
- 1g 23h
- PR unite (30g)
- 166
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di microsoft/WSL
-
feature wsl2
Difficoltà 2/5 1-3 ore Idoneità per principianti 80/100
microsoft/WSL#42306 · 3 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
feature
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
microsoft/WSL#42114 · 3 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
feature kernel wsl2
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
microsoft/WSL#41107 · 3 commenti · 1 reazione ·
I maintainer di solito rispondono entro 1 giorno
-
feature kernel
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
microsoft/WSL#41054 · 9 commenti · 1 reazione ·
I maintainer di solito rispondono entro 1 giorno
-
feature GPU
Difficoltà 1/5 1-3 ore Idoneità per principianti 70/100
microsoft/WSL#13592 · 4 commenti ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di microsoft/WSL
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
HarperFast/rocksdb-js#1131 ·
I maintainer di solito rispondono entro 1 giorno
-
area/daemon bug good first issue platform/linux priority/p2
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
ToshiNamura/Deimos#5 ·
-
needs-format
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
Niko1221/Strata#6251 · 1 commento ·
I maintainer di solito rispondono entro 5 giorni
-
[Bug]: NP 管理器文件编辑器里删除键无效Apertabug
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
metasequoiaime/msime#11666 ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
patrick-hudson/put.gd-desktop#1679 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno