microsoft
hv_netvsc eth0: nvsp_rndis_pkt_complete error status: 2
Windows Version
Windows-Version: 10.0.26100.3624
WSL Version
2.5.6.0
Are you using WSL 1 or WSL 2?
- [x] WSL 2
- [ ] WSL 1
Kernel Version
6.6.84.1-1
Distro Version
Ubuntu 24.04 noble
Other Software
wsl --version
WSL-Version: 2.5.6.0
Kernelversion: 6.6.84.1-1
WSLg-Version: 1.0.66
MSRDC-Version: 1.2.6074
Direct3D-Version: 1.611.1-81528511
DXCore-Version: 10.0.26100.1-240331-1435.ge-release
Windows-Version: 10.0.26100.3624
Repro Steps
dmesg | grep hv_netvsc
[wsl2]
networkingMode=bridged
vmSwitch=bridged
Expected Behavior
no errors
Actual Behavior
hv_netvsc 82c91f61-1e09-41bb-9602-ba7442566c01 eth0: nvsp_rndis_pkt_complete error status: 2
Diagnostic Logs
No response
Logs are required for review from WSL team
If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.
How to collect WSL logs
Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1
The script will output the path of the log file once done.
If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here
Once completed please upload the output files to this Github issue.
Click here for more info on logging If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Diagnostic information
.wslconfig found
Custom kernel command line found: 'fsck.mode=force fsck.repair=yes sysctl.vm.swappiness=1'
Detected appx version: 2.5.6.0
Detected user visible error: Wsl/Service/E_UNEXPECTED
Detected user visible error: Wsl/Service/E_UNEXPECTED
Detected user visible error: Wsl/Service/E_UNEXPECTED
Detected user visible error: Wsl/Service/E_UNEXPECTED
Detected user visible error: Wsl/Service/E_UNEXPECTED
Detected user visible error: Wsl/Service/E_UNEXPECTED
A workaround seems to be setting
/usr/sbin/ethtool -K eth0 tcp-segmentation-offload off
and the dmesg errors disappears until now.
This isn't an issue with WSL itself, I also see this on my Hyper-V VMs on Windows 11 10.0.26100.3775, with recent kernels (currently on 6.14.2). I ran into this first back on Windows 10.
I bisected it at the time, and the trouble started with torvalds/linux@bf9f1baa279f0758dc2297080360c5a616843927, which was merged with Linux 6.3. Building that commit such that HAVE_SKB_SMALL_HEAD_CACHE is not defined (either by patching out the #define or building with CONFIG_SLOB) makes the errors go away.
Would be great to see this fixed!
This seems to be fixed in 6.15-rc7, specifically by: https://github.com/torvalds/linux/commit/09db7a4d287d1a2bcfc04df023c103d1213a0518. I'm not seeing the error occur anymore after compiling this version for WSL. I have no idea when it could be expected for this fix to make its way down to here officially though.
@Malifox is entirely correct. I manually moved the changes from https://github.com/torvalds/linux/commit/09db7a4d287d1a2bcfc04df023c103d1213a0518 to the current branch of origin/linux-msft-wsl-6.6.y and the error goes away. Patch is attached.
