Maximilian Luz

@shadowrylander You can just pastebin the whole thing (or upload it as file here), better to have too much than too little. We'll probably only need the part involving suspend,...

@alturismo Please open a new issue or have a look at the other wifi issues (I currently don't have an overview over that topic, so not sure if there's already...

@shadowrylander Looks like `syncthing` is the problem: ``` Oct 04 19:08:49 surface kernel: Freezing user space processes ... Oct 04 19:08:49 surface kernel: Freezing of tasks failed after 20.003 seconds...

I can confirm that something's going on there, but I haven't had the time to look at it. On the SB2, (usually) the first resume takes a couple of seconds...

Okay, my immediate issue seems to be somehow caused by the dGPU hot-plug driver. When I remove this (and do not unload the modules in the sleep script) I can...

@chasecovello I'm currently working on the dGPU issue. Something in 5.2 changed and now it hangs. For me usually about 10s, occasionally requires a reboot though. The current solution for...

To add a bit on the second "bug". I wouldn't really describe it as a bug, but rather as an issue. The problem is likely the following: X-server/wayland/gnome/... somehow access...

Also happens on my SB2 with v5.0.9 and v5.1.2. Suspending on lid-close works fine, waking via power-button too. Looks like a regression in upstream?

I've had a look at this and apparently the GPE (ACPI) interrupt responsible for the lid does not get set up as wake source. I'm not sure why it has...

Still looking at how to best implement this, but I noticed that the GPE numbers are different on the Laptops: - `_L17` for Book 1, Book 2, Pro 4 and...