Problem with new monitor, crashes on specific program

Support Graphics & Display
1

Hello,
I have bought new monitor with upgrade to Monitor 4K Philips 288E2UAE/00 28’’ IPS 60Hz. (my previous monitor Full HD 144HZ no crashes, works good)
Everything works quite fine with new one, but now when I use my Android Studio and want to make let’s say massive operation like launch my phone and start the program or change entire Color Scheme to another on x11 screen freezes and I need to force to power off computer by button (it looks like it’s not fully compatible?) and on wayland program crashes
That was my topic one day, maybe it is related? Something was restarted because of monitor, crashes?

computer, linux info

System:
  Kernel: 6.4.16-5-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.4-x86_64
    root=UUID=758df14c-2163-4fe3-a0db-2a38fe4278d3 rw amd_pstate.enable=1
    amd_pstate=guided iommu=pt amd_pstate=active amd_pstate.shared_mem=1 quiet
    splash initcall_blacklist=acpi_cpufreq_init amd_pstate.enable=1
    amd_pstate=guided iommu=pt amd_pstate.shared_mem=1 apparmor=1
    security=apparmor udev.log_priority=3
  Desktop: GNOME v: 45.4 tk: GTK v: 3.24.41 wm: gnome-shell
    tools: gsd-screensaver-proxy dm: GDM v: 45.0.1 Distro: Manjaro
    base: Arch Linux
Machine:
  Type: Laptop System: HP product: HP Pavilion 15 Laptop PC v: N/A
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: HP model: 88D0 v: 78.31 serial: <superuser required>
    part-nu: 4H3T9EA#AKD uuid: <superuser required> UEFI: AMI v: F.23
    date: 10/05/2022
Battery:
  ID-1: BAT0 charge: 37.7 Wh (96.9%) condition: 38.9/38.9 Wh (100.0%)
    volts: 12.7 min: 11.3 model: HP Primary type: Li-ion serial: <filter>
    status: charging cycles: 94
CPU:
  Info: model: AMD Ryzen 7 5700U with Radeon Graphics bits: 64 type: MT MCP
    arch: Zen 2 gen: 3 level: v3 note: check built: 2020-22
    process: TSMC n7 (7nm) family: 0x17 (23) model-id: 0x68 (104) stepping: 1
    microcode: 0x8608104
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
    L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB L3: 8 MiB
    desc: 2x4 MiB
  Speed (MHz): avg: 1474 high: 4372 min/max: 400/4372 boost: enabled scaling:
    driver: amd-pstate governor: schedutil cores: 1: 1114 2: 1529 3: 1269 4: 4372
    5: 1114 6: 1114 7: 1114 8: 1114 9: 1114 10: 2618 11: 1114 12: 1114 13: 1543
    14: 1114 15: 1114 16: 1114 bogomips: 57518
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT enabled with STIBP
    protection
  Type: spec_rstack_overflow mitigation: safe RET
  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: Retpolines, IBPB: conditional, STIBP:
    always-on, RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Lucienne vendor: Hewlett-Packard driver: amdgpu v: kernel
    arch: GCN-5 code: Vega process: GF 14nm built: 2017-20 pcie: gen: 3
    speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s ports:
    active: HDMI-A-1,eDP-1 empty: DP-1 bus-ID: 04:00.0 chip-ID: 1002:164c
    class-ID: 0300 temp: 41.0 C
  Device-2: Luxvisions Innotech HP Wide Vision HD Camera driver: uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-3:3
    chip-ID: 30c9:000e class-ID: 0e02
  Display: x11 server: X.org v: 1.21.1.12 with: Xwayland v: 23.2.5
    compositor: gnome-shell driver: X: loaded: amdgpu
    unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
    gpu: amdgpu display-ID: :1 screens: 1
  Screen-1: 0 s-res: 5760x2160 s-size: <missing: xdpyinfo>
  Monitor-1: not-matched mapped: HDMI-A-0 pos: top-left res: 3840x2160
    dpi: 157 size: 621x341mm (24.45x13.43") diag: 708mm (27.89") modes: N/A
  Monitor-2: not-matched mapped: eDP pos: primary,bottom-r res: 1920x1080
    hz: 60 dpi: 142 size: 344x194mm (13.54x7.64") diag: 395mm (15.55") 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 x11:
    drv: radeonsi inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.0.2-manjaro1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon Graphics (radeonsi renoir
    LLVM 16.0.6 DRM 3.52 6.4.16-5-MANJARO) device-ID: 1002:164c memory: 500 MiB
    unified: no
Audio:
  Device-1: AMD Renoir Radeon High Definition Audio vendor: Hewlett-Packard
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    link-max: gen: 4 speed: 16 GT/s bus-ID: 04:00.1 chip-ID: 1002:1637
    class-ID: 0403
  Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: Hewlett-Packard
    driver: snd_rn_pci_acp3x v: kernel alternate: snd_pci_acp3x, snd_pci_acp5x,
    snd_pci_acp6x, snd_acp_pci, snd_rpl_pci_acp6x, snd_pci_ps,
    snd_sof_amd_renoir, snd_sof_amd_rembrandt pcie: gen: 3 speed: 8 GT/s
    lanes: 16 link-max: gen: 4 speed: 16 GT/s bus-ID: 04:00.5
    chip-ID: 1022:15e2 class-ID: 0480
  Device-3: AMD Family 17h/19h HD Audio vendor: Hewlett-Packard
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    link-max: gen: 4 speed: 16 GT/s bus-ID: 04:00.6 chip-ID: 1022:15e3
    class-ID: 0403
  Device-4: C-Media Thronmax MDrill One Pro
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 1-2.2:4 chip-ID: 0d8c:0080 class-ID: 0300
  API: ALSA v: k6.4.16-5-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.0.3 status: off with: pipewire-media-session
    status: active tools: pw-cli
  Server-3: PulseAudio v: 17.0 status: active with: pulseaudio-alsa
    type: plugin tools: pacat,pactl
Network:
  Device-1: Realtek RTL8852AE 802.11ax PCIe Wireless Network Adapter
    vendor: Hewlett-Packard driver: rtw89_8852ae v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 02:00.0 chip-ID: 10ec:8852
    class-ID: 0280
  IF: wlo1 state: up mac: <filter>
  Info: services: NetworkManager, systemd-networkd, systemd-timesyncd,
    wpa_supplicant
Bluetooth:
  Device-1: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB rev: 1.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-4:5 chip-ID: 0bda:2852
    class-ID: e001 serial: <filter>
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.2
    lmp-v: 11 status: discoverable: no pairing: no class-ID: 6c010c
Drives:
  Local Storage: total: 476.94 GiB used: 238.7 GiB (50.0%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: SK Hynix
    model: BC711 HFM512GD3JX013N size: 476.94 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: HPS1 temp: 34.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 476.64 GiB size: 468.09 GiB (98.21%)
    used: 238.7 GiB (51.0%) fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 312 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
  Kernel: swappiness: 5 (default 60) cache-pressure: 50 (default 100)
    zswap: yes compressor: zstd max-pool: 20%
  ID-1: swap-1 type: file size: 20 GiB used: 0 KiB (0.0%) priority: -2
    file: /swapfile
Sensors:
  System Temperatures: cpu: 47.9 C mobo: N/A gpu: amdgpu temp: 41.0 C
  Fan Speeds (rpm): fan-1: 0 fan-2: 0
Info:
  Memory: total: 32 GiB note: est. available: 30.68 GiB used: 6.76 GiB (22.0%)
  Processes: 466 Power: uptime: 8m states: freeze,mem,disk suspend: s2idle
    wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume
    image: 12.26 GiB services: gsd-power, power-profiles-daemon, upowerd
    Init: systemd v: 255 default: graphical tool: systemctl
  Packages: 1754 pm: pacman pkgs: 1749 libs: 506 tools: gnome-software,pamac
    pm: flatpak pkgs: 5 Compilers: clang: 16.0.6 gcc: 13.2.1 Shell: Zsh v: 5.9
    running-in: gnome-terminal inxi: 3.3.33


cpupower frequency-info                                                                                                                   1 ✘   
analyzing CPU 4:
  driver: amd-pstate
  CPUs which run at the same hardware frequency: 4
  CPUs which need to have their frequency coordinated by software: 4
  maximum transition latency: 20.0 us
  hardware limits: 400 MHz - 4.37 GHz
  available cpufreq governors: conservative ondemand userspace powersave performance schedutil
  current policy: frequency should be within 400 MHz and 4.37 GHz.
                  The governor "schedutil" may decide which speed to use
                  within this range.
  current CPU frequency: Unable to call hardware
  current CPU frequency: 2.27 GHz (asserted by call to kernel)
  boost state support:
    Supported: yes
    Active: yes
    AMD PSTATE Highest Performance: 255. Maximum Frequency: 4.37 GHz.
    AMD PSTATE Nominal Performance: 105. Nominal Frequency: 1.80 GHz.
    AMD PSTATE Lowest Non-linear Performance: 65. Lowest Non-linear Frequency: 1.11 GHz.
    AMD PSTATE Lowest Performance: 24. Lowest Frequency: 400 MHz.

x11

kwi 09 23:28:30 chris-15 systemd-fstab-generator[300]: Failed to create unit file '/run/systemd/generator/swapfile.swap', as it already exists. Duplicate entr>
kwi 09 23:28:30 chris-15 (sd-exec-[293]: /usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
kwi 09 23:28:29 chris-15 systemd-modules-load[323]: Failed to find module 'amd_pstate'
kwi 09 23:28:33 chris-15 bluetoothd[658]: src/device.c:set_wake_allowed_complete() Set device flags return status: Invalid Parameters
kwi 09 23:28:33 chris-15 kernel: amdgpu 0000:04:00.0: amdgpu: Secure display: Generic Failure.
kwi 09 23:28:33 chris-15 kernel: amdgpu 0000:04:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
kwi 09 23:28:51 chris-15 gdm-password][1368]: gkr-pam: unable to locate daemon control file
kwi 09 23:28:53 chris-15 systemd[1409]: Failed to start Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 203 and the job result is failed.
kwi 09 23:28:53 chris-15 systemd[1409]: Failed to start Application launched by gnome-session-binary.

when switch to wayland

kwi 09 23:28:30 chris-15 systemd-fstab-generator[300]: Failed to create unit file '/run/systemd/generator/swapfile.swap', as it already exists. Duplicate entr>
kwi 09 23:28:30 chris-15 (sd-exec-[293]: /usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
kwi 09 23:28:29 chris-15 systemd-modules-load[323]: Failed to find module 'amd_pstate'
kwi 09 23:28:33 chris-15 bluetoothd[658]: src/device.c:set_wake_allowed_complete() Set device flags return status: Invalid Parameters
kwi 09 23:28:33 chris-15 kernel: amdgpu 0000:04:00.0: amdgpu: Secure display: Generic Failure.
kwi 09 23:28:33 chris-15 kernel: amdgpu 0000:04:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
kwi 09 23:28:51 chris-15 gdm-password][1368]: gkr-pam: unable to locate daemon control file
kwi 09 23:28:53 chris-15 systemd[1409]: Failed to start Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 203 and the job result is failed.
kwi 09 23:28:53 chris-15 systemd[1409]: Failed to start Application launched by gnome-session-binary.
2

For one thing you are using a kernel that has been EOL (end-of-life, unsupported, dead) for over 6 months.

Install and boot into a supported kernel (like 6.6) and remove 6.4.

1 Like
3

Hello, thanks for advice.
I have done upgrade to 6.8 and it behaves differently, crash and need to login again.

░░ The job identifier is 1411 and the job result is failed.
kwi 10 10:01:25 chris-15 systemd[1396]: Failed to start GNOME XSettings service.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 1455 and the job result is failed.
kwi 10 10:01:31 chris-15 gdm-password][4719]: gkr-pam: unable to locate daemon control file
kwi 10 10:01:34 chris-15 systemd[1396]: Failed to start Application launched by gnome-session-binary.

during installation kernel:

UPGRADE LINUX
:: Running post-transaction hooks...
(1/4) Arming ConditionNeedsUpdate...
(2/4) Updating module dependencies...
(3/4) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux68.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.8-x86_64 -g /boot/initramfs-6.8-x86_64.img --microcode /boot/amd-ucode.img
==> Starting build: '6.8.4-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
^T  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [plymouth]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> ERROR: module not found: '(amd_pstate)'
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-6.8-x86_64.img'
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux68.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.8-x86_64 -g /boot/initramfs-6.8-x86_64-fallback.img -S autodetect --microcode /boot/amd-ucode.img
==> Starting build: '6.8.4-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [plymouth]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> ERROR: module not found: '(amd_pstate)'
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-6.8-x86_64-fallback.img'
==> WARNING: errors were encountered during the build. The image may not be complete.
error: command failed to execute correctly
(4/4) Updating Grub-Bootmenu
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-6.8-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-6.8-x86_64.img
Found initrd fallback image: /boot/initramfs-6.8-x86_64-fallback.img
Found linux image: /boot/vmlinuz-6.4-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-6.4-x86_64.img
Found initrd fallback image: /boot/initramfs-6.4-x86_64-fallback.img
Found linux image: /boot/vmlinuz-6.1-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-6.1-x86_64.img
Found initrd fallback image: /boot/initramfs-6.1-x86_64-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Adding boot menu entry for UEFI Firmware Settings ...
Root filesystem isn't btrfs
If you think an error has occurred, please file a bug report at "https://github.com/Antynea/grub-btrfs"
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
Found memtest86+ EFI image: /boot/memtest86+/memtest.efi
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done

Looks I have problems with daemon and modules like amd_pstate or WARNING: Possibly missing firmware for module: ‘aic94xx’.

That’s my /etc/default/grub

[...]
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash initcall_blacklist=acpi_cpufreq_init amd_pstate.enab>
GRUB_CMDLINE_LINUX="amd_pstate.enable=1 amd_pstate=guided iommu=pt amd_pstate=active amd_psta>

[...]

cpupower frequency-info      ✔ 
analyzing CPU 7:
  driver: amd-pstate
  CPUs which run at the same hardware frequency: 7
  CPUs which need to have their frequency coordinated by software: 7
  maximum transition latency: 20.0 us
  hardware limits: 400 MHz - 4.37 GHz
  available cpufreq governors: conservative ondemand userspace powersave performance schedutil
  current policy: frequency should be within 400 MHz and 4.37 GHz.
                  The governor "schedutil" may decide which speed to use
                  within this range.
  current CPU frequency: Unable to call hardware
  current CPU frequency: 4.33 GHz (asserted by call to kernel)
  boost state support:
    Supported: yes
    Active: yes
    AMD PSTATE Highest Performance: 255. Maximum Frequency: 4.37 GHz.
    AMD PSTATE Nominal Performance: 105. Nominal Frequency: 1.80 GHz.
    AMD PSTATE Lowest Non-linear Performance: 65. Lowest Non-linear Frequency: 1.11 GHz.
    AMD PSTATE Lowest Performance: 24. Lowest Frequency: 400 MHz.

greetings

4

Is there a reason to avoid the 6.6 LTS and instead only use the latest ?
(this will also ensure you need to switch it again within a few months)

In any case … our aim was just to get you in a supported state.

These would have all occurred regardless of the kernel.
You just happened to initiate mkinitcpio while installing the new kernel and saw them.

The first one could be remedied if desired by installing upd72020x-fw from the AUR if you really think you need that firmware (but you probably dont).

The ones produced during the fallback creating are simply all available ones that you dont have installed. Thats how the fallback creation works - it has nothing to do with the actual hardware its running on.

You can see about these here:
https://wiki.archlinux.org/title/Mkinitcpio#Possibly_missing_firmware_for_module_XXXX

The pstate output is likely because you have such an (invalid) entry in your mkinitcpio configuration. At /etc/mkinitcpio.conf or /etc/mkinitcpio.conf.d/*.

Please review the wiki page and/or related threads here for which modules you may want to include or omit.

idea - oh yeah … this could also indicate that you have unmanaged pacnews.

You can print them all with pacdiff -o

See the wiki entry here:

This is cut off … but from what I can tell you have duplicate and/or competing entries.
(for example pstate=active and pstate=guided cannot coexist … one must be used … maybe the last in this case ?)

Finally

Is pretty self-explanatory. Your root filesystem is not btrfs … and this is being printed probably because you have grub-btrfs installed instead of regular grub (should you?).

OK, so that was a lot to go over.
But I should also add I dont know if any of that is actually related to your monitor problem.

1 Like
5

What I’ve done:
pstate = active is deleted so guided works only.

pacdiff -o                                                                                                           127 ✘   
/etc/passwd.pacnew
/etc/shells.pacnew
/etc/gdm/custom.conf.pacsave
/etc/locale.gen.pacnew
/etc/default/grub.pacnew
/etc/pamac.conf.pacnew
/etc/pacman.conf.pacnew
/etc/pam.d/polkit-1.pacsave
/etc/default/useradd.pacnew

I have change /etc/mkinitcpio.conf
from

MODULES=("amd_pstate")

to

MODULES=(amd_pstate)

modinfo amd_pstate                                                                                                   127 ✘   
modinfo: ERROR: Module amd_pstate not found.

On last LTS version I had problems with AMD CPU. I’ve tried on 6.6 and the same effect occurs.
When I turn off my monitor everything works fine…
I tried my monitor on 30Hz, the same problem ;(
I don’t understand source of this problem unfortunately.
4k is not supported in linux manjaro?
I have a friend of mine with 2x 2k monitors on linux manjaro and it works.

EDIT:

sudo pacman -S optimus-manager

reinstall
KSCREEN, LIBSCREEN

Seems to work better, but still error occurs with crashes. Still need help with this.

Edit2 (additional information):
My computer without launching new monitor crashes the same way!
It didn’t occurs previously that often, but in fact when my computer was like running for one week from time to time it freezes and I needed to restart it, I think the source of the problem is not the additional monitor, but power management, but the true is when I launch my additional 4k monitor my battery decreased from 98% to 93% during my work with laptop + monitor(it is constantly loading). Does it give you any additional piece of information?

power info from console:

kwi 10 15:17:55 chris-15 gsd-power[1110]: unable to open file '/etc/dconf/db/site': Failed to open file “/etc/dconf/db/site”: open() failed: No such file or directory; expect degraded performance
kwi 10 15:17:55 chris-15 gsd-power[1110]: unable to open file '/etc/dconf/db/distro': Failed to open file “/etc/dconf/db/distro”: open() failed: No such file or directory; expect degraded performance
6

I am using 2 x 4k monitor with 2 nvidia-cards and nouveau as driver (with 30Hz)

That was expectable. Monitors are rarely susceptible to CPU crashes

7

Ok, so problem could be with power mangamenet + not enough voltage on time during massive CPU work.
I have found this:
https://wiki.archlinux.org/title/Ryzen
https://www.kernel.org/doc/html/v6.3/admin-guide/pm/amd-pstate.html
Unfortunately as far as I see ryzen controller is deprecated I can’t launch it.
I could use it ryzenadj, but totally I do not know what values I should setup here.

Ryzen Power Management adjust tool.

    -h, --help                            show this help message and exit

Options
    -i, --info                            Show information and most important power metrics after adjustment
    --dump-table                          Show whole power metric table before and after adjustment

Settings
    -a, --stapm-limit=<u32>               Sustained Power Limit         - STAPM LIMIT (mW)
    -b, --fast-limit=<u32>                Actual Power Limit            - PPT LIMIT FAST (mW)
    -c, --slow-limit=<u32>                Average Power Limit           - PPT LIMIT SLOW (mW)
    -d, --slow-time=<u32>                 Slow PPT Constant Time (s)
    -e, --stapm-time=<u32>                STAPM constant time (s)
    -f, --tctl-temp=<u32>                 Tctl Temperature Limit (degree C)
    -g, --vrm-current=<u32>               VRM Current Limit             - TDC LIMIT VDD (mA)
    -j, --vrmsoc-current=<u32>            VRM SoC Current Limit         - TDC LIMIT SoC (mA)
    --vrmgfx-current=<u32>                VRM GFX Current Limit - TDC LIMIT GFX (mA)
    --vrmcvip-current=<u32>               VRM CVIP Current Limit - TDC LIMIT CVIP (mA)
    -k, --vrmmax-current=<u32>            VRM Maximum Current Limit     - EDC LIMIT VDD (mA)
    -l, --vrmsocmax-current=<u32>         VRM SoC Maximum Current Limit - EDC LIMIT SoC (mA)
    --vrmgfxmax_current=<u32>             VRM GFX Maximum Current Limit - EDC LIMIT GFX (mA)
    -m, --psi0-current=<u32>              PSI0 VDD Current Limit (mA)
    --psi3cpu_current=<u32>               PSI3 CPU Current Limit (mA)
    -n, --psi0soc-current=<u32>           PSI0 SoC Current Limit (mA)
    --psi3gfx_current=<u32>               PSI3 GFX Current Limit (mA)
    -o, --max-socclk-frequency=<u32>      Maximum SoC Clock Frequency (MHz)
    -p, --min-socclk-frequency=<u32>      Minimum SoC Clock Frequency (MHz)
    -q, --max-fclk-frequency=<u32>        Maximum Transmission (CPU-GPU) Frequency (MHz)
    -r, --min-fclk-frequency=<u32>        Minimum Transmission (CPU-GPU) Frequency (MHz)
    -s, --max-vcn=<u32>                   Maximum Video Core Next (VCE - Video Coding Engine) (MHz)
    -t, --min-vcn=<u32>                   Minimum Video Core Next (VCE - Video Coding Engine) (MHz)
    -u, --max-lclk=<u32>                  Maximum Data Launch Clock (MHz)
    -v, --min-lclk=<u32>                  Minimum Data Launch Clock (MHz)
    -w, --max-gfxclk=<u32>                Maximum GFX Clock (MHz)
    -x, --min-gfxclk=<u32>                Minimum GFX Clock (MHz)
    -y, --prochot-deassertion-ramp=<u32>  Ramp Time After Prochot is Deasserted: limit power based on value, higher values does apply tighter limits after prochot is over
    --apu-skin-temp=<u32>                 APU Skin Temperature Limit    - STT LIMIT APU (degree C)
    --dgpu-skin-temp=<u32>                dGPU Skin Temperature Limit   - STT LIMIT dGPU (degree C)
    --apu-slow-limit=<u32>                APU PPT Slow Power limit for A+A dGPU platform - PPT LIMIT APU (mW)
    --skin-temp-limit=<u32>               Skin Temperature Power Limit (mW)
    --gfx-clk=<u32>                       Forced Clock Speed MHz (Renoir Only)
    --oc-clk=<u32>                        Forced Core Clock Speed MHz (Renoir and up Only)
    --oc-volt=<u32>                       Forced Core VID: Must follow this calcuation (1.55 - [VID you want to set e.g. 1.25 for 1.25v]) / 0.00625 (Renoir and up Only)
    --enable-oc                           Enable OC (Renoir and up Only)
    --disable-oc                          Disable OC (Renoir and up Only)
    --set-coall=<u32>                     All core Curve Optimiser
    --set-coper=<u32>                     Per core Curve Optimiser
    --set-cogfx=<u32>                     iGPU Curve Optimiser
    --power-saving                        Hidden options to improve power efficiency (is set when AC unplugged): behavior depends on CPU generation, Device and Manufacture
    --max-performance                     Hidden options to improve performance (is set when AC plugged in): behavior depends on CPU generation, Device and Manufacture

P-State Functions

WARNING: Use at your own risk!
By Jiaxun Yang <jiaxun.yang@flygoat.com>, Under LGPL.
Version: v0.14.0

For now I have reloaded amd_pstate (CPUs) to intelligent managing schedutil

sudo cpupower frequency -set--governor schedutil

cpupower frequency-info                                          ✔ 
analyzing CPU 10:
  driver: amd-pstate
  CPUs which run at the same hardware frequency: 10
  CPUs which need to have their frequency coordinated by software: 10
  maximum transition latency: 20.0 us
  hardware limits: 400 MHz - 4.37 GHz
  available cpufreq governors: conservative ondemand userspace powersave performance schedutil
  current policy: frequency should be within 400 MHz and 4.37 GHz.
                  The governor "schedutil" may decide which speed to use
                  within this range.
  current CPU frequency: Unable to call hardware
  current CPU frequency: 1.90 GHz (asserted by call to kernel)
  boost state support:
    Supported: yes
    Active: yes
    AMD PSTATE Highest Performance: 255. Maximum Frequency: 4.37 GHz.
    AMD PSTATE Nominal Performance: 105. Nominal Frequency: 1.80 GHz.
    AMD PSTATE Lowest Non-linear Performance: 65. Lowest Non-linear Frequency: 1.11 GHz.
    AMD PSTATE Lowest Performance: 24. Lowest Frequency: 400 MHz.

We will see how it goes.
(For now it works very good!)

8

Some similarities spotted Android Studio is build upon IntelliJ which has a known issue with xorg-wayland

9

Thank you for your answer. I have read carefully this topic and I think it is not the same source of problem.

I still have crashes with Android Studio never on the other program at the moment. (Probably because of the fact it uses a lot of CPU).
I haven’t crashes for like 2 days and again it appears. I have tried different governor from conservativ/performance and I stay with schedutil as it the most stable for me at the moment.

I think I should find the solutions of CPU/GPU AMD ryzen controller setup (something upgraded lib which is used instead of this deprecated), but I can’t find such thing. I need optimizer or good manual setup. But for now I do not know how to do it and don’t want to burn my laptop ;C :slight_smile:
Thanks and look for more advices if someone has got similar problems with AMD~.
Greetings