Black screen after keeping the laptop on for long time

Hello, I have been using Manjaro for some time and recently came across this issue when my whole screen goes black after the laptop is not in use for some time. In particular this happens when I first boot it up, the screen goes black, freezes and nothing works. The only option I then have is to force restart after which the boot goes normally. My initial guess was that it’s a boot issue but same thing happens if the put the laptop to sleep for long or even with the simple screen locking if it happens for long time.
Currently my only safe bet is to manually block sleep and screen locking in the brightness settings.
Below is the ouput of inxi

System:
  Host: exigov2 Kernel: 6.1.31-2-MANJARO arch: x86_64 bits: 64
    Desktop: KDE Plasma v: 5.27.5 Distro: Manjaro Linux
Machine:
  Type: Laptop System: AZOM product: EXIGO V2 v: N/A
    serial: <superuser required>
  Mobo: AZOM model: EXIGO V2 powered by premamod.com
    serial: <superuser required> UEFI: Prema Mod v: 1.06.09AOM v2
    date: 04/12/2017
CPU:
  Info: quad core model: Intel Core i5-7600K bits: 64 type: MCP cache:
    L2: 1024 KiB
  Speed (MHz): avg: 1606 min/max: 800/4200 cores: 1: 875 2: 893 3: 3800
    4: 856
Graphics:
  Device-1: NVIDIA GP106M [GeForce GTX 1060 Mobile] driver: nvidia
    v: 530.41.03
  Device-2: Chicony USB 2.0 Camera driver: uvcvideo type: USB
  Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.1 driver: X:
    loaded: nvidia gpu: nvidia,nvidia-nvswitch resolution: 1920x1080~60Hz
  API: OpenGL v: 4.6.0 NVIDIA 530.41.03 renderer: NVIDIA GeForce GTX
    1060/PCIe/SSE2
Audio:
  Device-1: Intel 100 Series/C230 Series Family HD Audio driver: snd_hda_intel
  Device-2: NVIDIA GP106 High Definition Audio driver: snd_hda_intel
  API: ALSA v: k6.1.31-2-MANJARO status: kernel-api
  Server-1: PulseAudio v: 16.1 status: active
Network:
  Device-1: Qualcomm Atheros Killer E2400 Gigabit Ethernet driver: alx
  IF: enp110s0 state: down mac: 80:fa:5b:4d:ea:f0
  Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi
  IF: wlp113s0 state: up mac: 00:28:f8:3e:51:2a
Bluetooth:
  Device-1: Intel Bluetooth wireless interface driver: btusb type: USB
  Report: rfkill ID: hci0 rfk-id: 1 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: see --recommends
Drives:
  Local Storage: total: 704.24 GiB used: 198.29 GiB (28.2%)
  ID-1: /dev/nvme0n1 vendor: Western Digital model: WDS500G3X0C-00SJG0
    size: 465.76 GiB
  ID-2: /dev/nvme1n1 vendor: Samsung model: MZVPV256HDGL-00000
    size: 238.47 GiB
Partition:
  ID-1: / size: 68.99 GiB used: 34.62 GiB (50.2%) fs: ext4 dev: /dev/nvme0n1p3
  ID-2: /boot/efi size: 511 MiB used: 324 KiB (0.1%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-3: /home size: 383.42 GiB used: 163.67 GiB (42.7%) fs: ext4
    dev: /dev/nvme0n1p4
Swap:
  ID-1: swap-1 type: partition size: 3.98 GiB used: 0 KiB (0.0%)
    dev: /dev/nvme0n1p2
Sensors:
  System Temperatures: cpu: 54.0 C pch: 66.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 210 Uptime: 32m Memory: available: 15.45 GiB
  used: 2.46 GiB (15.9%) Shell: Zsh inxi: 3.3.27

Here’s the journctl logs for when the screen freezes black during boot

Jul 05 09:00:29 exigov2 kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
Jul 05 09:00:29 exigov2 kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
Jul 05 09:00:30 exigov2 kernel:
Jul 05 09:00:31 exigov2 kernel: BUG: kernel NULL pointer dereference, address: 0000000000000070
Jul 05 09:00:31 exigov2 kernel: #PF: supervisor write access in kernel mode
Jul 05 09:00:31 exigov2 kernel: #PF: error_code(0x0002) - not-present page
Jul 05 09:00:31 exigov2 systemd[1]: Failed to start Load Kernel Modules.
░░ Subject: A start job for unit systemd-modules-load.service has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit systemd-modules-load.service has finished with a failure.
░░ 
░░ The job identifier is 77 and the job result is failed.
Jul 05 09:00:32 exigov2 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02

For comparison here’s an error log of normal boot

Jul 05 09:03:29 exigov2 kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
Jul 05 09:03:29 exigov2 kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
Jul 05 09:03:30 exigov2 kernel:
Jul 05 09:03:32 exigov2 bluetoothd[681]: src/plugin.c:plugin_init() Failed to init vcp plugin
Jul 05 09:03:32 exigov2 bluetoothd[681]: src/plugin.c:plugin_init() Failed to init mcp plugin
Jul 05 09:03:32 exigov2 bluetoothd[681]: src/plugin.c:plugin_init() Failed to init bap plugin
Jul 05 09:03:32 exigov2 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Jul 05 09:03:32 exigov2 bluetoothd[681]: Failed to set mode: Failed (0x03)

This problem kinda started when I upgraded to the latest kernel 6.3.5-2, I tried downgrading to kernel 6.2.16-2 and then linux-lts 6.1.31-2 to no avail.
Any help is appreciated. Thank you

you are saying in your title, that it happens after keeping the laptop on for long time; and in your description you are saying that it happens:

and then you are saying that it happens during boot:

so can you clarify it more?
and post full system info:
inxi -zav7

What I meant is that the issue happens when the laptop is not used for long period of time weather it was on or off doesn’t matter. For example if I turn off and on after say 15 min that’s not an issue but it is an issue if I turn it on after 5-6 hours.
The only exception is if the screen is forced to stay on then there’s no issue. The output as asked of ‘inxi -zav7’ as asked

System:
  Kernel: 6.1.31-2-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.1.1
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1-x86_64
    root=UUID=31147878-f10d-4130-8b91-9b44b52cba29 rw quiet apparmor=1
    security=apparmor resume=UUID=73006f3f-9947-4e96-9b56-bad5aeafcb36
    udev.log_priority=3
  Desktop: KDE Plasma v: 5.27.5 tk: Qt v: 5.15.9 wm: kwin_x11 vt: 1 dm:
    1: LightDM v: 1.32.0 note: stopped 2: SDDM Distro: Manjaro Linux
    base: Arch Linux
Machine:
  Type: Laptop System: AZOM product: EXIGO V2 v: N/A
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: AZOM model: EXIGO V2 powered by premamod.com
    serial: <superuser required> UEFI: Prema Mod v: 1.06.09AOM v2
    date: 04/12/2017
Memory:
  System RAM: available: 15.45 GiB used: 2.09 GiB (13.5%)
  RAM Report: permissions: Unable to run dmidecode. Root privileges
    required.
CPU:
  Info: model: Intel Core i5-7600K bits: 64 type: MCP arch: Kaby Lake
    gen: core 7 level: v3 note: check built: 2018 process: Intel 14nm family: 6
    model-id: 0x9E (158) stepping: 9 microcode: 0xF2
  Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 256 KiB
    desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB
    desc: 1x6 MiB
  Speed (MHz): avg: 3800 min/max: 800/4200 scaling: driver: intel_pstate
    governor: powersave cores: 1: 3800 2: 3800 3: 3800 4: 3800 bogomips: 30409
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_perfmon art avx avx2 bmi1 bmi2 bts clflush
    clflushopt cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64
    dtherm dts epb ept ept_ad erms est f16c flexpriority flush_l1d fma fpu
    fsgsbase fxsr ht hwp hwp_act_window hwp_epp hwp_notify ibpb ibrs ida
    intel_pt invpcid invpcid_single lahf_lm lm mca mce md_clear mmx monitor
    movbe mpx msr mtrr nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm
    pdpe1gb pebs pge pln pni popcnt pse pse36 pti pts rdrand rdseed rdtscp
    rep_good sdbg sep sgx smap smep ss ssbd sse sse2 sse4_1 sse4_2 ssse3
    stibp syscall tm tm2 tpr_shadow tsc tsc_adjust tsc_deadline_timer vme vmx
    vnmi vpid x2apic xgetbv1 xsave xsavec xsaveopt xsaves xtopology xtpr
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    disabled
  Type: mds mitigation: Clear CPU buffers; SMT disabled
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT disabled
  Type: retbleed mitigation: IBRS
  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: IBRS, IBPB: conditional, STIBP: disabled,
    RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort mitigation: TSX disabled
Graphics:
  Device-1: NVIDIA GP106M [GeForce GTX 1060 Mobile] vendor: CLEVO/KAPOK
    driver: nvidia v: 530.41.03 alternate: nouveau,nvidia_drm non-free: 530.xx+
    status: current (as of 2023-05) arch: Pascal code: GP10x
    process: TSMC 16nm built: 2016-21 pcie: gen: 3 speed: 8 GT/s lanes: 16
    ports: active: none off: eDP-1 empty: DP-1,DP-2,HDMI-A-1 bus-ID: 01:00.0
    chip-ID: 10de:1c20 class-ID: 0300
  Device-2: Chicony USB 2.0 Camera driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-10:4 chip-ID: 04f2:b5a7
    class-ID: 0e02
  Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.1
    compositor: kwin_x11 driver: X: loaded: nvidia gpu: nvidia,nvidia-nvswitch
    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: eDP-1 mapped: DP-0 note: disabled model: LG Display 0x046f
    built: 2014 res: 1920x1080 hz: 60 dpi: 142 gamma: 1.2
    size: 344x194mm (13.54x7.64") diag: 395mm (15.5") ratio: 16:9
    modes: 1920x1080
  API: OpenGL v: 4.6.0 NVIDIA 530.41.03 renderer: NVIDIA GeForce GTX
    1060/PCIe/SSE2 direct-render: Yes
Audio:
  Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: CLEVO/KAPOK
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a170
    class-ID: 0403
  Device-2: NVIDIA GP106 High Definition Audio vendor: CLEVO/KAPOK
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 01:00.1 chip-ID: 10de:10f1 class-ID: 0403
  API: ALSA v: k6.1.31-2-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: 0.3.70 status: off with: pipewire-media-session
    status: active tools: pw-cli
  Server-3: PulseAudio v: 16.1 status: active with: 1: pulseaudio-alsa
    type: plugin 2: pulseaudio-jack type: module tools: pacat,pactl
Network:
  Device-1: Qualcomm Atheros Killer E2400 Gigabit Ethernet vendor: CLEVO/KAPOK
    driver: alx v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d000
    bus-ID: 6e:00.0 chip-ID: 1969:e0a1 class-ID: 0200
  IF: enp110s0 state: down mac: <filter>
  Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel pcie:
    gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 71:00.0 chip-ID: 8086:24fd
    class-ID: 0280
  IF: wlp113s0 state: up mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  WAN IP: <filter>
Bluetooth:
  Device-1: Intel Bluetooth wireless interface driver: btusb v: 0.8 type: USB
    rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-11:5 chip-ID: 8087:0a2b
    class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 1 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 704.24 GiB used: 198.31 GiB (28.2%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital
    model: WDS500G3X0C-00SJG0 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: 111110WD temp: 47.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:5 vendor: Samsung
    model: MZVPV256HDGL-00000 size: 238.47 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: BXW7300Q temp: 36.9 C scheme: GPT
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 70.65 GiB size: 68.99 GiB (97.65%) used: 34.62 GiB (50.2%)
    fs: ext4 dev: /dev/nvme0n1p3 maj-min: 259:3 label: N/A
    uuid: 31147878-f10d-4130-8b91-9b44b52cba29
  ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%)
    used: 324 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
    label: NO_LABEL uuid: C1C8-531D
  ID-3: /home raw-size: 390.63 GiB size: 383.42 GiB (98.15%)
    used: 163.68 GiB (42.7%) fs: ext4 dev: /dev/nvme0n1p4 maj-min: 259:4
    label: N/A uuid: 4f48f405-a167-4e8a-95fe-5ab54e2d5f08
Swap:
  Kernel: swappiness: 10 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 3.98 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/nvme0n1p2 maj-min: 259:2 label: N/A
    uuid: 73006f3f-9947-4e96-9b56-bad5aeafcb36
Unmounted:
  ID-1: /dev/nvme1n1p1 maj-min: 259:6 size: 499 MiB fs: ntfs label: Recovery
    uuid: CC5288C45288B4AC
  ID-2: /dev/nvme1n1p2 maj-min: 259:7 size: 100 MiB fs: vfat label: N/A
    uuid: 128B-A0C8
  ID-3: /dev/nvme1n1p3 maj-min: 259:8 size: 16 MiB fs: <superuser required>
    label: N/A uuid: N/A
  ID-4: /dev/nvme1n1p4 maj-min: 259:9 size: 237.05 GiB fs: ntfs label: N/A
    uuid: 40D48E42D48E39E4
  ID-5: /dev/nvme1n1p5 maj-min: 259:10 size: 843 MiB fs: ntfs label: N/A
    uuid: 542EC4222EC3FACE
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 16 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 1-2:2 info: Synaptics type: <vendor specific> driver: N/A
    interfaces: 1 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1
    power: 100mA chip-ID: 06cb:0078 class-ID: ff00 serial: <filter>
  Device-2: 1-4:3 info: Pixart Imaging Gaming Mouse type: mouse,keyboard
    driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 100mA chip-ID: 093a:2533 class-ID: 0300
  Device-3: 1-10:4 info: Chicony USB 2.0 Camera type: video driver: uvcvideo
    interfaces: 2 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0
    power: 500mA chip-ID: 04f2:b5a7 class-ID: 0e02
  Device-4: 1-11:5 info: Intel Bluetooth wireless interface type: bluetooth
    driver: btusb interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1
    mode: 1.1 power: 100mA chip-ID: 8087:0a2b class-ID: e001
  Hub-2: 2-0:1 info: super-speed hub ports: 10 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 50.0 C pch: 63.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 206 Uptime: 5m wakeups: 1 Init: systemd v: 253 default: graphical
  tool: systemctl Compilers: gcc: 13.1.1 clang: 15.0.7 Packages: 2360
  pm: pacman pkgs: 2354 libs: 505 tools: pamac,yay pm: flatpak pkgs: 0
  pm: snap pkgs: 6 Shell: Zsh v: 5.9 running-in: yakuake inxi: 3.3.27

Over the years I have seen a lot of similar topics in the forum.

The common denominator is laptop with dual Intel/AMD and Nvidia GPU - but it may occur on onther configurations as well.

The power save sequence - usually - goes like this

  • suspend (in suspended state the ram is kept alive)
  • after some predefined period in suspend the system switch to sleep/hibernate to prevent a complete drain of battery
  • sleep/hibernate (in sleep/hibernate state the content of memory is written to disk)

From what I understood from those topics - it is caused by a condition where the Nvidia GPU cannot be initialized when the system has been in sleep/hibernate state.

It works fine with suspend as this is all RAM but sleep/hibernate is memory written to disk and the system is powered off.

When the system is powered up it is configured to read from disk and initialize everything from the sleep state - but it cannot correctly connect to the Nvidia GPU - thus causing the black screen.

I don’t know how to solve the issue but I have ideas to work around it - although most users don’t like the idea - they prefer the sentence it works with Windows - and thus expect it to work with Linux as well - but in some situations it doesn’t

  • disable the functionality
  • only use the onboard Intel GPU
  • power down the system

You may find inspiration on how to make it work by reading Power management/Suspend and hibernate - ArchWiki especially the Troubleshooting[1] section

I see, looks like that is indeed the case. This is the log when I tried to wake the laptop up from sleep

ul 06 20:15:40 abhinav-exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:0:0:0x0000000f
Jul 06 20:15:40 abhinav-exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:1:0:0x0000000f
Jul 06 20:15:40 abhinav-exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:2:0:0x0000000f
Jul 06 20:15:40 abhinav-exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:3:0:0x0000000f
Jul 06 20:15:40 abhinav-exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000987d:0:0:0x0000000f
Jul 06 20:15:40 abhinav-exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices
Jul 06 20:15:40 abhinav-exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices
Jul 06 20:15:40 abhinav-exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failure reading maximum pixel clock value for display device DP-0.
Jul 06 20:15:40 abhinav-exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices
Jul 06 20:15:40 abhinav-exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:0:0:0x0000000f
Jul 06 20:15:40 abhinav-exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:1:0:0x0000000f
Jul 06 20:15:40 abhinav-exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:2:0:0x0000000f
Jul 06 20:15:40 abhinav-exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:3:0:0x0000000f
Jul 06 20:15:40 abhinav-exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000987d:0:0:0x0000000f
Jul 06 20:15:40 abhinav-exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000987d:0:0:0x0000000f
Jul 06 20:15:40 abhinav-exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices
Jul 06 20:15:40 abhinav-exigov2 kernel: BUG: kernel NULL pointer dereference, address: 0000000000000054
Jul 06 20:15:40 abhinav-exigov2 kernel: #PF: supervisor read access in kernel mode
Jul 06 20:15:40 abhinav-exigov2 kernel: #PF: error_code(0x0000) - not-present page
Jul 06 20:15:40 abhinav-exigov2 kernel: snd_hda_codec_hdmi hdaudioC1D0: Unable to sync register 0x4f0800. -5
Jul 06 20:15:42 abhinav-exigov2 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Jul 06 20:15:42 abhinav-exigov2 bluetoothd[704]: Failed to set mode: Failed (0x03)

nvidia-modeset was turned on by me to enable hardware acceleration while watching youtube videos.
But this still doesn’t explain the issues faced during initial boot, that doesn’t show any nvidia related problem.

Indeed it does not.

I noticed that a combined bug circulates Mesa 23.1.3.1 causes system freezing/crashing which refers upstream to [SOLVED] arch with gnome starts every 3rd time after upgrade to 6.3.9 / Kernel & Hardware / Arch Linux Forums - at least that is how I understand it - some combinations of mesa and kernel 6.3 creates issues.

From the thread it appears that a kernel patch for 6.4 temporarily fix it - but the real thing is expected with 6.5-rc1.

you can try enabling early loading for the black screen at boot issue:
kate /etc/mkinitcpio.conf
and edit the modules section to look like this:

MODULES=(nvidia nvidia_drm nvidia_uvm nvidia_modeset)

save it and update it:
sudo mkinitcpio -P
reboot and test…


for this:

modify acpi strings; first check:

sudo strings /sys/firmware/acpi/tables/DSDT | grep -i 'windows ' | sort | tail -1

it will output some windows version, and now add it to grub:
kate /etc/default/grub
and in this line: GRUB_CMDLINE_LINUX_DEFAULT inside the quotes add these parameters:

acpi_osi=! acpi_osi='Windows 2015'

where Windows 2015 will be replaced with the output from the sudo strings command…
dont remove any parameters, add them to existing ones;
save the file and update grub:
sudo update-grub
reboot and test

I had a minor issue with mkinitcpio which I solved. Other than that everything seems to be working fine for now. I left it on for 2 hours without any issue. Its real real would be during the next boot after leaving it overnight for extended hours. I’ll keep you updated on whatever happens next.

Update: It didn’t work, what’s weirder is that there isn’t even a boot log this time as if the boot wasn’t even registered. Even my mouse wasn’t turned on. The error messages don’t show anything new, although the nvidia errors have gone I think. Attached is the whole log for today.

Since the log was too big for posting I pasted it here - Jul 08 08:53:02 exigov2 kernel: microcode: microcode updated early to revision 0 - Pastebin.com

Weirdest thing is that there’s not even a boot entry for some reason. I hope this helps.

you didnt add properly the parameters:

udev.log_priority=3 acpi_osi=! "acpi_osi=Windows 2015"

and it should be:

udev.log_priority=3 acpi_osi=! acpi_osi='Windows 2015'

where Windows 2015 will be replaced with the string command output from above, unless it actually outputted Windows 2015;
so your whole grub command line will look like this:

GRUB_CMDLINE_LINUX_DEFAULT="rw quiet apparmor=1 security=apparmor udev.log_priority=3 acpi_osi=! acpi_osi='Windows 2015'"

so correct it;
save grub and update it:
sudo update-grub
reboot and test…


and also post output from:
cat /etc/mkinitcpio.conf
since you mentioned some issues…

I have no idea why it showed like, I had copied and pasted it exactly same. The entry looks like this -

GRUB_CMDLINE_LINUX_DEFAULT=“quiet apparmor=1 security=apparmor resume=UUID=73006f3f-9947-4e96-9b56-bad5aeafcb36 udev.log_priority=3 acpi_osi=! acpi_osi=‘Windows 2015’”

The output of cat /etc/mkinitcpio.conf is:

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES=(piix ide_disk reiserfs)
MODULES=(nvidia nvidia_drm nvidia_uvm nvidia_modeset)

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
FILES=""

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No raid, lvm2, or encrypted root is needed.
#    HOOKS=(base)
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS=(base udev autodetect block filesystems)
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS=(base udev block filesystems)
#
##   This setup assembles a pata mdadm array with an encrypted root FS.
##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
#    HOOKS=(base udev block mdadm encrypt filesystems)
#
##   This setup loads an lvm2 volume group on a usb device.
#    HOOKS=(base udev block lvm2 filesystems)
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr, fsck and shutdown hooks.
HOOKS="base udev autodetect modconf block keyboard keymap resume filesystems fsck"

# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"
#COMPRESSION="zstd"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()

Thanks again for the help

ok, i see…
so do you have actually windows 2015 when you run the sudo strings command?
if yes, try changing it to windows 2012:

acpi_osi=! acpi_osi='Windows 2012'

save grub, then update it:
sudo update-grub
reboot and test…


if you still have issues, try enabling video memory preserve:
kate /etc/modprobe.d/nvidia-power-management.conf
and add there this line:

options nvidia NVreg_PreserveVideoMemoryAllocations=1 NVreg_TemporaryFilePath=/var/tmp

save the file, run this:
sudo mkinitcpio -P
reboot and test

I was trying to find the most appropriate version for acpi_osi by tallying the osi argument list but the there’s no info for versions after the 2004 version that came out in 2020. I was wondering if I should try Windows 2020 but I’m not sure. As for the commas while running, that happens no matter where I place the acpi_osi string.
The proper test is only possible at night cause that’s when I turn that laptop off for long time. I’ll let you know how it goes by both the methods.

Update: This happened again only this time it wasn’t even a reboot. I had forgotten to turn off my laptop, it was on for 4 hours no sleep/suspend. I closed all the open windows and suddenly my screen turned black showing the same errors later in the journalctl.

Jul 09 03:50:07 exigov2 plasmashell[1069]: libkcups: Renew-Subscription last error: 0 successful-ok
Jul 09 04:01:01 exigov2 CROND[12945]: (root) CMD (run-parts /etc/cron.hourly)
Jul 09 04:01:01 exigov2 CROND[12944]: (root) CMDEND (run-parts /etc/cron.hourly)
Jul 09 04:06:46 exigov2 pamac-tray-plas[1226]: updates_checker.vala:71: check updates
Jul 09 04:06:48 exigov2 pamac-tray-plas[1226]: updates_checker.vala:101: 0 updates found
Jul 09 04:13:11 exigov2 wpa_supplicant[817]: wlp113s0: WPA: Group rekeying completed with 8c:a3:99:b4:e3:63 [GTK=CCMP]
Jul 09 04:24:55 exigov2 dbus-daemon[527]: [system] Activating service name='org.kde.powerdevil.backlighthelper' requested by ':1.47' (uid=1000 pid=1088 comm="/usr/lib/org_kde_powerdevil") (using servicehelper)
Jul 09 04:24:55 exigov2 dbus-daemon[527]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Jul 09 04:24:55 exigov2 systemd[913]: app-org.kde.okular-87f8f49049ef4cc59d09a876bdc440a0.scope: Consumed 30.054s CPU time.
Jul 09 04:24:57 exigov2 systemd[913]: app-brave\x2dbrowser-ad697c02b7ad47f987035ed903db4d6b.scope: Consumed 6min 12.315s CPU time.
Jul 09 04:24:58 exigov2 kwin_x11[1025]: file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Jul 09 04:24:58 exigov2 kwin_x11[1025]: file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Jul 09 04:25:01 exigov2 systemd[913]: app-org.kde.dolphin-895e91f6437d43998431a7d27bb872e8.scope: Consumed 7.333s CPU time.
Jul 09 04:25:08 exigov2 kernel: NVRM: GPU at PCI:0000:01:00: GPU-1aa7808c-552f-4ea5-a0c5-ab4878dacd7c
Jul 09 04:25:08 exigov2 kernel: NVRM: Xid (PCI:0000:01:00): 79, pid='<unknown>', name=<unknown>, GPU has fallen off the bus.
Jul 09 04:25:08 exigov2 kernel: NVRM: GPU 0000:01:00.0: GPU has fallen off the bus.
Jul 09 04:25:56 exigov2 wpa_supplicant[817]: wlp113s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-78 noise=9999 txrate=585100
Jul 09 04:26:02 exigov2 kwin_x11[1025]: kwin_scene_opengl: A graphics reset attributable to the current GL context occurred.
Jul 09 04:26:02 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:3:0:0x0000000f
Jul 09 04:26:07 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:3:0:0x0000000f
Jul 09 04:26:07 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:3:0:0x0000000f
Jul 09 04:26:30 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:3:0:0x0000000f
Jul 09 04:26:48 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:3:0:0x0000000f
Jul 09 04:26:56 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000987d:0:0:0x0000000f
Jul 09 04:26:56 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:0:0:0x0000000f
Jul 09 04:26:56 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:0:0:0x0000000f
Jul 09 04:26:56 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:1:0:0x0000000f
Jul 09 04:26:56 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:1:0:0x0000000f
Jul 09 04:26:56 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:2:0:0x0000000f
Jul 09 04:26:56 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:2:0:0x0000000f
Jul 09 04:26:56 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:3:0:0x0000000f
Jul 09 04:26:56 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:3:0:0x0000000f
Jul 09 04:26:56 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000987d:0:0:0x0000000f
Jul 09 04:26:56 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:0:0:0x0000000f
Jul 09 04:26:56 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:0:0:0x0000000f
Jul 09 04:26:56 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:1:0:0x0000000f
Jul 09 04:26:56 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:1:0:0x0000000f
Jul 09 04:26:56 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:2:0:0x0000000f
Jul 09 04:26:56 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:2:0:0x0000000f
Jul 09 04:26:56 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:3:0:0x0000000f
Jul 09 04:26:56 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:3:0:0x0000000f
Jul 09 04:26:56 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:3:0:0x0000000f
Jul 09 04:26:56 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:3:0:0x0000000f
Jul 09 04:27:04 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:0:0:0x0000000f
Jul 09 04:27:04 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:1:0:0x0000000f
Jul 09 04:27:04 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:2:0:0x0000000f
Jul 09 04:27:04 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:3:0:0x0000000f
Jul 09 04:27:04 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000987d:0:0:0x0000000f
Jul 09 04:27:04 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query default adaptivesync listing for LG Display (DP-0)
Jul 09 04:27:04 exigov2 kernel: nvidia-modeset: WARNING: GPU:0: LG Display (DP-0): G-SYNC Compatible: EDID min refresh rate invalid, disabling G-SYNC Compatible.
Jul 09 04:27:04 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000987d:0:0:0x0000000f
Jul 09 04:27:34 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices
Jul 09 04:27:34 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices
Jul 09 04:27:34 exigov2 kernel: nvidia-modeset: WARNING: GPU:0: Failure processing EDID for display device LG Display (DP-0).
Jul 09 04:27:34 exigov2 kernel: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device LG Display (DP-0)
Jul 09 04:27:34 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failure reading maximum pixel clock value for display device DP-0.
Jul 09 04:27:34 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices
Jul 09 04:27:34 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:0:0:0x0000000f
Jul 09 04:27:34 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:1:0:0x0000000f
Jul 09 04:27:34 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:2:0:0x0000000f
Jul 09 04:27:34 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:3:0:0x0000000f
Jul 09 04:27:34 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000987d:0:0:0x0000000f
Jul 09 04:27:34 exigov2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000987d:0:0:0x0000000f
Jul 09 04:27:34 exigov2 systemd[1]: Created slice Slice /system/systemd-coredump.
Jul 09 04:27:34 exigov2 systemd[1]: Started Process Core Dump (PID 13148/UID 0).
Jul 09 04:27:34 exigov2 systemd-coredump[13149]: Process 674 (Xorg) of user 0 dumped core.

                                                         Stack trace of thread 674:
                                                         #0  0x00007fc66f12826c n/a (libc.so.6 + 0x8926c)
                                                         #1  0x00007fc66f0d8a08 raise (libc.so.6 + 0x39a08)
                                                         #2  0x00007fc66f0c1538 abort (libc.so.6 + 0x22538)
                                                         #3  0x00005624360a2cb0 OsAbort (Xorg + 0x153cb0)
                                                         #4  0x00005624360a4113 FatalError (Xorg + 0x155113)
                                                         #5  0x00005624360aaa79 n/a (Xorg + 0x15ba79)
                                                         #6  0x00007fc66f0d8ab0 n/a (libc.so.6 + 0x39ab0)
                                                         #7  0x00007fc66dadaaab n/a (nvidia_drv.so + 0xdaaab)
                                                         #8  0x00007fc66dadc1bd n/a (nvidia_drv.so + 0xdc1bd)
                                                         #9  0x00007fc66dadd894 n/a (nvidia_drv.so + 0xdd894)
                                                         #10 0x00007fc66dadd9a9 n/a (nvidia_drv.so + 0xdd9a9)
                                                         #11 0x00007fc66dad53e3 n/a (nvidia_drv.so + 0xd53e3)
                                                         #12 0x00007fc66dad80e8 n/a (nvidia_drv.so + 0xd80e8)
                                                         #13 0x00007fc66dae3503 n/a (nvidia_drv.so + 0xe3503)
                                                         #14 0x00007fc66dae8f14 n/a (nvidia_drv.so + 0xe8f14)
                                                         #15 0x00007fc66daea0d6 n/a (nvidia_drv.so + 0xea0d6)
                                                         #16 0x00007fc66daecc39 n/a (nvidia_drv.so + 0xecc39)
                                                         #17 0x00007fc66dad30c9 n/a (nvidia_drv.so + 0xd30c9)
                                                         #18 0x00007fc66dea05fe n/a (nvidia_drv.so + 0x4a05fe)
                                                         ELF object binary architecture: AMD x86-64
Jul 09 04:27:34 exigov2 systemd[1]: systemd-coredump@0-13148-0.service: Deactivated successfully.
Jul 09 04:27:34 exigov2 polkit-kde-authentication-agent-1[1087]: The X11 connection broke (error 1). Did the X11 server die?
Jul 09 04:27:34 exigov2 gmenudbusmenuproxy[1086]: The X11 connection broke (error 1). Did the X11 server die?
Jul 09 04:27:34 exigov2 dolphin[6643]: The X11 connection broke (error 1). Did the X11 server die?
Jul 09 04:27:34 exigov2 pamac-tray-plasma[1226]: The X11 connection broke (error 1). Did the X11 server die?
Jul 09 04:27:34 exigov2 kdeconnectd[1202]: The X11 connection broke (error 1). Did the X11 server die?
Jul 09 04:27:34 exigov2 kscreen_backend_launcher[1084]: The X11 connection broke (error 1). Did the X11 server die?
Jul 09 04:27:34 exigov2 yakuake[1204]: The X11 connection broke (error 1). Did the X11 server die?
Jul 09 04:27:34 exigov2 org_kde_powerdevil[1088]: The X11 connection broke (error 1). Did the X11 server die?
Jul 09 04:27:34 exigov2 kaccess[1214]: The X11 connection broke (error 1). Did the X11 server die?
Jul 09 04:27:34 exigov2 xdg-desktop-portal-kde[1089]: The X11 connection broke (error 1). Did the X11 server die?
Jul 09 04:27:34 exigov2 kactivitymanagerd[1085]: The X11 connection broke (error 1). Did the X11 server die?
Jul 09 04:27:34 exigov2 kglobalaccel5[1050]: The X11 connection broke (error 1). Did the X11 server die?
Jul 09 04:27:34 exigov2 kglobalaccel5[1050]: XIO:  fatal IO error 25 (Inappropriate ioctl for device) on X server ":0"
Jul 09 04:27:34 exigov2 kglobalaccel5[1050]:       after 8 requests (8 known processed) with 0 events remaining.
Jul 09 04:27:34 exigov2 kglobalaccel5[1050]: The X11 connection broke: I/O error (code 1)
Jul 09 04:27:34 exigov2 xembedsniproxy[1090]: The X11 connection broke (error 1). Did the X11 server die?
Jul 09 04:27:34 exigov2 systemd[913]: plasma-kscreen.service: Main process exited, code=exited, status=1/FAILURE
Jul 09 04:27:34 exigov2 systemd[913]: plasma-kscreen.service: Failed with result 'exit-code'.
Jul 09 04:27:34 exigov2 systemd[913]: plasma-kscreen.service: Consumed 1.218s CPU time.
Jul 09 04:27:34 exigov2 at-spi-bus-launcher[2001]: X connection to :0 broken (explicit kill or server shutdown).
Jul 09 04:27:34 exigov2 ksmserver[1022]: The X11 connection broke (error 1). Did the X11 server die?
Jul 09 04:27:34 exigov2 polkitd[531]: Unregistered Authentication Agent for unix-session:2 (system bus name :1.65, object path /org/kde/PolicyKit1/AuthenticationAgent, locale en_GB.UTF-8) (disconnected from bus)
Jul 09 04:27:34 exigov2 plasmashell[1069]: The X11 connection broke: I/O error (code 1)
Jul 09 04:27:34 exigov2 plasmashell[1069]: X connection to :0 broken (explicit kill or server shutdown).
Jul 09 04:27:34 exigov2 msm_kde_notifier[1200]: The X11 connection broke (error 1). Did the X11 server die?
Jul 09 04:27:34 exigov2 systemd[913]: plasma-polkit-agent.service: Consumed 1.383s CPU time.
Jul 09 04:27:34 exigov2 systemd[913]: plasma-xdg-desktop-portal-kde.service: Main process exited, code=exited, status=1/FAILURE
Jul 09 04:27:34 exigov2 systemd[913]: plasma-xdg-desktop-portal-kde.service: Failed with result 'exit-code'.
Jul 09 04:27:34 exigov2 systemd[913]: plasma-xdg-desktop-portal-kde.service: Consumed 1.380s CPU time.
Jul 09 04:27:34 exigov2 systemd[913]: app-msm_kde_notifier@autostart.service: Main process exited, code=exited, status=1/FAILURE
Jul 09 04:27:34 exigov2 systemd[913]: app-msm_kde_notifier@autostart.service: Failed with result 'exit-code'.
Jul 09 04:27:34 exigov2 systemd[913]: app-msm_kde_notifier@autostart.service: Consumed 11.679s CPU time.
Jul 09 04:27:34 exigov2 systemd[913]: Stopped target plasma-workspace-x11.target.
Jul 09 04:27:34 exigov2 systemd[913]: Stopped target KDE Plasma Workspace.
Jul 09 04:27:34 exigov2 systemd[913]: Stopped target Startup of XDG autostart applications.
Jul 09 04:27:34 exigov2 systemd[913]: Stopping Geoclue Demo agent...
Jul 09 04:27:34 exigov2 systemd[913]: Stopping Accessibility...
Jul 09 04:27:34 exigov2 systemd[913]: Stopping KDE Connect...
Jul 09 04:27:34 exigov2 systemd[913]: Stopping Yakuake...
Jul 09 04:27:34 exigov2 systemd[913]: Stopping Update Notifier Tray Icon...
Jul 09 04:27:34 exigov2 systemd[913]: Stopping Accessibility services bus...
Jul 09 04:27:34 exigov2 systemd[913]: Stopping Virtual filesystem service - Apple File Conduit monitor...
Jul 09 04:27:34 exigov2 systemd[913]: Stopping Virtual filesystem service...
Jul 09 04:27:34 exigov2 kded5[1024]: Service  ":1.41" unregistered
Jul 09 04:27:34 exigov2 systemd[913]: Stopping Virtual filesystem service - digital camera monitor...
Jul 09 04:27:34 exigov2 systemd[913]: Stopping Virtual filesystem metadata service...
Jul 09 04:27:34 exigov2 systemd[913]: Stopping Virtual filesystem service - Media Transfer Protocol monitor...
Jul 09 04:27:34 exigov2 systemd[913]: Stopping Virtual filesystem service - disk device monitor...
Jul 09 04:27:34 exigov2 systemd[913]: Stopping Proxies GTK DBus menus to a Plasma readable format...
Jul 09 04:27:34 exigov2 systemd[913]: Stopping KRunner...
Jul 09 04:27:34 exigov2 systemd[913]: Stopping KDE Window Manager...
Jul 09 04:27:34 exigov2 kded5[1024]: Service  ":1.45" unregistered
Jul 09 04:27:34 exigov2 systemd[913]: Stopping Handle legacy xembed system tray icons...
Jul 09 04:27:34 exigov2 kded5[1024]: The X11 connection broke: I/O error (code 1)
Jul 09 04:27:34 exigov2 kded5[1024]: X connection to :0 broken (explicit kill or server shutdown).
Jul 09 04:27:34 exigov2 systemd[913]: Stopping Portal service...
Jul 09 04:27:34 exigov2 systemd[913]: Stopping flatpak document portal service...
Jul 09 04:27:34 exigov2 systemd[913]: Stopping sandboxed app permission store...
Jul 09 04:27:34 exigov2 systemd[913]: Stopping Baloo File Indexer Daemon...
Jul 09 04:27:34 exigov2 systemd[913]: app-kaccess@autostart.service: Main process exited, code=exited, status=1/FAILURE
Jul 09 04:27:34 exigov2 systemd[913]: app-kaccess@autostart.service: Failed with result 'exit-code'.
Jul 09 04:27:34 exigov2 systemd[913]: Stopped Accessibility.
Jul 09 04:27:34 exigov2 systemd[913]: app-kaccess@autostart.service: Consumed 2.975s CPU time.
Jul 09 04:27:34 exigov2 systemd[1]: run-user-1000-doc.mount: Deactivated successfully.
Jul 09 04:27:34 exigov2 systemd[913]: Stopped sandboxed app permission store.
Jul 09 04:27:34 exigov2 systemd[913]: plasma-ksmserver.service: Main process exited, code=exited, status=1/FAILURE
Jul 09 04:27:34 exigov2 systemd[913]: plasma-ksmserver.service: Failed with result 'exit-code'.
Jul 09 04:27:34 exigov2 systemd[913]: Stopped KDE Session Management Server.
Jul 09 04:27:34 exigov2 systemd[913]: plasma-ksmserver.service: Consumed 11.471s CPU time.
Jul 09 04:27:34 exigov2 systemd[913]: Stopped KDE Global Shortcuts Server.
Jul 09 04:27:34 exigov2 systemd[913]: plasma-kglobalaccel.service: Consumed 2.055s CPU time.
Jul 09 04:27:34 exigov2 systemd[913]: plasma-gmenudbusmenuproxy.service: Main process exited, code=exited, status=1/FAILURE
Jul 09 04:27:34 exigov2 systemd[913]: plasma-gmenudbusmenuproxy.service: Failed with result 'exit-code'.
Jul 09 04:27:34 exigov2 systemd[913]: Stopped Proxies GTK DBus menus to a Plasma readable format.
Jul 09 04:27:34 exigov2 systemd[913]: plasma-gmenudbusmenuproxy.service: Consumed 1.226s CPU time.
Jul 09 04:27:34 exigov2 systemd[913]: plasma-xembedsniproxy.service: Main process exited, code=exited, status=1/FAILURE
Jul 09 04:27:34 exigov2 systemd[913]: plasma-xembedsniproxy.service: Failed with result 'exit-code'.
Jul 09 04:27:34 exigov2 systemd[913]: Stopped Handle legacy xembed system tray icons.
Jul 09 04:27:34 exigov2 systemd[913]: plasma-xembedsniproxy.service: Consumed 1.246s CPU time.
Jul 09 04:27:34 exigov2 systemd[913]: app-org.kde.kdeconnect.daemon@autostart.service: Main process exited, code=exited, status=1/FAILURE
Jul 09 04:27:34 exigov2 systemd[913]: app-org.kde.kdeconnect.daemon@autostart.service: Failed with result 'exit-code'.
Jul 09 04:27:34 exigov2 systemd[913]: Stopped KDE Connect.
Jul 09 04:27:34 exigov2 systemd[913]: app-org.kde.kdeconnect.daemon@autostart.service: Consumed 15.243s CPU time.
Jul 09 04:27:34 exigov2 systemd[913]: app-org.kde.yakuake@autostart.service: Main process exited, code=exited, status=1/FAILURE
Jul 09 04:27:34 exigov2 systemd[913]: app-org.kde.yakuake@autostart.service: Failed with result 'exit-code'.
Jul 09 04:27:34 exigov2 systemd[913]: Stopped Yakuake.
Jul 09 04:27:34 exigov2 systemd[913]: app-org.kde.yakuake@autostart.service: Consumed 5.746s CPU time.
Jul 09 04:27:34 exigov2 systemd[913]: Stopped Geoclue Demo agent.
Jul 09 04:27:34 exigov2 systemd[913]: app-pamac\x2dtray\x2dplasma@autostart.service: Main process exited, code=exited, status=1/FAILURE
Jul 09 04:27:34 exigov2 systemd[913]: app-pamac\x2dtray\x2dplasma@autostart.service: Failed with result 'exit-code'.
Jul 09 04:27:34 exigov2 systemd[913]: Stopped Update Notifier Tray Icon.
Jul 09 04:27:34 exigov2 systemd[913]: app-pamac\x2dtray\x2dplasma@autostart.service: Consumed 23.377s CPU time.
Jul 09 04:27:34 exigov2 systemd[913]: Stopped target Current graphical user session.
Jul 09 04:27:34 exigov2 systemd[913]: Stopped Virtual filesystem service - Media Transfer Protocol monitor.
Jul 09 04:27:34 exigov2 startplasma-x11[929]: org.kde.startup: "kdeinit5_shutdown" () exited with code 255
Jul 09 04:27:34 exigov2 systemd[913]: plasma-powerdevil.service: Main process exited, code=exited, status=1/FAILURE
Jul 09 04:27:34 exigov2 systemd[913]: plasma-powerdevil.service: Failed with result 'exit-code'.
Jul 09 04:27:34 exigov2 systemd[913]: Stopped Powerdevil.
Jul 09 04:27:34 exigov2 systemd[913]: plasma-powerdevil.service: Consumed 2.929s CPU time.
Jul 09 04:27:34 exigov2 systemd[913]: Stopped Virtual filesystem metadata service.
Jul 09 04:27:34 exigov2 systemd[913]: gvfs-metadata.service: Consumed 1.063s CPU time.
Jul 09 04:27:34 exigov2 systemd[913]: Stopped Accessibility services bus.
Jul 09 04:27:34 exigov2 systemd[913]: at-spi-dbus-bus.service: Consumed 3.749s CPU time.
Jul 09 04:27:34 exigov2 systemd[913]: Stopped Virtual filesystem service - digital camera monitor.
Jul 09 04:27:34 exigov2 systemd[913]: Stopped KActivityManager Activity manager Service.
Jul 09 04:27:34 exigov2 systemd[913]: plasma-kactivitymanagerd.service: Consumed 1min 33.178s CPU time.
Jul 09 04:27:34 exigov2 systemd[913]: Stopped Virtual filesystem service - disk device monitor.
Jul 09 04:27:34 exigov2 systemd[913]: Stopped Virtual filesystem service.
Jul 09 04:27:34 exigov2 systemd[913]: Stopped target KDE Plasma Workspace Core.
Jul 09 04:27:34 exigov2 systemd[913]: Stopping KDE Plasma Workspace...
Jul 09 04:27:34 exigov2 systemd[913]: Stopped target Session services which should run early before the graphical session is brought up.
Jul 09 04:27:34 exigov2 systemd[913]: Stopped Virtual filesystem service - Apple File Conduit monitor.
Jul 09 04:27:34 exigov2 systemd[1]: run-user-1000-gvfs.mount: Deactivated successfully.
Jul 09 04:27:34 exigov2 systemd[913]: Stopped Portal service.
Jul 09 04:27:34 exigov2 systemd[913]: xdg-desktop-portal.service: Consumed 1.105s CPU time.
Jul 09 04:27:34 exigov2 systemd[913]: Stopped flatpak document portal service.
Jul 09 04:27:34 exigov2 systemd[913]: Stopped Dolphin file manager.
Jul 09 04:27:34 exigov2 systemd[913]: plasma-kded.service: Main process exited, code=exited, status=1/FAILURE
Jul 09 04:27:34 exigov2 systemd[913]: plasma-kded.service: Failed with result 'exit-code'.
Jul 09 04:27:34 exigov2 systemd[913]: Stopped KDE Daemon.
Jul 09 04:27:34 exigov2 systemd[913]: plasma-kded.service: Consumed 24.125s CPU time.
Jul 09 04:27:34 exigov2 sddm-helper[911]: [PAM] Closing session
Jul 09 04:27:34 exigov2 sddm-helper[911]: pam_unix(sddm:session): session closed for user abhinav
Jul 09 04:27:34 exigov2 sddm-helper[911]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_close_session
Jul 09 04:27:34 exigov2 sddm-helper[911]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Jul 09 04:27:34 exigov2 sddm-helper[911]: [PAM] Ended.
Jul 09 04:27:34 exigov2 sddm[667]: Auth: sddm-helper exited successfully
Jul 09 04:27:34 exigov2 sddm[667]: Socket server stopping...
Jul 09 04:27:34 exigov2 systemd[1]: session-2.scope: Deactivated successfully.
Jul 09 04:27:34 exigov2 sddm[667]: Socket server stopped.
Jul 09 04:27:34 exigov2 sddm[667]: Display server stopping...
Jul 09 04:27:34 exigov2 systemd[913]: Stopped Baloo File Indexer Daemon.
Jul 09 04:27:34 exigov2 systemd[913]: kde-baloo.service: Consumed 1.515s CPU time.
Jul 09 04:27:34 exigov2 systemd[1]: session-2.scope: Consumed 1.984s CPU time.
Jul 09 04:27:34 exigov2 systemd-logind[538]: Session 2 logged out. Waiting for processes to exit.
Jul 09 04:27:34 exigov2 NetworkManager[599]: <info>  [1688857054.9796] device (wlp113s0): state change: activated -> deactivating (reason 'connection-removed', sys-iface-state: 'managed')
Jul 09 04:27:34 exigov2 NetworkManager[599]: <info>  [1688857054.9798] manager: NetworkManager state is now DISCONNECTING
Jul 09 04:27:34 exigov2 dbus-daemon[527]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.5' (uid=0 pid=599 comm="/usr/bin/NetworkManager --no-daemon")
Jul 09 04:27:34 exigov2 systemd-logind[538]: Removed session 2.
Jul 09 04:27:34 exigov2 systemd[1]: Starting Network Manager Script Dispatcher Service...
Jul 09 04:27:34 exigov2 pulseaudio[1339]: Error opening PCM device front:0: No such file or directory
Jul 09 04:27:34 exigov2 pulseaudio[1339]: Error opening PCM device front:0: No such file or directory
Jul 09 04:27:34 exigov2 systemd[1]: Started Network Manager Script Dispatcher Service.
Jul 09 04:27:34 exigov2 dbus-daemon[527]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jul 09 04:27:34 exigov2 bluetoothd[840]: Endpoint unregistered: sender=:1.76 path=/MediaEndpoint/A2DPSource/ldac_hq
Jul 09 04:27:34 exigov2 bluetoothd[840]: Endpoint unregistered: sender=:1.76 path=/MediaEndpoint/A2DPSource/ldac_sq
Jul 09 04:27:34 exigov2 bluetoothd[840]: Endpoint unregistered: sender=:1.76 path=/MediaEndpoint/A2DPSource/ldac_mq
Jul 09 04:27:34 exigov2 bluetoothd[840]: Endpoint unregistered: sender=:1.76 path=/MediaEndpoint/A2DPSink/aptx_hd
Jul 09 04:27:34 exigov2 bluetoothd[840]: Endpoint unregistered: sender=:1.76 path=/MediaEndpoint/A2DPSource/aptx_hd
Jul 09 04:27:34 exigov2 bluetoothd[840]: Endpoint unregistered: sender=:1.76 path=/MediaEndpoint/A2DPSink/aptx
Jul 09 04:27:34 exigov2 bluetoothd[840]: Endpoint unregistered: sender=:1.76 path=/MediaEndpoint/A2DPSource/aptx
Jul 09 04:27:34 exigov2 bluetoothd[840]: Endpoint unregistered: sender=:1.76 path=/MediaEndpoint/A2DPSink/sbc
Jul 09 04:27:34 exigov2 bluetoothd[840]: Endpoint unregistered: sender=:1.76 path=/MediaEndpoint/A2DPSource/sbc
Jul 09 04:27:34 exigov2 bluetoothd[840]: Endpoint unregistered: sender=:1.76 path=/MediaEndpoint/A2DPSink/sbc_xq_453
Jul 09 04:27:34 exigov2 bluetoothd[840]: Endpoint unregistered: sender=:1.76 path=/MediaEndpoint/A2DPSource/sbc_xq_453
Jul 09 04:27:34 exigov2 bluetoothd[840]: Endpoint unregistered: sender=:1.76 path=/MediaEndpoint/A2DPSink/sbc_xq_512
Jul 09 04:27:34 exigov2 bluetoothd[840]: Endpoint unregistered: sender=:1.76 path=/MediaEndpoint/A2DPSource/sbc_xq_512
Jul 09 04:27:34 exigov2 bluetoothd[840]: Endpoint unregistered: sender=:1.76 path=/MediaEndpoint/A2DPSink/sbc_xq_552
Jul 09 04:27:34 exigov2 bluetoothd[840]: Endpoint unregistered: sender=:1.76 path=/MediaEndpoint/A2DPSource/sbc_xq_552
Jul 09 04:27:34 exigov2 kernel: wlp113s0: deauthenticating from 8c:a3:99:b4:e3:63 by local choice (Reason: 3=DEAUTH_LEAVING)
Jul 09 04:27:35 exigov2 systemd[913]: Stopped KDE Plasma Workspace.
Jul 09 04:27:35 exigov2 systemd[913]: plasma-plasmashell.service: Consumed 1min 32.096s CPU time.
Jul 09 04:27:35 exigov2 systemd[913]: pulseaudio.service: Consumed 24.786s CPU time.
Jul 09 04:27:35 exigov2 systemd[913]: Stopped KRunner.
Jul 09 04:27:35 exigov2 systemd[913]: plasma-krunner.service: Consumed 8.737s CPU time.
Jul 09 04:27:35 exigov2 wpa_supplicant[817]: wlp113s0: CTRL-EVENT-DISCONNECTED bssid=8c:a3:99:b4:e3:63 reason=3 locally_generated=1
Jul 09 04:27:35 exigov2 wpa_supplicant[817]: wlp113s0: CTRL-EVENT-DSCP-POLICY clear_all
Jul 09 04:27:35 exigov2 NetworkManager[599]: <info>  [1688857055.1317] device (wlp113s0): supplicant interface state: completed -> disconnected
Jul 09 04:27:35 exigov2 NetworkManager[599]: <info>  [1688857055.1317] device (p2p-dev-wlp113s0): supplicant management interface state: completed -> disconnected
Jul 09 04:27:35 exigov2 NetworkManager[599]: <info>  [1688857055.1318] device (wlp113s0): state change: deactivating -> disconnected (reason 'connection-removed', sys-iface-state: 'managed')
Jul 09 04:27:35 exigov2 avahi-daemon[518]: Withdrawing address record for 2405:201:a414:3ba2:aebf:a871:7e00:79d2 on wlp113s0.
Jul 09 04:27:35 exigov2 NetworkManager[599]: <info>  [1688857055.1320] dhcp4 (wlp113s0): canceled DHCP transaction
Jul 09 04:27:35 exigov2 avahi-daemon[518]: Leaving mDNS multicast group on interface wlp113s0.IPv6 with address 2405:201:a414:3ba2:aebf:a871:7e00:79d2.
Jul 09 04:27:35 exigov2 NetworkManager[599]: <info>  [1688857055.1320] dhcp4 (wlp113s0): activation: beginning transaction (timeout in 45 seconds)
Jul 09 04:27:35 exigov2 avahi-daemon[518]: Joining mDNS multicast group on interface wlp113s0.IPv6 with address fe80::af36:37cf:4c98:e2a9.
Jul 09 04:27:35 exigov2 NetworkManager[599]: <info>  [1688857055.1320] dhcp4 (wlp113s0): state changed no lease
Jul 09 04:27:35 exigov2 avahi-daemon[518]: Registering new address record for fe80::af36:37cf:4c98:e2a9 on wlp113s0.*.
Jul 09 04:27:35 exigov2 NetworkManager[599]: <info>  [1688857055.1321] dhcp6 (wlp113s0): canceled DHCP transaction
Jul 09 04:27:35 exigov2 avahi-daemon[518]: Withdrawing address record for fe80::af36:37cf:4c98:e2a9 on wlp113s0.
Jul 09 04:27:35 exigov2 NetworkManager[599]: <info>  [1688857055.1321] dhcp6 (wlp113s0): activation: beginning transaction (timeout in 45 seconds)
Jul 09 04:27:35 exigov2 avahi-daemon[518]: Leaving mDNS multicast group on interface wlp113s0.IPv6 with address fe80::af36:37cf:4c98:e2a9.
Jul 09 04:27:35 exigov2 NetworkManager[599]: <info>  [1688857055.1321] dhcp6 (wlp113s0): state changed no lease
Jul 09 04:27:35 exigov2 avahi-daemon[518]: Interface wlp113s0.IPv6 no longer relevant for mDNS.
Jul 09 04:27:35 exigov2 sddm[667]: Display server stopped.
Jul 09 04:27:35 exigov2 sddm[667]: Running display stop script  "/usr/share/sddm/scripts/Xstop"
Jul 09 04:27:35 exigov2 sddm[667]: Removing display ":0" ...
Jul 09 04:27:35 exigov2 sddm[667]: Adding new display on vt 1 ...
Jul 09 04:27:35 exigov2 sddm[667]: Loading theme configuration from ""
Jul 09 04:27:35 exigov2 sddm[667]: Display server starting...
Jul 09 04:27:35 exigov2 sddm[667]: Adding cookie to "/var/run/sddm/{3024c7bd-a5f8-4044-bdbf-4282be80ca27}"
Jul 09 04:27:35 exigov2 NetworkManager[599]: <info>  [1688857055.1498] device (wlp113s0): set-hw-addr: set MAC address to 1A:50:5D:30:47:91 (scanning)
Jul 09 04:27:35 exigov2 avahi-daemon[518]: Interface wlp113s0.IPv4 no longer relevant for mDNS.
Jul 09 04:27:35 exigov2 avahi-daemon[518]: Leaving mDNS multicast group on interface wlp113s0.IPv4 with address 192.168.29.79.
Jul 09 04:27:35 exigov2 sddm[667]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt1 -auth /var/run/sddm/{3024c7bd-a5f8-4044-bdbf-4282be80ca27} -noreset -displayfd 18
Jul 09 04:27:35 exigov2 avahi-daemon[518]: Withdrawing address record for 192.168.29.79 on wlp113s0.
Jul 09 04:27:35 exigov2 avahi-daemon[518]: Joining mDNS multicast group on interface wlp113s0.IPv4 with address 192.168.29.79.
Jul 09 04:27:35 exigov2 avahi-daemon[518]: New relevant interface wlp113s0.IPv4 for mDNS.
Jul 09 04:27:35 exigov2 avahi-daemon[518]: Registering new address record for 192.168.29.79 on wlp113s0.IPv4.
Jul 09 04:27:35 exigov2 avahi-daemon[518]: Withdrawing address record for 192.168.29.79 on wlp113s0.
Jul 09 04:27:35 exigov2 avahi-daemon[518]: Leaving mDNS multicast group on interface wlp113s0.IPv4 with address 192.168.29.79.
Jul 09 04:27:35 exigov2 avahi-daemon[518]: Interface wlp113s0.IPv4 no longer relevant for mDNS.
Jul 09 04:27:35 exigov2 sddm[667]: Failed to read display number from pipe
Jul 09 04:27:35 exigov2 sddm[667]: Display server stopping...
Jul 09 04:27:35 exigov2 sddm[667]: Attempt 1 starting the Display server on vt 1 failed
Jul 09 04:27:35 exigov2 NetworkManager[599]: <info>  [1688857055.1982] manager: NetworkManager state is now DISCONNECTED
Jul 09 04:27:37 exigov2 sddm[667]: Display server starting...
Jul 09 04:27:37 exigov2 sddm[667]: Adding cookie to "/var/run/sddm/{3024c7bd-a5f8-4044-bdbf-4282be80ca27}"
Jul 09 04:27:37 exigov2 sddm[667]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt1 -auth /var/run/sddm/{3024c7bd-a5f8-4044-bdbf-4282be80ca27} -noreset -displayfd 17
Jul 09 04:27:37 exigov2 sddm[667]: Failed to read display number from pipe
Jul 09 04:27:37 exigov2 sddm[667]: Display server stopping...
Jul 09 04:27:37 exigov2 sddm[667]: Attempt 2 starting the Display server on vt 1 failed
Jul 09 04:27:39 exigov2 sddm[667]: Display server starting...
Jul 09 04:27:39 exigov2 sddm[667]: Adding cookie to "/var/run/sddm/{3024c7bd-a5f8-4044-bdbf-4282be80ca27}"
Jul 09 04:27:39 exigov2 sddm[667]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt1 -auth /var/run/sddm/{3024c7bd-a5f8-4044-bdbf-4282be80ca27} -noreset -displayfd 17
Jul 09 04:27:39 exigov2 sddm[667]: Failed to read display number from pipe
Jul 09 04:27:39 exigov2 sddm[667]: Display server stopping...
Jul 09 04:27:39 exigov2 sddm[667]: Attempt 3 starting the Display server on vt 1 failed
Jul 09 04:27:39 exigov2 sddm[667]: Could not start Display server on vt 1
Jul 09 04:27:40 exigov2 kernel: sysrq: This sysrq operation is disabled.
Jul 09 04:27:41 exigov2 kernel: sysrq: This sysrq operation is disabled.
Jul 09 04:27:41 exigov2 kernel: sysrq: This sysrq operation is disabled.
Jul 09 04:27:42 exigov2 kernel: sysrq: This sysrq operation is disabled.
Jul 09 04:27:42 exigov2 kernel: sysrq: This sysrq operation is disabled.
Jul 09 04:27:42 exigov2 kernel: sysrq: This sysrq operation is disabled.
Jul 09 04:27:42 exigov2 kernel: sysrq: This sysrq operation is disabled.
Jul 09 04:27:43 exigov2 kernel: sysrq: This sysrq operation is disabled.
Jul 09 04:27:43 exigov2 kernel: sysrq: This sysrq operation is disabled.
Jul 09 04:27:43 exigov2 kernel: sysrq: This sysrq operation is disabled.
Jul 09 04:27:43 exigov2 kernel: sysrq: This sysrq operation is disabled.
Jul 09 04:27:43 exigov2 kernel: sysrq: This sysrq operation is disabled.
Jul 09 04:27:43 exigov2 kernel: sysrq: This sysrq operation is disabled.
Jul 09 04:27:44 exigov2 kernel: sysrq: This sysrq operation is disabled.
Jul 09 04:27:44 exigov2 kernel: sysrq: This sysrq operation is disabled.
Jul 09 04:27:44 exigov2 kernel: sysrq: This sysrq operation is disabled.
Jul 09 04:27:45 exigov2 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Jul 09 04:27:45 exigov2 systemd[1]: Stopping User Manager for UID 1000...
Jul 09 04:27:45 exigov2 systemd[913]: Activating special unit Exit the Session...
Jul 09 04:27:45 exigov2 systemd[913]: Removed slice User Background Tasks Slice.
Jul 09 04:27:45 exigov2 org.freedesktop.secrets[1162]: discover_other_daemon: 1
Jul 09 04:27:45 exigov2 systemd[913]: background.slice: Consumed 1min 54.241s CPU time.
Jul 09 04:27:45 exigov2 systemd[913]: Stopped target Main User Target.
Jul 09 04:27:45 exigov2 systemd[913]: Stopping AppImageLauncher daemon...
Jul 09 04:27:45 exigov2 systemd[913]: Stopping D-Bus User Message Bus...
Jul 09 04:27:45 exigov2 systemd[913]: Stopping User preferences database...
Jul 09 04:27:45 exigov2 systemd[913]: Stopping GNOME Keyring daemon...
Jul 09 04:27:45 exigov2 systemd[913]: Stopping PipeWire Media Session Manager...
Jul 09 04:27:45 exigov2 systemd[913]: Stopped User preferences database.
Jul 09 04:27:45 exigov2 systemd[913]: Stopped GNOME Keyring daemon.
Jul 09 04:27:45 exigov2 systemd[913]: Stopped AppImageLauncher daemon.
Jul 09 04:27:45 exigov2 systemd[913]: appimagelauncherd.service: Consumed 27.540s CPU time.
Jul 09 04:27:45 exigov2 systemd[913]: Stopped D-Bus User Message Bus.
Jul 09 04:27:45 exigov2 systemd[913]: dbus.service: Consumed 3.997s CPU time.
Jul 09 04:27:45 exigov2 systemd[913]: Stopped PipeWire Media Session Manager.
Jul 09 04:27:45 exigov2 systemd[913]: Stopping PipeWire Multimedia Service...
Jul 09 04:27:45 exigov2 systemd[913]: Stopped PipeWire Multimedia Service.
Jul 09 04:28:25 exigov2 systemd-logind[538]: Power key pressed short.
Jul 09 04:28:25 exigov2 systemd-logind[538]: Powering off...
Jul 09 04:28:25 exigov2 systemd-logind[538]: System is powering down.

It started with the same GPU falling of the bus error at 04:25:08 after which it was stuck at kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state for some time and then the Xorg server died I think. I’ll try the last fix as you mentioned.

it looks like this is some power management issue, since it crashes when your pc is idle, could also be a bios setting…
so the video memory preserve option for nvidia, will probably not help, but try it anyway…
when it fails, check in bios for som aspm/ power management/ c-state settings…
and also post output from:
ls /etc/modprobe.d
find /etc/X11/ -name "*.conf"

This is definitely a bios issue cause today I tried to log in, the screen again went black. I tried using REISUB to reboot and it didn’t work, in fact nothing would have worked cause nothing started?
Basically there’s no journalctl entry for the boot as if it didn’t happen.

ul 10 04:26:08 exigov2 systemd[1]: Finished System Power Off.
Jul 10 04:26:08 exigov2 systemd[1]: Reached target System Power Off.
Jul 10 04:26:08 exigov2 systemd[1]: Shutting down.
Jul 10 04:26:09 exigov2 systemd-shutdown[1]: Syncing filesystems and block devices.
Jul 10 04:26:09 exigov2 systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Jul 10 04:26:09 exigov2 systemd-journald[280]: Received SIGTERM from PID 1 (systemd-shutdow).
Jul 10 04:26:09 exigov2 systemd-journald[280]: Journal stopped
-- Boot 4f4507a6cfa84b20b8373f4b5e69cc18 --
Jul 10 09:47:34 exigov2 kernel: microcode: microcode updated early to revision 0xf2, date = 2022-12-26
Jul 10 09:47:34 exigov2 kernel: Linux version 6.2.16-2-MANJARO (builduser@fv-az198-77) (gcc (GCC) 13.1.1 20230429, GNU ld (GNU Binutils) 2.40.0) #1 SMP PREEMPT_DYNAMIC Sun Jun  4 12:09:09 UTC 2023
Jul 10 09:47:34 exigov2 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.2-x86_64 root=UUID=31147878-f10d-4130-8b91-9b44b52cba29 rw "acpi_osi=Windows 2015" acpi_osi=! quiet apparmor=1 security=apparmor resume=UUID=73006f3f-9947-4e96-9b56-bad5aeafcb36 udev.log_priority=3 sysrq_always_enabled=1

Just no mention that I tried booting between 9:30 and 9:45. This is the most bizarre thing I have seen. Anyway, here’s the output of ls /etc/modprobe.d
mhwd-gpu.conf nvidia.conf nvidia-power-management.conf
and the output of find /etc/X11/ -name ".conf"*

/etc/X11/xorg.conf.d/00-keyboard.conf
/etc/X11/xorg.conf.d/30-touchpad.conf
/etc/X11/xorg.conf
/etc/X11/mhwd.d/nvidia.conf

The only thing that I have in mind is try booting into the windows if that works. If it’s a bios issue it should effect windows as well is my guess. Hoping for the best.

maybe i should have said that it is a possible bios issue + linux…
it is something that happens when your computer goes idle, so we can add some parameters that modify that, and that should fix it… thats why i wanted to check the configs, if there were already made some modifications regarding power management…
so post output from:

cat /etc/modprobe.d/nvidia.conf
*
cat /etc/modprobe.d/nvidia-power-management.conf
*
cat /etc/X11/xorg.conf
#(this xorg conf shouldnt be there)
*
cat /etc/X11/mhwd.d/nvidia.conf

I see, the corresponding outputs are

❯ cat /etc/modprobe.d/nvidia.conf       
options nvidia-drm modeset=1

❯ cat /etc/modprobe.d/nvidia-power-management.conf
options nvidia NVreg_PreserveVideoMemoryAllocations=1 NVreg_TemporaryFilePath=/var/tmp
❯ cat /etc/X11/xorg.conf                        
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 530.41.03

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 530.41.03

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "0"
EndSection

Section "Files"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "LG Display"
    HorizSync       53.3 - 66.7
    VertRefresh     48.0 - 60.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "NVIDIA GeForce GTX 1060"
EndSection

Section "Screen"

# Removed Option "metamodes" "1920x1080_60 +0+0"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "Stereo" "0"
    Option         "nvidiaXineramaInfoOrder" "DFP-1"
    Option         "metamodes" "1920x1080_60 +0+0"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection
❯ cat /etc/X11/mhwd.d/nvidia.conf               
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 465.31

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0"
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Unknown"
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
        Option "NoLogo" "1"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Extensions"
    Option         "COMPOSITE" "Enable"
EndSection

 
Section "InputClass"
    Identifier          "Keyboard Defaults"
    MatchIsKeyboard        "yes"
    Option              "XkbOptions" "terminate:ctrl_alt_bksp"
EndSection

post also output from:

grep . /sys/devices/system/cpu/cpu0/cpuidle/state*/name
cat /sys/module/intel_idle/parameters/max_cstate

output

❯ grep . /sys/devices/system/cpu/cpu0/cpuidle/state*/name
/sys/devices/system/cpu/cpu0/cpuidle/state0/name:POLL
/sys/devices/system/cpu/cpu0/cpuidle/state1/name:C1
/sys/devices/system/cpu/cpu0/cpuidle/state2/name:C1E
/sys/devices/system/cpu/cpu0/cpuidle/state3/name:C3
/sys/devices/system/cpu/cpu0/cpuidle/state4/name:C6
/sys/devices/system/cpu/cpu0/cpuidle/state5/name:C7s
/sys/devices/system/cpu/cpu0/cpuidle/state6/name:C8

❯ cat /sys/module/intel_idle/parameters/max_cstate 
9