WSL crashes when building application #12238
Assignees
Labels
kernel
WSL kernel
Comments
Logs are required for review from WSL teamIf this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. How to collect WSL logsDownload and execute collect-wsl-logs.ps1 in an administrative powershell prompt: 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 View similar issuesPlease 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:
Closed similar issues:
|
|
WslLogs-2024-11-04_14-57-59.zip |
Diagnostic information |
Diagnostic information |
|
Thank you for reporting this @MirChamb3r. I indeed see a kernel panic in the logs: |
|
I think this is a likely dup of #12089, but I will leave this issue open while I look closer |
|
Thanks for looking into it. It does seem to be the same or closely related. I also ran a Windows memory diagnostic and it reported no errors as well. |
|
@MirChamb3r are you using an AMD processor? |
|
@elsaco no I'm using an intel processor. |
|
Just a general question, would updating the kernel or even rolling back the kernel possibly fix this? |
|
There's unlikely to be any harm in trying, especially v6.1 (which is what's currently on that guide, though it should probably be updated). Though just so you know WSL running v6.6 doesn't currently pull in kernel modules automatically. So if you're using something like Docker, it might be broken until you revert back to an older version or compile the kernel with the relevant modules built in. |
|
Well, here's more info for you. You were right; it didn't solve the problem, but it didn't just straight-up crash WSL this time. As you can see, I'm building this for an arm processor, and now I'm seeing that perhaps the compiler we use in our toolkit is having trouble with the newer kernel. |
You can downgrade back to the stock kernel by just removing the Very odd it's now resulting in a segfault from |
|
Building a kernel (or large project) on WSL shouldn't crash it. I did a quick test using kernel build outputzImage info: WSL info, using To capture more feedback add @MirChamb3r are you using an ARM based system or just building ARM software on an Intel system? |
|
Sorry I should clarify, this is built using a toolkit our company uses to build our own Linux-based system which goes on our own device (with an arm processor in this instance). |
|
So good news, I figured out how to fix this. Long story short, updating the BIOS then rebuilding my application worked. I should say what led me to this was the fact that the crashes were somewhat random and the fact that the CPU usage was always so high right before WSL would crash. Building the kernel and cppunit easily maxed out my CPU so that's where the instability would cause a crash. And that's what led me to investigate the microcode issue. |
|
Glad to hear this fixed it for you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Windows Version
Microsoft Windows [Version 10.0.22631.4391]
WSL Version
2.3.24.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.153.1-2
Distro Version
Ubuntu 22.04
Other Software
Building company code on WSL so unfortunately can't share all however crashes happened when building these third party applications:
Linux Kernel version 4.x
CppUnit version 1.9.8
Repro Steps
Doing a build the application starts to build a package such as the Linux kernel or the CppUnit library and it'll crash WSL with error code 1. When rebooting WSL I found out that the files that it was building would get corrupted and need to be removed and redownloaded along with the toolkit I was using to build the application.
This was working fine for about a year then about 3 weeks ago this happened. I was able to get it to build again the first time by redownloading all the files and then rebuilding the application; but, that is no longer working.
I have spun up a new instance of WSL from scratch, downloaded the application again and got the same exact failure on a different drive on my PC.
Expected Behavior
Should build fine with no errors or crashes
Actual Behavior
Crashes and corrupts files mid build.
Diagnostic Logs
The log that gets caught when it crashes:
HyperVLog.txt
WslLogs-2024-11-04_14-57-59.zip
The log in the terminal that gets logged is just error code 1 when it crashes:
[process exited with code 1 (0x00000001)]
You can now close this terminal with Ctrl+D, or press Enter to restart.
The text was updated successfully, but these errors were encountered: