vinci
20 September 2024 10:15
1
After a recent update I’ve issues with my system completely freezing after waking up a display. I have no screen locking in place, it’s really just the “Turn off screen” option from the power management section.
What’s weird about that issue is that the display seems to come back on, at least sometimes. I can seen the screen appearing but following that the system is completely unresponsive for at least a minute. Sometimes it then finds its way back…
I’m sorry I know that’s not a lot to go on, but I really have no clue where to start looking.
Can you provide your
garuda-inxi
As per the forum template
2 Likes
vinci
20 September 2024 12:26
3
Sure.
System:
Kernel: 6.10.10-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=08444cbe-8e6a-4ca6-be59-025001d9562e rw rootflags=subvol=@
quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
ibt=off
Desktop: KDE Plasma v: 6.1.5 tk: Qt v: N/A info: frameworks v: 6.6.0
wm: kwin_wayland with: krunner vt: 1 dm: SDDM Distro: Garuda
base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: WS C422 PRO_SE v: Rev 1.xx
serial: <superuser required> part-nu: ASUS_MB_KBLX
uuid: <superuser required> UEFI: American Megatrends v: 3302
date: 11/04/2020
CPU:
Info: model: Intel Xeon W-2125 bits: 64 type: MT MCP arch: Skylake level: v4
note: check process: Intel 14nm family: 6 model-id: 0x55 (85) stepping: 4
microcode: 0x2007006
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 4 MiB desc: 4x1024 KiB
L3: 8.2 MiB desc: 1x8.2 MiB
Speed (MHz): avg: 2013 high: 4500 min/max: 1200/4500 scaling:
driver: intel_pstate governor: powersave cores: 1: 1200 2: 4500 3: 1200
4: 1200 5: 1200 6: 4404 7: 1200 8: 1200 bogomips: 63999
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Baffin [Radeon RX 550 640SP / 560/560X] vendor: XFX Pine
driver: amdgpu v: kernel arch: GCN-4 code: Arctic Islands process: GF 14nm
built: 2016-20 pcie: gen: 3 speed: 8 GT/s lanes: 8 ports:
active: DP-1,HDMI-A-1 empty: DVI-D-1 bus-ID: 65:00.0 chip-ID: 1002:67ff
class-ID: 0300 temp: 52.0 C
Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.2
compositor: kwin_wayland driver: X: loaded: amdgpu unloaded: modesetting
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu d-rect: 4520x1920
display-ID: 0
Monitor-1: DP-1 pos: right res: 1080x1920 size: N/A modes: N/A
Monitor-2: HDMI-A-1 pos: primary,left res: 3440x1440 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
wayland: drv: radeonsi x11: drv: radeonsi
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.2.2-arch1.1
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 550 Series (radeonsi
polaris11 LLVM 18.1.8 DRM 3.57 6.10.10-zen1-1-zen) device-ID: 1002:67ff
memory: 1.95 GiB unified: no display-ID: :1.0
API: Vulkan v: 1.3.295 layers: 3 device: 0 type: discrete-gpu name: AMD
Radeon RX 550 Series (RADV POLARIS11) driver: mesa radv v: 24.2.2-arch1.1
device-ID: 1002:67ff surfaces: xcb,xlib,wayland device: 1 type: cpu
name: llvmpipe (LLVM 18.1.8 256 bits) driver: mesa llvmpipe
v: 24.2.2-arch1.1 (LLVM 18.1.8) device-ID: 10005:0000
surfaces: xcb,xlib,wayland
Audio:
Device-1: Intel 200 Series PCH HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel alternate: snd_soc_avs bus-ID: 00:1f.3
chip-ID: 8086:a2f0 class-ID: 0403
Device-2: AMD Baffin HDMI/DP Audio [Radeon RX 550 640SP / 560/560X]
vendor: XFX Pine driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s
lanes: 8 bus-ID: 65:00.1 chip-ID: 1002:aae0 class-ID: 0403
API: ALSA v: k6.10.10-zen1-1-zen status: kernel-api tools: N/A
Server-1: PipeWire v: 1.2.3 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel I210 Gigabit Network vendor: ASUSTeK driver: igb v: kernel
pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 4000 bus-ID: 04:00.0
chip-ID: 8086:1533 class-ID: 0200
IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Intel I210 Gigabit Network vendor: ASUSTeK driver: igb v: kernel
pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 05:00.0
chip-ID: 8086:1533 class-ID: 0200
IF: enp5s0 state: down mac: <filter>
IF-ID-1: docker0 state: down mac: <filter>
Info: services: NetworkManager,systemd-timesyncd
Drives:
Local Storage: total: 698.65 GiB used: 251.65 GiB (36.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 960 EVO 500GB
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 3B7QCXE7 temp: 47.9 C
scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 850 EVO 250GB
size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 3B6Q scheme: MBR
Partition:
ID-1: / raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 251.65 GiB (54.1%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 584 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 251.65 GiB (54.1%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 251.65 GiB (54.1%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 251.65 GiB (54.1%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 62.49 GiB used: 141.2 MiB (0.2%)
priority: 100 comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 8
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 68.0 C mobo: N/A gpu: amdgpu temp: 52.0 C
Fan Speeds (rpm): N/A gpu: amdgpu fan: 955
Info:
Memory: total: 64 GiB note: est. available: 62.49 GiB
used: 13.99 GiB (22.4%)
Processes: 320 Power: uptime: 2h 22m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 24.97 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1801 libs: 455 tools: pamac,paru Compilers:
clang: 18.1.8 gcc: 14.2.1 Shell: garuda-inxi default: fish v: 3.7.1
running-in: konsole inxi: 3.3.35
Garuda (2.6.26-1):
System install date: 2023-07-04
Last full system update: 2024-09-20 ↻
Is partially upgraded: No
Relevant software: snapper(custom) NetworkManager dracut
Windows dual boot: No/Undetected
Failed units:
I have two systems where this is occurring. The have the same LC-Power monitor in common, once connected with HDMI, once with display port.
Have you tried running in x11 to see if it persists?
1 Like
vinci
20 September 2024 12:50
5
Doesn’t look like it does. On X11 everything seems fine, no freezes.
vinci
20 September 2024 13:12
7
Just did to boot into X11 and back to Wayland.
1 Like
If its fine in x11 stay using that
vinci
20 September 2024 15:23
9
Sadly X11 does not feel as snappy. If possible I’d rather solve this issue. I’m curious to see if more people will run into this.
squidf
21 September 2024 07:37
10
Have you looked at what has been updated? If one is the kernel, have you tried to boot on an older one?
I remember getting a black screen once and booting on a previous snapshot and updating again with garuda-update solved the issue.
My little 2 cents.
1 Like
Try the lts kernel by running :
sudo pacman -S linux-lts linux-lts-headers
Believe me, this has solved many sleep wake related issues for in the past. Wouldn’t hurt to try, would it ?
2 Likes
vinci
23 September 2024 12:34
12
For whatever reason that seemed to have solved my issue… Thanks
1 Like
system
Closed
25 September 2024 12:34
13
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.