Screen starts glitching after hibernation

inxi:

System:
  Kernel: 5.18.0-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.1.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=21c7fde8-1bef-4f82-abc8-364dad2d6848 rw [email protected]
    quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
    systemd.unified_cgroup_hierarchy=1
    resume=UUID=59131e58-a432-49f0-bae1-aebf3325230e loglevel=3
  Desktop: Tabby info: latte-dock wm: kwin_x11 dm: SDDM
    Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Laptop System: HP product: OMEN by HP Laptop 15-dc1xxx v: N/A
    serial: <filter> Chassis: type: 10 serial: <filter>
  Mobo: HP model: 8574 v: 21.17 serial: <filter> UEFI: AMI v: F.22
    date: 05/03/2021
Battery:
  ID-1: BAT0 charge: 53.2 Wh (100.0%) condition: 53.2/53.2 Wh (100.0%)
    volts: 17.3 min: 15.4 model: HP Primary type: Li-ion serial: N/A
    status: full
CPU:
  Info: model: Intel Core i7-9750H socket: BGA1440 (U3E1) note: check
    bits: 64 type: MT MCP arch: Coffee Lake family: 6 model-id: 0x9E (158)
    stepping: 0xD (13) microcode: 0xF0
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
    L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB
    L3: 12 MiB desc: 1x12 MiB
  Speed (MHz): avg: 1168 high: 1201 min/max: 800/4500 base/boost: 3960/8300
    scaling: driver: intel_pstate governor: powersave volts: 1.1 V
    ext-clock: 100 MHz cores: 1: 1100 2: 1100 3: 1161 4: 1183 5: 1144 6: 1200
    7: 1200 8: 1201 9: 1200 10: 1186 11: 1145 12: 1200 bogomips: 62399
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: spec_store_bypass
    mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2
    mitigation: Enhanced IBRS, IBPB: conditional, RSB filling
  Type: srbds mitigation: TSX disabled
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA TU106M [GeForce RTX 2060 Mobile] vendor: Hewlett-Packard
    driver: nvidia v: 515.43.04 alternate: nouveau,nvidia_drm non-free: 515.xx+
    status: current (as of 2022-05) arch: Turing pcie: gen: 1 speed: 2.5 GT/s
    lanes: 8 link-max: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.0
    chip-ID: 10de:1f11 class-ID: 0300
  Device-2: Lite-On HP Wide Vision HD Camera type: USB driver: uvcvideo
    bus-ID: 1-6:3 chip-ID: 04ca:707f class-ID: 0e02 serial: <filter>
  Display: x11 server: X.Org v: 21.1.3 with: Xwayland v: 22.1.2
    compositors: 1: kwin_x11 2: Tabby driver: X: loaded: nvidia gpu: nvidia
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 143 s-size: 341x191mm (13.43x7.52")
    s-diag: 391mm (15.39")
  Monitor-1: DP-2 res: 1920x1080 hz: 60 dpi: 142
    size: 344x194mm (13.54x7.64") diag: 395mm (15.55") modes: N/A
  OpenGL: renderer: NVIDIA GeForce RTX 2060/PCIe/SSE2
    v: 4.6.0 NVIDIA 515.43.04 direct render: Yes
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: Hewlett-Packard
    driver: snd_hda_intel v: kernel
    alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3
    chip-ID: 8086:a348 class-ID: 0403
  Device-2: NVIDIA TU106 High Definition Audio vendor: Hewlett-Packard
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 8
    link-max: lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:10f9 class-ID: 0403
  Sound Server-1: ALSA v: k5.18.0-zen1-1-zen running: yes
  Sound Server-2: PulseAudio v: 15.0 running: no
  Sound Server-3: PipeWire v: 0.3.51 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Hewlett-Packard driver: r8169 v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 3c:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: eno1 state: down mac: <filter>
  Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 3d:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlo1 state: up mac: <filter>
  IF-ID-1: docker0 state: down mac: <filter>
  IF-ID-2: tailscale0 state: unknown speed: -1 duplex: full mac: N/A
Bluetooth:
  Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8
    bus-ID: 1-7:4 chip-ID: 8087:0029 class-ID: e001
  Report: bt-adapter ID: hci0 rfk-id: 1 state: up address: <filter>
RAID:
  Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci
    v: 3.0 port: 5020 bus-ID: 00:17.0 chip-ID: 8086:282a rev: N/A
    class-ID: 0104
Drives:
  Local Storage: total: 1.84 TiB used: 59.52 GiB (3.2%)
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
    model: MZVLB1T0HBLR-000H1 size: 953.87 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: HPS0NEXF temp: 43.9 C scheme: GPT
  SMART: yes health: PASSED on: 249d 0h cycles: 829
    read-units: 50,721,188 [25.9 TB] written-units: 53,054,602 [27.1 TB]
  ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 EVO 1TB
    family: based SSDs size: 931.51 GiB block-size: physical: 512 B
    logical: 512 B sata: 3.3 speed: 6.0 Gb/s type: SSD serial: <filter>
    rev: 1B6Q temp: 35 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 238d 1h cycles: 496
    written: 2.2 TiB Pre-Fail: reallocated sector: 99 threshold: 10
Partition:
  ID-1: / raw-size: 896.9 GiB size: 896.9 GiB (100.00%)
    used: 59.52 GiB (6.6%) fs: btrfs block-size: 4096 B dev: /dev/sda2
    maj-min: 8:2
  ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.45%)
    used: 563 KiB (0.2%) fs: vfat block-size: 512 B dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 896.9 GiB size: 896.9 GiB (100.00%)
    used: 59.52 GiB (6.6%) fs: btrfs block-size: 4096 B dev: /dev/sda2
    maj-min: 8:2
  ID-4: /var/log raw-size: 896.9 GiB size: 896.9 GiB (100.00%)
    used: 59.52 GiB (6.6%) fs: btrfs block-size: 4096 B dev: /dev/sda2
    maj-min: 8:2
  ID-5: /var/tmp raw-size: 896.9 GiB size: 896.9 GiB (100.00%)
    used: 59.52 GiB (6.6%) fs: btrfs block-size: 4096 B dev: /dev/sda2
    maj-min: 8:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 31.23 GiB used: 512 KiB (0.0%)
    priority: 100 dev: /dev/zram0
  ID-2: swap-2 type: partition size: 34.36 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/sda3 maj-min: 8:3
Sensors:
  System Temperatures: cpu: 58.0 C pch: 52.0 C mobo: N/A gpu: nvidia
    temp: 53 C
  Fan Speeds (RPM): N/A
Info:
  Processes: 327 Uptime: 8m wakeups: 1 Memory: 31.23 GiB
  used: 4.51 GiB (14.4%) Init: systemd v: 251 tool: systemctl Compilers:
  gcc: 12.1.0 Packages: pacman: 1478 lib: 369 Shell: garuda-inxi (sudo)
  default: Bash v: 5.1.16 running-in: tabby inxi: 3.3.16
Garuda (2.6.3-2):
  System install date:     2021-07-24
  Last full system update: 2022-05-31
  Is partially upgraded:   No
  Relevant software:       tlp NetworkManager
  Windows dual boot:       Yes
  Snapshots:               Timeshift (maybe)
  Failed units:

Hi community,

I have this slight problem with Garuda KDE Dragonized - every time I hibernate my laptop (I almost never turn it off, only restart it after updates), some time after restoring from hibernation the screen starts glitching, sometimes on it's own, sometimes when invoking e.g. alt+tab. I can't really describe it, it's just white screen with shades of gray, however I am still able to control the system, so when I can hit the logout button I am able to log in again and the glitch is gone.

The problem is, it doesn't work all the time as I am not always able to hit the logout button :slight_smile:

I then get an error saying that the screen effects were restarted due to graphics glitch. I also get sometimes error on screen that the hardware was changed (it was not) during the hibernation, results doubtful.

It's not really that big a problem, but I am developing on my laptop and when this occurs, lines of code not saved or already commited to git could be lost, so any help with this issue would be greatly appreciated.

1 Like

Try disabling the kwin compositor prior to suspending. Testing alternate kernels would also be a good idea. Also, check that your bios is up to date.

2 Likes