segfault, one distro not launching at all, various errors in logs of the other distro, wsl crashed and burned

[jtabox]

Windows Version

Microsoft Windows [Version 10.0.22621.2861]

WSL Version

2.0.14.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.133.1-1

Distro Version

Ubuntu 22.04

Other Software

Docker Desktop for Windows 4.26.1 (131620)

Repro Steps

I've been getting multiple errors since I installed the latest WSL version (2.0.14.0). I'm not sure how connected they are, but it's been an absolute disaster trying to get anything to run. Any help would be appreciated.

1. Trying to launch a WSL distro (Ubuntu 22.04) with wsl -d distro-name, that was working fine a few hours ago suddenly will not work.
2. My other (default) Ubuntu 22.04 distro is working so far but I'm getting various error messages and strange malfunctions.

Expected Behavior

Expected my distros to run.

Actual Behavior

1. Trying to run the distro I get this in the command prompt:

  wsl -d nvc-1211-d
Catastrophic failure
Error code: Wsl/Service/CreateInstance/E_UNEXPECTED

The debug console shows this:

[ 2291.280807] init[5875]: segfault at 1 ip 000000000032209a sp 00007ffccec184e8 error 4 in init[29d000+151000]
[ 2291.280812] Code: e9 cb 01 00 00 cc cc cc cc cc cc cc cc cc cc cc 48 85 d2 41 0f 95 c0 40 f6 c7 07 0f 84 1c 01 00 00 48 85 d2 0f 84 13 01 00 00 <40> 38 37 75 0b 48 89 f8 48 89 d1 e9 0e 01 00 00 48 8d 47 01 48 89
[ 2291.280816] potentially unexpected fatal signal 11.
[ 2291.280817] CPU: 21 PID: 5875 Comm: init Not tainted 5.15.133.1-microsoft-standard-WSL2 #1
[ 2291.280818] RIP: 0033:0x32209a
[ 2291.280821] Code: e9 cb 01 00 00 cc cc cc cc cc cc cc cc cc cc cc 48 85 d2 41 0f 95 c0 40 f6 c7 07 0f 84 1c 01 00 00 48 85 d2 0f 84 13 01 00 00 <40> 38 37 75 0b 48 89 f8 48 89 d1 e9 0e 01 00 00 48 8d 47 01 48 89
[ 2291.280822] RSP: 002b:00007ffccec184e8 EFLAGS: 00010206
[ 2291.280823] RAX: 000000007fffffff RBX: 0000000000000001 RCX: 000000000022e484
[ 2291.280824] RDX: 000000007fffffff RSI: 0000000000000000 RDI: 0000000000000001
[ 2291.280825] RBP: 0000000000000000 R08: 0000000000000001 R09: 00000000ffffffff
[ 2291.280825] R10: 00000000ffffffff R11: 0000000000000000 R12: 0000000000214157
[ 2291.280826] R13: 0000000000000001 R14: 000000007fffffff R15: 0000000000000073
[ 2291.280826] FS:  00000000004078a0 GS:  0000000000000000
[ 2291.280922] WSL (1) ERROR: InitEntryUtilityVm:2266: Init has exited. Terminating distribution

I have logs for this error which I'm uploading.

---

2. My other (default) distro runs for now, but when I tried running sudo apt update previously it stuck completely and I had to Ctrl+C and wsl --shutdown to get it back up working. I'm also getting this error message when I log in: Processing fstab with mount -a failed., but doing sudo mount -a when I'm logged in works.

Furthermore, there's various errors in this distro when running dmesg:

[    0.324235] PCI: Fatal: No config space access function found

[    6.189073] FS-Cache: Duplicate cookie detected
[    6.189462] FS-Cache: O-cookie c=00000004 [p=00000002 fl=222 nc=0 na=1]
[    6.189875] FS-Cache: O-cookie d=00000000b4eb1103{9P.session} n=00000000bde8bb2e
[    6.190465] FS-Cache: O-key=[10] '34323934393337383933'
[    6.190823] FS-Cache: N-cookie c=00000005 [p=00000002 fl=2 nc=0 na=1]
[    6.191402] FS-Cache: N-cookie d=00000000b4eb1103{9P.session} n=00000000acd4ff94
[    6.191906] FS-Cache: N-key=[10] '34323934393337383933'

[    7.075423] WSL (2) ERROR: UtilCreateProcessAndWait:687: /bin/mount failed with status 0x4000
[    7.076192] WSL (2) ERROR: ConfigMountFsTab:2579: Processing fstab with mount -a failed.

[   10.488372] WSL (1) ERROR: ConfigApplyWindowsLibPath:2527: open /etc/ld.so.conf.d/ld.wsl.conf
[   10.488373]  failed 2
[   10.490260] WSL (3) ERROR: UtilCreateProcessAndWait:665: /bin/mount failed with 2
[   10.490978] WSL (1) ERROR: UtilCreateProcessAndWait:687: /bin/mount failed with status 0xff00

There's also this warning below:

[   10.134515] WSL (1) WARNING: /usr/share/zoneinfo/Europe/Stockholm not found. Is the tzdata package installed?

But if I go to that directory manually when logged in, the file is there:

╰─ l /usr/share/zoneinfo/Europe/Stockholm
Permissions Size User Group Date Modified    Name
.rw-r--r--  1.9k root root  2023-05-20 01:26  /usr/share/zoneinfo/Europe/Stockholm

I don't have any logs for those errors because I'm not sure how to trigger those. But I can upload logs and hope the errors pop up.

Diagnostic Logs

WslLogs-2023-12-17_13-15-42.zip

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

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. Thank you!

Open similar issues:

• SEGFAULT on WSL for simple binary that doesn't SEGFAULT on std. Ubuntu or with valgrind (#2546), similarity score: 0.78
• WSL in 22h2 causes total system crash (#8977), similarity score: 0.76

Closed similar issues:

• WSL Crashes and Exits (#8250), similarity score: 0.76
• WSL2 crashes at startup (#4768), similarity score: 0.75
• WSL2 randomly crashes (#7368), similarity score: 0.75

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

[OneBlue]

Thank you for reporting this @jtabox. Does setting:

[wsl2]
safeMode=true

And then running wsl --shutdown allow the distribution to start ?

I wonder if this could be caused by your systemd configuration.

[jtabox]

@OneBlue thanks for replying.
I can't try your suggestion unfortunately because I ended up deleting the distro and using another PC to accomplish my task.

I've actually ended up completely removing all the options under the [experimental] section of .wslconfig, meaning no autoMemoryReclaim or sparseVhd. Which is a pity, because they seem to be useful options and I'd really like to have them on. But in general, my feeling is (i.e. I have no concrete evidence to back this up) that ever since I've started "playing" with those two options, I've been having some minor or major issue with WSL regularly. So I've reached a point where I'm hesitant to install stuff in WSL and use it, because of fear it'll suddenly stop working.

Anyway, rant off. You mention my systemd configuration as a probable cause, what exactly is that? You mean the .wslconfig/wsl.conf files? Or something else?

[OneBlue]

Ah too bad. My thinking was that there could have been something in the distro's system configuration that caused init to crash and so setting safemode=true would disable systemd in that distro.

Thank you for following up though. Closing since we can't investigate deeper since the repro is gone. Feel free to reopen if it happens again.