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

Windows 11 - Laptop hangs when sleep mode is triggered after WSL terminal opened #7891

Open
1 of 2 tasks
mikeszczygiel opened this issue Jan 4, 2022 · 8 comments
Open
1 of 2 tasks

Comments

@mikeszczygiel
Copy link

mikeszczygiel commented Jan 4, 2022

Version

Windows 11 Version 21H2 (OS Build 22000.376)

WSL Version

  • WSL 2
  • WSL 1

Kernel Version

5.10.16

Distro Version

Ubuntu 20.04

Other Software

No response

Repro Steps

  • Upgrade laptop to Windows 11
  • Enter sleep mode - observe: no issue
  • Open WSL terminal, manually enter sleep mode (power button)
    • Observe: laptop hangs until force shutdown
  • Downgrade to Windows 10 - Version 10.0.19043.1415
    • Observe: no WSL/sleep issues

Expected Behavior

  • Open WSL terminal, manually enter sleep mode (power button)
    • Observe: laptop goes to sleep normally

Actual Behavior

Diagnostic Logs

No response

@mikeszczygiel mikeszczygiel changed the title Windows 11 hangs when sleep mode is triggered after WSL2 terminal opened Windows 11 - Laptop hangs when sleep mode is triggered after WSL terminal opened Jan 4, 2022
@acarrillo
Copy link

acarrillo commented Sep 25, 2022

I have noticed something similar on Windows 11 and it's quite maddening. I did not notice this when I was still running Windows 10. My CPU usage skyrockets after I try to 'resume' from a sleep, and my WSLg terminal emulator (guake) becomes frozen and unresponsive. Running wsl --shutdown from a new terminal hangs forever.

This is what my CPU usage due to WSL looks like during this event; my laptop fan hates it and the bottom of my laptop burns!!:

image

I experience this frequently after a long laptop 'sleep'.

@cibelewatt
Copy link

Having the same issue here!

@Yves-air
Copy link

Same/similar issues, all related to sleep mode while a WSL2 is running (Win11, Ubuntu 20.04, Dell XPS 15 9520).

@martinfibigergmail
Copy link

wsl freezes after even a short sleep. Hibernation works. XPS 15 9520. W11.
have to do settings/installed apps/wsl -> advanced -> reset
after that it works.
I'm using docker desktop which freezes too as it is built on top of wsl.

@jerryabramson
Copy link

I am seeing a somewhat tangential issue, but I think it may help triage the issue.

When you see the issue, are you using Windows Terminal or some other command-line terminal?

In my case, it is Windows Terminal (Preview) that is causing the hang/fan to spin up. It also causes my external mouse (which has a driver, and has special mouse bindings for WT) to stop working, while inside of WT. Once I move the mouse outside of WT, it 'wakes up.'

I normally use WT for both PowerShell 7 (7.3) and WSL (Debian and/or Oracle Linux.

I also use WT for Cygwin64 and Git-bash.

@Yves-air
Copy link

I was using WT, but definitely not preview (v1.16.10262.0).

I've switched my computer to Linux since, no more problems!

@yc0
Copy link

yc0 commented Feb 24, 2023

wsl freezes after even a short sleep. Hibernation works. XPS 15 9520. W11. have to do settings/installed apps/wsl -> advanced -> reset after that it works. I'm using docker desktop which freezes too as it is built on top of wsl.

If you want to keep your data, 'Reset' is not working. It will erase your data definitely.

@studiozandra
Copy link

studiozandra commented Dec 20, 2023

wsl freezes after even a short sleep. Hibernation works. XPS 15 9520. W11. have to do settings/installed apps/wsl -> advanced -> reset after that it works. I'm using docker desktop which freezes too as it is built on top of wsl.

Crashes after wake from sleep. Hibernation does not work for me. (Windows 11 Pro, i7, 40GB RAM, 2023-10 Cumulative Update (KB5031358)) Task Manager shows 12 processes for WSL, and over 100 instances of conhost.exe running, I assume it's each time VS Code tries to reconnect:
image

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

No branches or pull requests

8 participants