Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WSL2 process crash #11509

Closed
1 of 2 tasks
wiselyG opened this issue Apr 25, 2024 · 5 comments
Closed
1 of 2 tasks

WSL2 process crash #11509

wiselyG opened this issue Apr 25, 2024 · 5 comments
Labels

Comments

@wiselyG
Copy link

wiselyG commented Apr 25, 2024

Windows Version

Microsoft windows [10.0.19045.4291]

WSL Version

0.0.0.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.10.16

Distro Version

Ubuntu 22.04

Other Software

https://github.com/nimble-technology/nimble-miner-public.git

Repro Steps

mkdir $HOME/nimble
cd ~/nimble

git clone https://github.com/nimble-technology/nimble-miner-public.git

cd nimble-miner-public

make install

Expected Behavior

https://docs.nimble.technology/

Actual Behavior

process exit with code 1

Diagnostic Logs

No response

Copy link

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 wsl-gh-logs@microsoft.com 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!

Closed similar issues:

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

@wiselyG
Copy link
Author

wiselyG commented Apr 25, 2024

/emailed-logs

Copy link

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

@github-actions github-actions bot added the emailed-logs Logs have been emailed label Apr 25, 2024
@OneBlue
Copy link
Collaborator

OneBlue commented Apr 25, 2024

@wiselyG: Looks like the WSL VM is triple faulting:

Microsoft-Windows-Hyper-V-Worker		04-24-2024 22:59:57.252	"	"	"VmName: 	Virtual Machine
VmId: 	6CAE5CC5-50E0-4DCF-948C-0DF3136AE417
Rax: 	0x55D9E600B070
Rbx: 	0x1000
Rcx: 	0x1000
Rdx: 	0x1000
Rsp: 	0xFFFFC90002F37CC8
Rbp: 	0xFFFF8882BE230000
Rsi: 	0x55D9E600A070
Rdi: 	0xFFFF8882BE230000
R8: 	0x0
R9: 	0xFFFFFFFFFFFF0000
R10: 	0x0
R11: 	0x1
R12: 	0x1000
R13: 	0xFFFFC90002F37E60
R14: 	0xFFFFC90002F37E50
R15: 	0xFFFFFFFF82245520
Rip: 	0xFFFFFFFF817ABF9E
Rflags: 	0x40206
FpControlStatus: 	0x7F030000000000000000000000000000
XmmControlStatus: 	0x0000000000000000A01F0000FFFF0200
Cr0: 	0x80050033
Cr2: 	0x7F2DAF7B7010
Cr3: 	0x1800D8000
Cr4: 	0x350EA0
Cr8: 	0x1
Xfem: 	0x7
Dr0: 	0x0
Dr1: 	0x0
Dr2: 	0x0
Dr3: 	0x0
Dr6: 	0xFFFF0FF0
Dr7: 	0x400
Es: 	0x00000000000000000000000000000000
Cs: 	0x0000000000000000FFFFFFFF10009B20
Ss: 	0x0000000000000000FFFFFFFF180093C0
Ds: 	0x00000000000000000000000000000000
Fs: 	0x00E018B32D7F00000000000000000000
Gs: 	0x000088278388FFFF0000000000000000
Ldtr: 	0x00000000000000000000000000000000
Tr: 	0x0050210000FEFFFF6700000040008900
Idtr: 	0x000000000000FF0F0000000000FEFFFF
Gdtr: 	0x0000000000007F000030210000FEFFFF
Tsc: 	0xAB50F75C74
ApicBase: 	0xFEE00800
SysenterCs: 	0x10
SysenterEip: 	0x0
SysenterEsp: 	0x0"				19980	6524	1		00000000-0000-0000-0000-000000000000		

This can be caused by hardware issues. Can you try to run a memory check on your machine ?

Copy link
Contributor

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants