Terminal in VSCode (OS release) doesn't render properly after suspend

medicineman25 · 2020-01-02 03:04:54

Kernel: 4.19.91-1-lts
WM: Fluxbox 1.3.7
Comp: Picom-7.5-2
X: xf86-video-vesa-2.4.0-2
Nvidia-lts: 440.44

As you can see here:

The terminal is not rendering properly after suspension, requiring a close and re-open of VSCode (no system reboot required).

Anyone else having this issue?

Last edited by medicineman25 (2020-01-02 03:05:22)

seth · 2020-01-02 08:24:27

X: xf86-video-vesa-2.4.0-2

hardly… hopefully.

If you're using the nvidia blob (please post your xorg log) this is "normal" - at least assuming the section is rendered in opengl. The VRAM isn't stored in RAM during the S3 and lost after a brief while due to the power cut.
You'll then get a garbled texture full of random bytes. Forcing a re-render of that texture is usually sufficient. (Commonly happens with browsers but be aware that picom/compton is susceptible to the same problem if operating on the GL backend) and in rare cases this can crash the process.

I'm unfortunately not aware of any mitigation.

V1del · 2020-01-02 11:53:56

Nvidia has added some systemd integrations that should help with properly resuming from suspend, try enabling

systemctl enable nvidia-hibernate.service nvidia-resume.service nvidia-suspend.service

Ref: https://download.nvidia.com/XFree86/Lin … ement.html

medicineman25 · 2020-01-03 02:59:29

If you're using the nvidia blob (please post your xorg log) this is "normal" - at least assuming the section is rendered in opengl. The VRAM isn't stored in RAM during the S3 and lost after a brief while due to the power cut.
You'll then get a garbled texture full of random bytes. Forcing a re-render of that texture is usually sufficient. (Commonly happens with browsers but be aware that picom/compton is susceptible to the same problem if operating on the GL backend) and in rare cases this can crash the process.

yeh damn, that is a shame. I can confirm that it's still happening with picom disabled. Also /var/log/Xorg.0.log shows nothing at all.

Just out of curiousity, how the heck did you know that? I know that knowledge comes with time and patience but you guys seem to know way more about Linux than I knew there was to know. Are there good known sources for gaining advanced in-depth knowledge of Linux systems beyond the usual sysadmin style lecture?

Nvidia has added some systemd integrations that should help with properly resuming from suspend, try enabling
systemctl enable nvidia-hibernate.service nvidia-resume.service nvidia-suspend.service
Ref: https://download.nvidia.com/XFree86/Lin … ement.html

They look shiny. Tried them and unfortunately it only half fixes the problem. The texture is rendering *better* but still grey and blocky i.e. no RGB glitter. This is obviously expected given that I'm not actually suspending anything from RAM as mentioned by Seth

Also just btw, for some reason video doesn't resume properly at all when using the suspend interface. I had to reboot, hibernate does seem to allow for resuming. Not really an issue for me as I'm happy to use system suspend for now.

Thanks for the help guys, I now realize that power mgmt is an aspect of my system I have ignorantly neglected as other parts are also not resuming as expected, like pulseaudio. I'll have to spend more time on that moving forward.

Last edited by medicineman25 (2020-01-03 03:16:34)

seth · 2020-01-03 08:51:47

Just out of curiousity, how the heck did you know that?

Been there, seen that. Googled a lot (as the link V1del posted and that I now incorperated to my knowledge suggests: it's previously been worse)

video doesn't resume properly at all when using the suspend interface

W/ or w/o picom running? Or is this "video" like "citizen kane in mpv/vlc or youtube"?

I had to reboot, hibernate does seem to allow for resuming

This indicates the system was in hibernation - either explicitly, though https://www.freedesktop.org/software/sy … -hibernate or because of a parallel windows installation in fast-boot mode (which you want to disable, https://wiki.archlinux.org/index.php/Du … _Start-Up)

medicineman25 · 2020-01-04 12:48:14

Just out of curiousity, how the heck did you know that?
Been there, seen that. Googled a lot (as the link V1del posted and that I now incorperated to my knowledge suggests: it's previously been worse)

haha yeh cool... dat knowledge base

video doesn't resume properly at all when using the suspend interface
W/ or w/o picom running? Or is this "video" like "citizen kane in mpv/vlc or youtube"?

Apologies, the screen remains black and tapping the power button does nothing to wake it up. The laptop appears responsive, the keys light up just like when it normally wakes up.

I had to reboot, hibernate does seem to allow for resuming
This indicates the system was in hibernation - either explicitly, though https://www.freedesktop.org/software/sy … -hibernate or because of a parallel windows installation in fast-boot mode (which you want to disable, https://wiki.archlinux.org/index.php/Du … _Start-Up)

Yes I have a dual boot system, I'll look into disabling fast-boot

Thanks again!!

Arch Linux

#1 2020-01-02 03:04:54

Terminal in VSCode (OS release) doesn't render properly after suspend

#2 2020-01-02 08:24:27

Re: Terminal in VSCode (OS release) doesn't render properly after suspend

#3 2020-01-02 11:53:56

Re: Terminal in VSCode (OS release) doesn't render properly after suspend

#4 2020-01-03 02:59:29

Re: Terminal in VSCode (OS release) doesn't render properly after suspend

#5 2020-01-03 08:51:47

Re: Terminal in VSCode (OS release) doesn't render properly after suspend

#6 2020-01-04 12:48:14

Re: Terminal in VSCode (OS release) doesn't render properly after suspend

Board footer