Kernel BUG at fs/namei.c:844 (try_to_unlazy) after 9P/virtiofs channel disruption causes WSL2 crash

[poriscui]

Windows Version

Microsoft Windows [版本 10.0.26200.8894]

WSL Version

WSL 版本: 2.9.4.0 内核版本: 6.18.35.2-1 WSLg 版本: 1.0.79 MSRDC 版本: 1.2.7214 Windows 版本: 10.0.26200.8894

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

6.18.35.2-microsoft-standard-WSL2 (gcc 13.2.0, #1 SMP PREEMPT_DYNAMIC Wed Jun 17 23:14:00 UTC 2026)

Distro Version

Debian 11 (bullseye)

Other Software

Docker Engine 29.6.2 (running natively inside WSL2, not Docker Desktop)
Docker Buildx (docker-container driver, BuildKit v0.31.2)
.wslconfig: networkingMode=mirrored, dnsTunneling=true, memory=16G, autoMemoryReclaim=Gradual

Repro Steps

1. Configure .wslconfig with networkingMode=mirrored and dnsTunneling=true
2. Create a Docker buildx builder with docker-container driver:
   docker buildx create --name czy-builder --driver docker-container --use
   --platform linux/amd64,linux/arm64 --config ./buildkitd.toml
3. Run a heavy cross-platform Docker build (ARM64 FreeSWITCH compilation):
   docker buildx build --builder czy-builder --platform linux/arm64
   --progress=plain --target release -t freeswitch:release.v1.10.7-arm64
   -f Dockerfile.freeswitch.arm --load .
4. After ~10-15 minutes of heavy build I/O, observe DNS resolution failures in dmesg:
   "WSL (135) ERROR: CheckConnection: getaddrinfo() failed: -5"
5. Shortly after, the 9P/virtiofs channel disrupts:
   "Exception: Operation canceled @p9io.cpp:258 (AcceptAsync)"
6. WSL receives SIGTERM and shuts down uncleanly.
7. After WSL restart, running ls or any path lookup triggers a kernel BUG:
   "kernel BUG at fs/namei.c:844!"
   "Oops: invalid opcode: 0000 [Will this be Open Source? #1] SMP NOPTI"
   "RIP: 0010:try_to_unlazy+0xbc/0xe0"
   Call trace: statx → vfs_statx → filename_lookup → path_lookupat → complete_walk → try_to_unlazy → BUG()
8. WSL crashes again.

Expected Behavior

After a 9P channel disruption and WSL restart, the kernel should properly clean up VFS dentry cache state. Path lookup operations (ls, statx) should work normally without triggering a kernel BUG/oops. The VFS state machine should not enter an invalid state after 9P/virtiofs reconnection.

Actual Behavior

After 9P/virtiofs channel disruption and subsequent WSL restart, the VFS dentry cache retains corrupted/stale state from the unclean shutdown. When any process performs a path lookup (e.g., ls invoking statx syscall), the RCU-walk to refcounted-walk transition via try_to_unlazy() detects an invalid nameidata state (RAX=4, expected LOOKUP_RCU=1) and triggers kernel BUG at fs/namei.c:844. This causes a kernel oops (invalid opcode 0000 [#1]) which destabilizes the entire WSL VM, leading to cascading Docker exec failures ("broken pipe" errors on /run/docker.sock) and eventual WSL crash.

Key evidence from dmesg/kern.log:

Pre-crash DNS failures (11 min before crash):

WSL (135) ERROR: CheckConnection: getaddrinfo() failed: -5
9P channel disruption:

Exception: Operation canceled @p9io.cpp:258 (AcceptAsync)
systemd-journald: Received SIGTERM from PID 1 (systemd-shutdow)
EXT4-fs (sdd): unmounting filesystem
Unclean shutdown confirmed on restart:

EXT4-fs (sdd): recovery complete
systemd-journald: File ... corrupted or uncleanly shut down, renaming and replacing
Kernel BUG (the actual crash):

kernel BUG at fs/namei.c:844!
Oops: invalid opcode: 0000 [#1] SMP NOPTI
CPU: 7 UID: 0 PID: 13059 Comm: ls Not tainted 6.18.35.2-microsoft-standard-WSL2
RIP: 0010:try_to_unlazy+0xbc/0xe0
RAX: 0000000000000004 RBX: ... RCX: 0000000000000000
Call Trace:
complete_walk+0x43/0xb0
path_lookupat+0x9c/0x180
filename_lookup+0xe2/0x1e0
vfs_statx+0x69/0x100
do_statx+0x48/0x80
__x64_sys_statx+0xa6/0xf0
do_syscall_64+0x73/0x990
entry_SYSCALL_64_after_hwframe+0x76/0x7e
Cascading Docker failures (symptom, not root cause):

Error running exec ... in container: exec attach failed:
error attaching stdout stream: write unix /run/docker.sock->@: write: broken pipe
The root cause chain: 9P channel disruption → unclean shutdown → corrupted dentry cache on restart → try_to_unlazy() kernel BUG → WSL crash.

Diagnostic Logs

Jul 28 09:04:46 Czy dockerd[337]: time="2026-07-28T09:04:46.905085596+08:00" level=error msg="Error running exec 91a72f1c5fe04ee3273788755f4670c7f624c1d032740cd8690635f5dcafa82e in container: exec attach failed: error attaching stdout stream: write unix /run/docker.sock->@: write: broken pipe"
Jul 28 09:05:42 Czy dockerd[337]: time="2026-07-28T09:05:42.465224432+08:00" level=error msg="Error running exec 6f12c1b3d78b133f6cc80ba405726883abd176c2be70ed2015ea47defbc87b24 in container: exec attach failed: error attaching stdout stream: write unix /run/docker.sock->@: write: broken pipe"
Jul 28 09:05:43 Czy dockerd[337]: time="2026-07-28T09:05:43.120458637+08:00" level=error msg="Error running exec c1f8e87b5ae2ca7f7aa9a7c6a80f4c245ee5d9430b7f741c9a6901907bce195e in container: exec attach failed: error attaching stdout stream: write unix /run/docker.sock->@: write: broken pipe"
Jul 28 09:05:49 Czy dockerd[337]: time="2026-07-28T09:05:49.145823298+08:00" level=error msg="Error running exec cb2fb83734dca1bbd9537d1ac31f61ec50d7e62ff8d4826b5f71c32537dbfc98 in container: exec attach failed: error attaching stdout stream: write unix /run/docker.sock->@: write: broken pipe"
Jul 28 09:05:54 Czy dockerd[337]: time="2026-07-28T09:05:54.021885442+08:00" level=error msg="Error running exec d136143004c8e7ef628eb18097c1dac598e0be7babb8d1ec9e76cc7c46d4d120 in container: exec attach failed: error attaching stdout stream: write unix /run/docker.sock->@: write: broken pipe"
Jul 28 09:05:54 Czy dockerd[337]: time="2026-07-28T09:05:54.467607410+08:00" level=error msg="Error running exec 04add2ac4e6cd6c77a6deca49bec1f223b08494a838d4a7b1b28c46e80ffdc3a in container: exec attach failed: error attaching stdout stream: write unix /run/docker.sock->@: write: broken pipe"
Jul 28 09:05:58 Czy dockerd[337]: time="2026-07-28T09:05:58.708408283+08:00" level=error msg="Error running exec 86dc9e36f946e642cc82b46b078e5ff9cddd7b660a0fafac35597ec52929260f in container: exec attach failed: error attaching stdout stream: write unix /run/docker.sock->@: write: broken pipe"
Jul 28 09:06:05 Czy dockerd[337]: time="2026-07-28T09:06:05.272092583+08:00" level=error msg="Error running exec 3cf6496bfe8c79fb3566ca81a22a117dc4610f859b50b9d6d00f259ae91dff55 in container: exec attach failed: error attaching stdout stream: write unix /run/docker.sock->@: write: broken pipe"
Jul 28 09:06:08 Czy dockerd[337]: time="2026-07-28T09:06:08.798769249+08:00" level=error msg="Error running exec 70dfd6b4195c2cc44b9f56bd5f2b5474b8098a48f5fec299a09b0f35803ff8e5 in container: exec attach failed: error attaching stdout stream: write unix /run/docker.sock->@: write: broken pipe"
Jul 28 09:06:09 Czy dockerd[337]: time="2026-07-28T09:06:09.200837648+08:00" level=error msg="Error running exec d1e544dcebf5e87b5c585d97f857fb111ceba6543cb1381cd7ce85ef0a70c466 in container: exec attach failed: error attaching stdout stream: write unix /run/docker.sock->@: write: broken pipe"
Jul 28 09:06:09 Czy dockerd[337]: time="2026-07-28T09:06:09.580226610+08:00" level=error msg="Error running exec d04200f79434933d2d03deba28e44fc0355a024a3aab730231fa4ac35e34c8f4 in container: exec attach failed: error attaching stdout stream: write unix /run/docker.sock->@: write: broken pipe"
Jul 28 09:06:10 Czy dockerd[337]: time="2026-07-28T09:06:10.629489394+08:00" level=error msg="Error running exec 02f04a6a347eb1973feb83f44f40ebdf87cc94f845eef990ef0680f020eb3786 in container: exec attach failed: error attaching stdout stream: write unix /run/docker.sock->@: write: broken pipe"
Jul 28 09:06:14 Czy dockerd[337]: time="2026-07-28T09:06:14.034117897+08:00" level=error msg="Error running exec 38d1fe09b7d9e30f0dca094e46c66616414e4527177c2ed95f175d5b5bd030c2 in container: exec attach failed: error attaching stdout stream: write unix /run/docker.sock->@: write: broken pipe"
Jul 28 09:06:14 Czy dockerd[337]: time="2026-07-28T09:06:14.390404874+08:00" level=error msg="Error running exec 3b986fd642f4b21292edd6906d16a4fe6985dcd3805d6f5faeef827234c89b98 in container: exec attach failed: error attaching stdout stream: write unix /run/docker.sock->@: write: broken pipe"
Jul 28 09:06:18 Czy dockerd[337]: time="2026-07-28T09:06:18.613831694+08:00" level=error msg="Error running exec 7f2a89381ef0fdddfb3f54e946a6ef281554ecc213d8078575b48580e351c047 in container: exec attach failed: error attaching stdout stream: write unix /run/docker.sock->@: write: broken pipe"
Jul 28 09:06:19 Czy dockerd[337]: time="2026-07-28T09:06:19.019165881+08:00" level=error msg="Error running exec 7bb0f06cdefb048095ea5f84645267e1b9c85843469bd376fbdf1b4949498337 in container: exec attach failed: error attaching stdout stream: write unix /run/docker.sock->@: write: broken pipe"
Jul 28 09:06:31 Czy dockerd[337]: time="2026-07-28T09:06:31.450865656+08:00" level=error msg="Error running exec b1213c9d315b7bbf8892c7bf5dc5abfbff91bc94e6b2cb281335c29bce9521fe in container: exec attach failed: error attaching stdout stream: write unix /run/docker.sock->@: write: broken pipe"
Jul 28 09:06:31 Czy dockerd[337]: time="2026-07-28T09:06:31.934497341+08:00" level=error msg="Error running exec 175072500b4a3f30c40aa6e40344a0debbe8f71bbfaebb6124ff76a90ce17a5f in container: exec attach failed: error attaching stdout stream: write unix /run/docker.sock->@: write: broken pipe"
Jul 28 09:06:40 Czy dockerd[337]: time="2026-07-28T09:06:40.474017132+08:00" level=error msg="Error running exec 7ac15c62005a8501b93883731b5e2aaf55edb080e0ec696ba0ce7c10093fbafc in container: exec attach failed: error attaching stdout stream: write unix /run/docker.sock->@: write: broken pipe"
Jul 28 09:06:42 Czy dockerd[337]: time="2026-07-28T09:06:42.106268910+08:00" level=error msg="Error running exec 48437c668b6eebe1a36dae009cc55c8ded66bbe1b5deb58c941a271f2d10560b in container: exec attach failed: error attaching stdout stream: write unix /run/docker.sock->@: write: broken pipe"
Jul 28 09:06:55 Czy dockerd[337]: time="2026-07-28T09:06:55.559441102+08:00" level=error msg="Error running exec 0631fe16cbc2ce1feba5285ee7f7f7d61d7e43a17e274c6ac90f4aab493cc191 in container: exec attach failed: error attaching stdout stream: write unix /run/docker.sock->@: write: broken pipe"
Jul 28 09:07:02 Czy dockerd[337]: time="2026-07-28T09:07:02.733350827+08:00" level=error msg="Error running exec 8980210a373f249fce5b386f0e01ed760a287869d30535f528e8cb90ef17de81 in container: exec attach failed: error attaching stdout stream: write unix /run/docker.sock->@: write: broken pipe"
Jul 28 09:07:07 Czy dockerd[337]: time="2026-07-28T09:07:07.283785971+08:00" level=error msg="Error running exec 5ec1431c97a6f745e8a92b8073e78b22eb9ee03fcb035de0239814f17be98774 in container: exec attach failed: error attaching stdout stream: write unix /run/docker.sock->@: write: broken pipe"
Jul 28 09:07:08 Czy dockerd[337]: time="2026-07-28T09:07:08.378367489+08:00" level=error msg="Error running exec 7e655a4aba120455ef9f6a39040890cbacc280761da2edb9876c377ffaa58611 in container: exec attach failed: error attaching stdout stream: write unix /run/docker.sock->@: write: broken pipe"
Jul 28 09:07:08 Czy dockerd[337]: time="2026-07-28T09:07:08.793486111+08:00" level=error msg="Error running exec b8095fca8668a32a0a8ab5c910cc18cbdf197ea1e935f52aa7344ca5dea5d5e3 in container: exec attach failed: error attaching stdout stream: write unix /run/docker.sock->@: write: broken pipe"
Jul 28 09:07:12 Czy dockerd[337]: time="2026-07-28T09:07:12.025938374+08:00" level=error msg="Error running exec 2d0073a0fc957920eeff4e82b9a84e8dc14c1ff19a55edfb62d95b76f23be1fc in container: exec attach failed: error attaching stdout stream: write unix /run/docker.sock->@: write: broken pipe"
Jul 28 09:07:12 Czy dockerd[337]: time="2026-07-28T09:07:12.429610737+08:00" level=error msg="Error running exec d2107f8d37127b9512595ec82d1a641feaa952066e007b8ff088ec3c005e9c80 in container: exec attach failed: error attaching stdout stream: write unix /run/docker.sock->@: write: broken pipe"
Jul 28 09:07:12 Czy dockerd[337]: time="2026-07-28T09:07:12.797375886+08:00" level=error msg="Error running exec 34d3e2344d828622b81a68a54eb4dc88900c18ef82685f0479a70fbad95cd2a6 in container: exec attach failed: error attaching stdout stream: write unix /run/docker.sock->@: write: broken pipe"
Jul 28 09:07:17 Czy dockerd[337]: time="2026-07-28T09:07:17.979649012+08:00" level=error msg="Error running exec 4ddc657f651a15f7d016ddd09d597ffcb2907b18f61b96730e8654f75612812c in container: exec attach failed: error attaching stdout stream: write unix /run/docker.sock->@: write: broken pipe"
Jul 28 09:07:19 Czy dockerd[337]: time="2026-07-28T09:07:19.088706104+08:00" level=error msg="Error running exec 137ff8b21cf835306d3931b2b34708f57d827fdda12b4fe380ed13edccf10d62 in container: exec attach failed: error attaching stdout stream: write unix /run/docker.sock->@: write: broken pipe"
Jul 28 09:07:32 Czy dockerd[337]: time="2026-07-28T09:07:32.469548095+08:00" level=error msg="Error running exec b484218100ebd8835e2265b8adbc63f24cefe72ebbeb7ad924416c550eb5969e in container: exec attach failed: error attaching stdout stream: write unix /run/docker.sock->@: write: broken pipe"
Jul 28 09:07:34 Czy dockerd[337]: time="2026-07-28T09:07:34.127541164+08:00" level=error msg="Error running exec 029185b96c0f6918c48b5c46d5c6ec5906a9c15bc692dafa8f78d36e496385f1 in container: exec attach failed: error attaching stdout stream: write unix /run/docker.sock->@: write: broken pipe"
Jul 28 09:07:36 Czy kernel: [ 1043.996863] ------------[ cut here ]------------
Jul 28 09:07:36 Czy kernel: [ 1043.998965] kernel BUG at fs/namei.c:844!
Jul 28 09:07:36 Czy kernel: [ 1043.999841] Oops: invalid opcode: 0000 [#1] SMP NOPTI
Jul 28 09:07:36 Czy kernel: [ 1044.000429] CPU: 7 UID: 0 PID: 13059 Comm: ls Not tainted 6.18.35.2-microsoft-standard-WSL2 #1 PREEMPT(none)
Jul 28 09:07:36 Czy kernel: [ 1044.001747] RIP: 0010:try_to_unlazy+0xbc/0xe0
Jul 28 09:07:36 Czy kernel: [ 1044.002640] Code: ff 84 c0 75 b8 81 63 38 ff fe ff ff 45 31 e4 48 c7 43 40 00 00 00 00 e8 32 bf d0 ff 44 89 e0 5b 41 5c 41 5d 5d c3 cc cc cc cc <0f> 0b 48 c7 03 00 00 00 00 48 c7 43 08 00 00 00 00 eb c8 0f 0b 66
Jul 28 09:07:36 Czy kernel: [ 1044.006124] RSP: 0018:ffffcec1a54d3ac0 EFLAGS: 00010246
Jul 28 09:07:36 Czy kernel: [ 1044.006538] RAX: 0000000000000004 RBX: ffffcec1a54d3b40 RCX: 0000000000000000
Jul 28 09:07:36 Czy kernel: [ 1044.007371] RDX: 0000000000000000 RSI: 000000000000002e RDI: ffffcec1a54d3b40
Jul 28 09:07:36 Czy kernel: [ 1044.008212] RBP: ffffcec1a54d3ad8 R08: 0000000000000064 R09: 0000000000003835
Jul 28 09:07:36 Czy kernel: [ 1044.009101] R10: 0000000000000002 R11: 00000002e4838045 R12: ffff88c8c97d4d80
Jul 28 09:07:36 Czy kernel: [ 1044.010116] R13: ffff88c8c97d4d80 R14: 0000000000000000 R15: ffffcec1a54d3c80
Jul 28 09:07:36 Czy kernel: [ 1044.011635] FS: 000072f8a06bd400(0000) GS:ffff88cad0186000(0000) knlGS:0000000000000000
Jul 28 09:07:36 Czy kernel: [ 1044.012606] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 28 09:07:36 Czy kernel: [ 1044.013214] CR2: 000072f8a0660060 CR3: 0000000135e41001 CR4: 0000000000b70ef0
Jul 28 09:07:36 Czy kernel: [ 1044.014043] Call Trace:
Jul 28 09:07:36 Czy kernel: [ 1044.014234]
Jul 28 09:07:36 Czy kernel: [ 1044.014456] complete_walk+0x43/0xb0
Jul 28 09:07:36 Czy kernel: [ 1044.015086] path_lookupat+0x9c/0x180
Jul 28 09:07:36 Czy kernel: [ 1044.015604] ? proc_pid_readlink+0x12d/0x1b0
Jul 28 09:07:36 Czy kernel: [ 1044.016224] filename_lookup+0xe2/0x1e0
Jul 28 09:07:36 Czy kernel: [ 1044.016538] ? do_readlinkat.part.0+0xa6/0x160
Jul 28 09:07:36 Czy kernel: [ 1044.017192] ? do_syscall_64+0x73/0x990
Jul 28 09:07:36 Czy kernel: [ 1044.017973] vfs_statx+0x69/0x100
Jul 28 09:07:36 Czy kernel: [ 1044.018429] do_statx+0x48/0x80
Jul 28 09:07:36 Czy kernel: [ 1044.018912] ? putname+0x63/0x80
Jul 28 09:07:36 Czy kernel: [ 1044.019289] ? __x64_sys_statx+0xb0/0xf0
Jul 28 09:07:36 Czy kernel: [ 1044.019607] ? __check_object_size+0x221/0x2c0
Jul 28 09:07:36 Czy kernel: [ 1044.019959] ? strncpy_from_user+0x2b/0x120
Jul 28 09:07:36 Czy kernel: [ 1044.020298] ? getname_flags.part.0+0x4b/0x1d0
Jul 28 09:07:36 Czy kernel: [ 1044.020709] ? getname_flags+0x3b/0x60
Jul 28 09:07:36 Czy kernel: [ 1044.021062] __x64_sys_statx+0xa6/0xf0
Jul 28 09:07:36 Czy kernel: [ 1044.021327] x64_sys_call+0x12a1/0x20f0
Jul 28 09:07:36 Czy kernel: [ 1044.021636] do_syscall_64+0x73/0x990
Jul 28 09:07:36 Czy kernel: [ 1044.022080] ? __x64_sys_statx+0xb0/0xf0
Jul 28 09:07:36 Czy kernel: [ 1044.022485] ? x64_sys_call+0x12a1/0x20f0
Jul 28 09:07:36 Czy kernel: [ 1044.022776] ? do_syscall_64+0x73/0x990
Jul 28 09:07:36 Czy kernel: [ 1044.023187] ? __x64_sys_readlink+0x29/0x40
Jul 28 09:07:36 Czy kernel: [ 1044.023504] ? x64_sys_call+0x1f7f/0x20f0
Jul 28 09:07:36 Czy kernel: [ 1044.023886] ? do_syscall_64+0x73/0x990
Jul 28 09:07:36 Czy kernel: [ 1044.024268] ? x64_sys_call+0x1f7f/0x20f0
Jul 28 09:07:36 Czy kernel: [ 1044.024600] ? do_syscall_64+0x73/0x990
Jul 28 09:07:36 Czy kernel: [ 1044.024954] ? irqentry_exit+0x3f/0x50
Jul 28 09:07:36 Czy kernel: [ 1044.025233] ? exc_page_fault+0x7f/0x170
Jul 28 09:07:36 Czy kernel: [ 1044.025591] entry_SYSCALL_64_after_hwframe+0x76/0x7e
Jul 28 09:07:36 Czy kernel: [ 1044.026153] RIP: 0033:0x72f8a0868d4a
Jul 28 09:07:36 Czy kernel: [ 1044.026618] Code: b8 ff ff ff ff 64 c7 00 16 00 00 00 e9 95 fd ff ff e8 9a 08 02 00 66 2e 0f 1f 84 00 00 00 00 00 41 89 ca b8 4c 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2e 41 89 c1 85 c0 74 0f 48 8b 05 10 31 0e 00
Jul 28 09:07:36 Czy kernel: [ 1044.028017] RSP: 002b:00007ffcc12d2ce8 EFLAGS: 00000246 ORIG_RAX: 000000000000014c
Jul 28 09:07:36 Czy kernel: [ 1044.028818] RAX: ffffffffffffffda RBX: 000072f8a0660dc8 RCX: 000072f8a0868d4a
Jul 28 09:07:36 Czy kernel: [ 1044.029396] RDX: 0000000000000100 RSI: 00007ffcc12db3e5 RDI: 00000000ffffff9c
Jul 28 09:07:36 Czy kernel: [ 1044.030406] RBP: 000000000000025e R08: 00007ffcc12d2cf0 R09: 000072f8a094cbe0
Jul 28 09:07:36 Czy kernel: [ 1044.031063] R10: 000000000000025e R11: 0000000000000246 R12: 00007ffcc12db3e5
Jul 28 09:07:36 Czy kernel: [ 1044.031696] R13: 0000000000000000 R14: 00007ffcc12db3e5 R15: 000072f8a0660dc8
Jul 28 09:07:36 Czy kernel: [ 1044.032356]
Jul 28 09:07:36 Czy kernel: [ 1044.032639] Modules linked in: nf_conntrack_netlink xt_conntrack xt_MASQUERADE xfrm_user xfrm_algo xt_set ip_set xt_addrtype nft_compat autofs4 br_netfilter bridge stp llc ip_tables tun
Jul 28 09:07:36 Czy kernel: [ 1044.033855] ---[ end trace 0000000000000000 ]---
Jul 28 09:07:36 Czy kernel: [ 1044.034410] RIP: 0010:try_to_unlazy+0xbc/0xe0
Jul 28 09:07:36 Czy kernel: [ 1044.034766] Code: ff 84 c0 75 b8 81 63 38 ff fe ff ff 45 31 e4 48 c7 43 40 00 00 00 00 e8 32 bf d0 ff 44 89 e0 5b 41 5c 41 5d 5d c3 cc cc cc cc <0f> 0b 48 c7 03 00 00 00 00 48 c7 43 08 00 00 00 00 eb c8 0f 0b 66
Jul 28 09:07:36 Czy kernel: [ 1044.037417] RSP: 0018:ffffcec1a54d3ac0 EFLAGS: 00010246
Jul 28 09:07:36 Czy kernel: [ 1044.037883] RAX: 0000000000000004 RBX: ffffcec1a54d3b40 RCX: 0000000000000000
Jul 28 09:07:36 Czy kernel: [ 1044.038526] RDX: 0000000000000000 RSI: 000000000000002e RDI: ffffcec1a54d3b40
Jul 28 09:07:36 Czy kernel: [ 1044.039300] RBP: ffffcec1a54d3ad8 R08: 0000000000000064 R09: 0000000000003835
Jul 28 09:07:36 Czy kernel: [ 1044.039957] R10: 0000000000000002 R11: 00000002e4838045 R12: ffff88c8c97d4d80
Jul 28 09:07:36 Czy kernel: [ 1044.040543] R13: ffff88c8c97d4d80 R14: 0000000000000000 R15: ffffcec1a54d3c80
Jul 28 09:07:36 Czy kernel: [ 1044.041234] FS: 000072f8a06bd400(0000) GS:ffff88cad0186000(0000) knlGS:0000000000000000
Jul 28 09:07:36 Czy kernel: [ 1044.042344] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 28 09:07:36 Czy kernel: [ 1044.043141] CR2: 000072f8a0660060 CR3: 0000000135e41001 CR4: 0000000000b70ef0

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

If this is a networking issue, please use .\collect-wsl-logs.ps1 -LogProfile networking instead, following the instructions in Collect WSL logs for networking issues

Once completed please upload the output files to this GitHub issue.

See Collect WSL logs (recommended method).

If you choose to email these logs instead of attaching them to the bug, please send them to wsl-gh-logs@microsoft.com with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.

[poriscui]

In fact, WSL runs normally when installed using WSL_2.7.3.0.x64.msi or any earlier release. After upgrading to a newer version, however, it crashes spontaneously even when no operations are performed.

[OneBlue]

Have you seen this before @chessturo ?