/init seems to crash when resume from S3 sleep.

[shigenobuokamoto]

Windows Version

Microsoft Windows [Version 10.0.26100.1150]

WSL Version

2.3.11.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

6.6.36.3-1

Distro Version

Ubuntu 24.04

Other Software

No response

Repro Steps

Windows into S3 sleep.
resume Windows.

Expected Behavior

return to previous state before sleep.

Actual Behavior

the WSL Distro crashes.
but, kernel is running.

[   30.465930] WSL (1) ERROR: ValidateMessageHeader:329: Protocol error: Received message size:
[   30.465945] 28, type: 7, sequence: 0. Expected type: 0, expected sequence: 2, channel: init
[   30.465972] WSL (2) ERROR: ValidateMessageHeader:329: Protocol error: Received message size:
[   30.476375] hv_utils: TimeSync IC version 4.0
[   30.485262] libc++abi:
[   30.485271] terminating due to uncaught exception of type wil::ResultException: Invalid argument @C:/__w/1/s/src/shared/inc\SocketChannel.h:331 (ValidateMessageHeader)

Diagnostic Logs

No response

[github-actions]

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 scipt will output the path of the log file once done.

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'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Open similar issues:

• WSL sometimes crashes when computer wakes from sleep (#9563), similarity score: 0.77
• WSL2 distro dies when the PC is sleeping (#8763), similarity score: 0.73

Closed similar issues:

• Wsl die after laptop sleep and can't be reopened (#9301), similarity score: 0.74
• Error 4294967295 after wake from hibernation on Surface Pro X / arm64 (#6259), similarity score: 0.73
• Cannot connect to WSL after waking computer from sleep (#9142), similarity score: 0.72

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[g2flyer]

i see same behavior after upgrading from 2.2.4 to 2.3.11; besides sleep (not surprisingly) also with hibernate: distros die (both wsl and wsl --system) but kernel (as of wsl --debug-shell) survives. reverting back to 2.2.4 (and hence older kernel) makes it work again ...
PS: this was on ubuntu 24.04 distro with wslg, systemd and gradual memory reclaim enabled, all running on win11 10.0.22631
BTW: issue also mentioned in 2.3.11 release discussion (#11789 (comment))

[shigenobuokamoto]

/emailed-logs

[github-actions]

Diagnostic information

Found '/emailed-logs', adding tag 'emailed-logs'

[rowleya]

I also get this happening now. It also seemed to happen randomly when I walked away and came back to my laptop...

[rowleya]

Here are my logs after just getting this. I ran the log collector just before hibernate, and then came back from hibernate and WSL had crashed, but the log collector was still running. Hope it helps!
WslLogs-2024-07-19_07-15-38.zip

[benhillis]

Thanks for reporting and all the logs above, @OneBlue this looks related to your socket protocol changes (or maybe those changes are catching something misbehaving). Could you please take a look?

[flyingllama87]

Same issue for me.

[ChrisHanlonCA]

I had the exact same log messages 6 times when doing hibernates and the problem went away when I did a full shutdown on the Windows computer. My log messages included

1. WSL (1) ERROR: ValidateMessageHeader:329: Protocol error: Received message size:
2. 28, type: 7, sequence: 0. Expected type: 0, expected sequence: 2, channel: init
3. WSL (2) ERROR: ValidateMessageHeader:329: Protocol error: Received message size:
4. hv_utils: TimeSync IC version 4.0
5. libc++abi:
6. terminating due to uncaught exception of type wil::ResultException: Invalid argument @C:/__w/1/s/src/shared/inc\SocketChannel.h:331 (ValidateMessageHeader)

[jamez70]

I'm having the same issue

[benhillis]

We have a fix for this we will be rolling out soon.

[shigenobuokamoto]

i have confirmed that this has been fixed in 2.3.12.

thanks so much WSL team.

[heartacker]

Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x8007019e
Error: 0x8007019e ??????? Linux ? Windows ????

Press any key to continue...

[jamez70]

I have installed 2.3.12 without any issues. The problem usually occurred overnight for me so I will see tomorrow morning if the terminals are still open.

[pmyers]

Updated to 2.3.12 via wsl --update --pre-release and I did not see the WSL2 guest OS crash (in my case Fedora) following a resume from S3. Thank you for the quick fix on this one 👍

[Pvtsameerkhaan]

wsl problem not solve

[jamez70]

Solved for me. Hasn't crashed since

[rowleya]

Solved for me too since the 2.3.12 update (not tried the one just released yet)