Hello,
I had a PC Freeze and wasn’t doing anything special. I was about to maximize a Firefox Window on my KDE Desktop after i was done watching a movie and out of nowhere my PC Froze… TTY wasn’t working but REISUB commands still was doing his job.
After a restart here is the output:
$ journalctl -p err -b -1
Jun 25 23:14:32 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Jun 25 23:14:33 koboldx-z170 kernel: irq 16: nobody cared (try booting with the "irqpoll" option)
Jun 25 23:14:33 koboldx-z170 kernel: handlers:
Jun 25 23:14:33 koboldx-z170 kernel: [<00000000eeaa766e>] i801_isr [i2c_i801]
Jun 25 23:14:33 koboldx-z170 kernel: [<000000007f4ac70b>] azx_interrupt [snd_hda_codec]
Jun 25 23:14:33 koboldx-z170 kernel: Disabling IRQ #16
Jun 25 23:14:37 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:0:0:0x0000000f
Jun 25 23:14:37 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:2:0:0x0000000f
Jun 25 23:14:37 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:4:0:0x0000000f
Jun 25 23:14:37 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Jun 25 23:14:37 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: DP-4: Failed to disable DisplayPort audio stream-3
Looks like you are on X11 and that the freeze has something to do with kernel mode setting.
What is the output of sudo cat /sys/module/nvidia_drm/parameters/modeset ?
On Wayland at least, the modeset=1 kernel module parameter needs to be enabled (should already be enabled by default on nvidia 575). Not sure about on X11.
I just had a second freeze, which i had while i minimized a flatpak game:
Jun 27 01:38:24 koboldx-z170 kernel: irq 16: nobody cared (try booting with the "irqpoll" option)
Jun 27 01:38:24 koboldx-z170 kernel: handlers:
Jun 27 01:38:24 koboldx-z170 kernel: [<00000000140ec8cf>] i801_isr [i2c_i801]
Jun 27 01:38:24 koboldx-z170 kernel: [<0000000052f1e304>] azx_interrupt [snd_hda_codec]
Jun 27 01:38:24 koboldx-z170 kernel: Disabling IRQ #16
Jun 27 01:38:24 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Jun 27 01:38:25 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:0:0:0x0000000f
Jun 27 01:38:25 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:2:0:0x0000000f
Jun 27 01:38:25 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:4:0:0x0000000f
Jun 27 01:38:25 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Jun 27 01:38:25 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: DP-4: Failed to disable DisplayPort audio stream-3
Nothing is happening when i type in that command
But after i openend that path in dolphin and double clicked on modeset… my PC froze again with that info after i did REISUB again (right after the reboot… double freeze):
Jun 27 01:50:19 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6>
Jun 27 01:50:19 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:0>
Jun 27 01:50:19 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:2>
Jun 27 01:50:19 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:4>
Jun 27 01:50:19 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6>
Jun 27 01:50:19 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: DP-4: Failed to disable DisplayPort audio stream-3
Jun 27 01:50:20 koboldx-z170 kernel: irq 16: nobody cared (try booting with the "irqpoll" option)
Jun 27 01:50:20 koboldx-z170 kernel: handlers:
Jun 27 01:50:20 koboldx-z170 kernel: [<00000000224a6d5d>] i801_isr [i2c_i801]
Jun 27 01:50:20 koboldx-z170 kernel: [<00000000e4692f78>] azx_interrupt [snd_hda_codec]
Jun 27 01:50:20 koboldx-z170 kernel: Disabling IRQ #16
Jun 27 01:54:28 koboldx-z170 systemd[1]: Failed to start CUPS Scheduler.
Is that normal that a double mouse click lead to a system freeze when clicking on modeset in dolphin?
Edit:
I was wrong…
I openend with sudo nano and it showed only a Y that was in there.
Just the: Y and nothing else.
$ sudo cat /sys/module/nvidia_drm/parameters/modeset
Y
Yeah of course… its in my system settings in my first post.
$ cat /etc/default/grub
# GRUB boot loader configuration
GRUB_DEFAULT=saved
GRUB_TIMEOUT=1
GRUB_DISTRIBUTOR="Manjaro"
GRUB_CMDLINE_LINUX_DEFAULT="sysrq_always_enabled=1 retbleed=off resume=UUID=717b267e-7322-4bf9-a840-f1210d422d1a udev.log_priority=3"
GRUB_CMDLINE_LINUX=""
# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
# Uncomment to enable booting from LUKS encrypted devices
#GRUB_ENABLE_CRYPTODISK=y
# Set to 'countdown' or 'menu' to change timeout behavior,
# press ESC key to display menu.
GRUB_TIMEOUT_STYLE=hidden
# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console
# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command 'videoinfo'
GRUB_GFXMODE=auto
# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep
# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true
# Uncomment and set to the desired menu colors. Used by normal and wallpaper
# modes only. Entries specified as foreground/background.
GRUB_COLOR_NORMAL="light-gray/black"
GRUB_COLOR_HIGHLIGHT="green/black"
# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/usr/share/grub/background.png"
GRUB_THEME="/usr/share/grub/themes/manjaro/theme.txt"
# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"
# Uncomment to make GRUB remember the last selection. This requires
# setting 'GRUB_DEFAULT=saved' above.
GRUB_SAVEDEFAULT=true
# Uncomment to disable submenus in boot menu
#GRUB_DISABLE_SUBMENU=y
# Uncomment this option to enable os-prober execution in the grub-mkconfig command
GRUB_DISABLE_OS_PROBER=true
# Uncomment to ensure that the root filesystem is mounted read-only so that
# systemd-fsck can run the check automatically. We use 'fsck' by default, which
# needs 'rw' as boot parameter, to avoid delay in boot-time. 'fsck' needs to be
# removed from 'mkinitcpio.conf' to make 'systemd-fsck' work.
# See also Arch-Wiki: https://wiki.archlinux.org/index.php/Fsck#Boot_time_checking
#GRUB_ROOT_FS_RO=true
$ cat /etc/mkinitcpio.conf
# 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=(usbhid xhci_hcd)
MODULES=()
# 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 modconf block filesystems fsck)
#
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS=(base udev modconf block filesystems fsck)
#
## This setup assembles a mdadm array with an encrypted root file system.
## Note: See 'mkinitcpio -H mdadm_udev' for more information on RAID devices.
# HOOKS=(base udev modconf keyboard keymap consolefont block mdadm_udev encrypt filesystems fsck)
#
## This setup loads an lvm2 volume group.
# HOOKS=(base udev modconf block lvm2 filesystems fsck)
#
## This will create a systemd based initramfs which loads an encrypted root filesystem.
# HOOKS=(base systemd autodetect modconf kms keyboard sd-vconsole sd-encrypt block filesystems fsck)
#
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr and fsck hooks.
HOOKS=(base udev autodetect microcode modconf kms keyboard keymap consolefont block filesystems fsck)
# COMPRESSION
# Use this to compress the initramfs image. By default, zstd compression
# is used for Linux ≥ 5.9 and gzip compression is used for Linux < 5.9.
# Use 'cat' to create an uncompressed image.
#COMPRESSION="zstd"
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()
# MODULES_DECOMPRESS
# Decompress loadable kernel modules and their firmware during initramfs
# creation. Switch (yes/no).
# Enable to allow further decreasing image size when using high compression
# (e.g. xz -9e or zstd --long --ultra -22) at the expense of increased RAM usage
# at early boot.
# Note that any compressed files will be placed in the uncompressed early CPIO
# to avoid double compression.
#MODULES_DECOMPRESS="no"
Before you head down that route, I would try Wayland first to see if you still experience freezes.
Addendum:
Also, the nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state error appears in the thread below - the problem there is at least partly power related, so it may or may not apply to you.
I have a Multi Rail GPU Power Supply, i already splitted 2 rails into the GPU.
Anyways, after several investigation i think my freezes are gaming related… Specially related to the newest Nvidia Flatpak Driver… its not the first time where i face system freezes because of some buggy Flatpak Nvidia drivers that lead to system freezes:
$ flatpak list
Name Application ID Version Branch Installation
Beyond All Reason info.beyondallreason.bar 1.2988.0.1 stable system
Freedesktop Platform org.freedesktop.Platform freedesktop-sdk-24.08.22 24.08 system
Mesa org.freedesktop.Platform.GL.default 25.1.3 24.08 system
Mesa (Extra) org.freedesktop.Platform.GL.default 25.1.3 24.08extra system
nvidia-575-64 org.freedesktop.Platform.GL.nvidia-575-64 1.4 system
openh264 org.freedesktop.Platform.openh264 2.5.1 2.5.1 system
Damn i wish i could download a older Nvidia Flatpak driver as 575.64 the second last version was running fine.
@Kobold Didn’t realise that nvidia drivers could be installed from flatpak.
Also didn’t realise that you had already experienced a near-exact occurrence of the same error last year, and that you had already posted about it.
If you had led with that, it would have saved some time.
If I were you, I would remove the flatpak nvidia driver, install linux612-nvidia / linux612-nvidia-open from the extra repo, install the game from the AUR as @Xephon suggested, fully configure the driver (early module loading, etc), and see if you still have issues.
Yeah sry, after i faced that first freeze where i created this topic, it was 20min later after my flatpak game closed and when my system froze.
That’s also one of confusion problem’s when we are on a rolling release distro, because after a release update i was think that it could be related to the OS Driver.
It took time till a realised that it could be related to the Flatpak Nvidia Driver again
