Display randomly freezes and 2nd monitor goes unresponsive

Wolfyxon · 2023-03-29 21:21:16

Don't do that.

Why not?

Remove any kind of xorg.conf you have.

I meant to configure it, not revert it.
Also the old config seems to be invalid. When running nvidia-xconfig it outputs

PARSE ERROR: Parse error on line 27 of section
             Screen in file /etc/X11/xorg.conf.
             Unexpected EOF. Missing EndSection
             keyword?

before generating the new one. I don't see any errors.

Wolfyxon · 2023-03-30 07:31:52

I experimented with the config a bit.
When I use intel instead of modsetting: No freezing happens but xrandr doesn't detect HDMI
nvidia: only HDMI is recognized
modesetting: Both monitors works but freeze on heavy GPU usage (current)

Last edited by Wolfyxon (2023-03-30 07:32:04)

seth · 2023-03-30 12:22:27

Why not?

Because it creates a config full of garbage that can *not* handle a hybrid graphcis setup.

I meant to configure it, not revert it.

Yea, but not w/ the kind of nonsense that's in there right now.
If you want to configure it, remove any config you generated, post an xorg log to illustrate the base condition, read https://wiki.archlinux.org/title/NVIDIA_Optimus and make up your mind how you want to use the system, then configure it accordingly. If you've specific questions about that: ask.
Neither nvidia-whatever nor Xorg -configure will produce anything usefull, let alone what you specifically want here.

Wolfyxon · 2023-03-30 17:23:22

Ok I removed the xorg.conf.
Here's the log http://0x0.st/HHHM.txt

Forgot to mention. Every time it freezes, this log appears in the Xorg log

[  1227.185] (II) event5  - Corsair CORSAIR M55 RGB PRO Gaming Mouse: SYN_DROPPED event - some input events have been lost.

But it's probably nothing helpful.
EDIT: Wow I found a lot of people having the same issue as me, but there's no clear solution.

Last edited by Wolfyxon (2023-03-30 18:05:20)

seth · 2023-03-30 18:16:39

That just indicates that not all events could be processed.
Post the system journal of a (recent) boot w/ such freeze and then oc there's still https://bbs.archlinux.org/viewtopic.php … 5#p2087985

In #49 you wrote:

I think the LTS kernel isn't required.

You think that based on what?

Wolfyxon · 2023-03-30 19:00:42

journal: http://0x0.st/HHXs.txt

You think that based on what?

Because I noticed that when modesetting isn't used (and only 1 monitor is being detected) it doesn't freeze.
I think we should go back to the LTS kernel...

seth wrote:

What error?
Please post an updated dkms build log.

Pacman:

[wolfyxon@WolfArch linux515-lts]$ sudo pacman -U linux-lts515-5.15.102-1-x86_64.pkg.tar.zst linux-lts515-headers-5.15.102-1-x86_64.pkg.tar.zst
[sudo] password for wolfyxon: 
loading packages...
resolving dependencies...
looking for conflicting packages...

Packages (2) linux-lts515-5.15.102-1  linux-lts515-headers-5.15.102-1

Total Installed Size:  270.38 MiB

:: Proceed with installation? [Y/n] y
(2/2) checking keys in keyring                                [##################################] 100%
(2/2) checking package integrity                              [##################################] 100%
(2/2) loading package files                                   [##################################] 100%
(2/2) checking for file conflicts                             [##################################] 100%
(2/2) checking available disk space                           [##################################] 100%
:: Processing package changes...
(1/2) installing linux-lts515                                 [##################################] 100%
Optional dependencies for linux-lts515
    wireless-regdb: to set the correct wireless channels of your country
    linux-firmware: firmware images needed for some devices [installed]
(2/2) installing linux-lts515-headers                         [##################################] 100%
:: Running post-transaction hooks...
(1/4) Arming ConditionNeedsUpdate...
(2/4) Updating module dependencies...
(3/4) Install DKMS modules
==> dkms install --no-depmod nvidia/530.41.03 -k 5.15.102-1-lts515
Error! Bad return status for module build on kernel: 5.15.102-1-lts515 (x86_64)
Consult /var/lib/dkms/nvidia/530.41.03/build/make.log for more information.
==> WARNING: `dkms install --no-depmod nvidia/530.41.03 -k 5.15.102-1-lts515' exited 10
(4/4) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux-lts515.preset: 'default'
  -> -k /boot/vmlinuz-linux-lts515 -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts515.img --microcode /boot/intel-ucode.img
==> Starting build: '5.15.102-1-lts515'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-lts515.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-lts515.preset: 'fallback'
  -> -k /boot/vmlinuz-linux-lts515 -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts515-fallback.img -S autodetect --microcode /boot/intel-ucode.img
==> Starting build: '5.15.102-1-lts515'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-lts515-fallback.img'
==> Image generation successful

dkms log: http://0x0.st/HHXX.txt

seth · 2023-03-30 19:08:26

Because I noticed that when modesetting isn't used (and only 1 monitor is being detected) it doesn't freeze.

W/o seeing the log I'm gonna speculate that this is because you were only running on one GPU at the time (no optimus)

pacman -Ql linux-lts515 | grep objtool

Edit: also

pacman -Qs base-devel

Last edited by seth (2023-03-30 19:09:47)

Wolfyxon · 2023-03-30 19:13:51

[wolfyxon@WolfArch linux515-lts]$ pacman -Qs base-devel
local/base-devel 1-1
    Basic tools to build Arch Linux packages
local/binutils 2.40-4 (base-devel)
    A set of programs to assemble and manipulate binary and object files
local/gcc 12.2.1-2 (base-devel)
    The GNU Compiler Collection - C and C++ frontends
local/libtool 2.4.7+4+g1ec8fa28-2 (base-devel)
    A generic library support script

pacman -Ql linux-lts515 | grep objtool

It returned nothing.
Here's the output without grep: http://0x0.st/HHXT.txt

Last edited by Wolfyxon (2023-03-30 19:14:34)

seth · 2023-03-30 19:20:40

pacman -Ql linux-lts515-headers | grep objtool

Wolfyxon · 2023-03-30 19:22:34

linux-lts515-headers /usr/lib/modules/5.15.102-1-lts515/build/include/linux/objtool.h

seth · 2023-03-30 19:28:22

Yeah, that's not gonna cut it and that's why the dkms builds fail and it's also in the comments of https://aur.archlinux.org/packages/linux-lts515-headers
Try https://aur.archlinux.org/packages/linux-lts-515-git and https://aur.archlinux.org/packages/linu … it-headers instead.

Wolfyxon · 2023-03-30 19:31:46

Ok, I'll tell you the results tomorrow.
EDIT: Because it's probably not gonna finish compiling today + it's already night in my country

Last edited by Wolfyxon (2023-03-30 20:03:35)

Wolfyxon · 2023-03-30 20:04:15

Wait, are you sure these are the right packages? They both have the same git clone URL.

seth · 2023-03-30 20:16:32

The PKGBUILD will build both packages from the same source.

Bestest User · 2023-03-31 04:35:34

I've been having this same problem, I have an nvidia hybrid graphics optimus/prime setup with an external monitor connected with a USB-C to DP connection, and whenever a big discrete GPU rendered application opens or closes it will sometimes completely freeze the rendering of the second screen.
On my setup, only the display freezes, but things on that screen can still be interacted with all the same with no problems until, as in yours, the display is turned off and on in xrandr.
Is the current working theory to try on the LTS kernel?

seth · 2023-03-31 06:58:42

pacman -Qs xf86-video

Otherwise the current lts kernel would be too new, hence the linux-lts-515 hassle.

Wolfyxon · 2023-03-31 16:30:23

local/xf86-video-vesa 2.6.0-1 (xorg-drivers xorg)
    X.org vesa video driver

I successfully installed the kernel & headers without any errors (and I'm running it) but the freezing still happens.

Last edited by Wolfyxon (2023-03-31 16:58:10)

Wolfyxon · 2023-03-31 16:52:07

I doubt that it will help, but here's the pacman log of the update that made my display unstable.
http://0x0.st/HHqx.txt
I was running 6.0.9 before it. Sadly I can't downgrade since I deleted the caches long time ago.
NOTE: The previous update was 3 months earlier (I forgot to upgrade, now I'm doing it regularly every day)

Last edited by Wolfyxon (2023-03-31 16:56:11)

seth · 2023-03-31 19:03:34

https://wiki.archlinux.org/title/Downgr … ux_Archive

Edit:

[2023-02-21T17:47:41+0100] [ALPM] upgraded nvidia-dkms (520.56.06-2 -> 525.89.02-2)
[2023-02-21T17:47:41+0100] [ALPM] upgraded nvidia-settings (520.56.06-1 -> 525.89.02-1)

Downgrading nvidia might help (you're using dkms anyway), esp. if it's not the kernel.

Last edited by seth (2023-03-31 19:06:02)

Wolfyxon · 2023-03-31 20:58:52

I'm using the downgrade script.

:: Retrieving packages...
 nvidia-dkms-520.56.06-2-x86_64                                                                   41.8 MiB  2.83 MiB/s 00:15 [############################################################################] 100%
loading packages...
warning: downgrading package nvidia-dkms (530.41.03-1 => 520.56.06-2)
resolving dependencies...
warning: cannot resolve "nvidia-utils=520.56.06", a dependency of "nvidia-dkms"
:: The following package cannot be upgraded due to unresolvable dependencies:
      nvidia-dkms

:: Do you want to skip the above package for this upgrade? [y/N]

What should I do?

Last edited by Wolfyxon (2023-03-31 21:04:55)

seth · 2023-03-31 21:38:24

nvidia-utils and nvidia(-dkms) must be the same version, so downgrade them both.

Wolfyxon · 2023-04-02 12:36:56

I downgraded all nvidia related packages but now everything nvidia related stopped working. (2nd monitor, prime-run)
Pacman log

[2023-04-02T14:32:26+0200] [PACMAN] Running 'pacman -U https://archive.archlinux.org/packages/l/lib32-nvidia-utils/lib32-nvidia-utils-520.56.06-1-x86_64.pkg.tar.zst https://archive.archlinux.org/packages/n/nvidia/nvidia-520.56.06-2-x86_64.pkg.tar.zst https://archive.archlinux.org/packages/n/nvidia-settings/nvidia-settings-520.56.06-1-x86_64.pkg.tar.zst https://archive.archlinux.org/packages/n/nvidia-utils/nvidia-utils-520.56.06-2-x86_64.pkg.tar.zst'
[2023-04-02T14:33:42+0200] [ALPM] transaction started
[2023-04-02T14:33:43+0200] [ALPM] downgraded nvidia-utils (530.41.03-1 -> 520.56.06-2)
[2023-04-02T14:33:43+0200] [ALPM-SCRIPTLET] If you run into trouble with CUDA not being available, run nvidia-modprobe first.
[2023-04-02T14:33:43+0200] [ALPM-SCRIPTLET] If you use GDM on Wayland, you might have to run systemctl enable --now nvidia-resume.service
[2023-04-02T14:33:44+0200] [ALPM] downgraded lib32-nvidia-utils (530.41.03-1 -> 520.56.06-1)
[2023-04-02T14:33:44+0200] [ALPM] downgraded nvidia (530.41.03-2 -> 520.56.06-2)
[2023-04-02T14:33:44+0200] [ALPM] downgraded nvidia-settings (530.41.03-1 -> 520.56.06-1)
[2023-04-02T14:33:44+0200] [ALPM] transaction completed
[2023-04-02T14:33:44+0200] [ALPM] running '20-systemd-sysusers.hook'...
[2023-04-02T14:33:44+0200] [ALPM] running '30-systemd-daemon-reload.hook'...
[2023-04-02T14:33:45+0200] [ALPM] running '30-systemd-udev-reload.hook'...
[2023-04-02T14:33:45+0200] [ALPM] running '30-systemd-update.hook'...
[2023-04-02T14:33:45+0200] [ALPM] running '60-depmod.hook'...
[2023-04-02T14:33:48+0200] [ALPM] running 'dbus-reload.hook'...
[2023-04-02T14:33:48+0200] [ALPM] running 'update-desktop-database.hook'...
[2023-04-02T14:34:40+0200] [PACMAN] Running 'pacman -U https://archive.archlinux.org/packages/o/opencl-nvidia/opencl-nvidia-520.56.06-2-x86_64.pkg.tar.zst'
[2023-04-02T14:35:02+0200] [ALPM] transaction started
[2023-04-02T14:35:02+0200] [ALPM] downgraded opencl-nvidia (530.41.03-1 -> 520.56.06-2)
[2023-04-02T14:35:02+0200] [ALPM] transaction completed
[2023-04-02T14:35:02+0200] [ALPM] running '30-systemd-update.hook'...
[2023-04-02T14:37:33+0200] [PACMAN] Running 'pacman -S nvidia nvidia-utils opencl-nvidia lib32-nvidia-utils nvidia-settings'
[2023-04-02T14:37:47+0200] [ALPM] transaction started
[2023-04-02T14:37:50+0200] [ALPM] upgraded nvidia-utils (520.56.06-2 -> 530.41.03-1)
[2023-04-02T14:37:50+0200] [ALPM-SCRIPTLET] If you run into trouble with CUDA not being available, run nvidia-modprobe first.
[2023-04-02T14:37:50+0200] [ALPM-SCRIPTLET] If you use GDM on Wayland, you might have to run systemctl enable --now nvidia-resume.service
[2023-04-02T14:37:50+0200] [ALPM] upgraded nvidia (520.56.06-2 -> 530.41.03-2)
[2023-04-02T14:37:50+0200] [ALPM] upgraded opencl-nvidia (520.56.06-2 -> 530.41.03-1)
[2023-04-02T14:37:51+0200] [ALPM] upgraded lib32-nvidia-utils (520.56.06-1 -> 530.41.03-1)
[2023-04-02T14:37:51+0200] [ALPM] upgraded nvidia-settings (520.56.06-1 -> 530.41.03-1)
[2023-04-02T14:37:51+0200] [ALPM] transaction completed
[2023-04-02T14:37:51+0200] [ALPM] running '20-systemd-sysusers.hook'...
[2023-04-02T14:37:51+0200] [ALPM] running '30-systemd-daemon-reload.hook'...
[2023-04-02T14:37:51+0200] [ALPM] running '30-systemd-udev-reload.hook'...
[2023-04-02T14:37:51+0200] [ALPM] running '30-systemd-update.hook'...
[2023-04-02T14:37:51+0200] [ALPM] running '60-depmod.hook'...
[2023-04-02T14:37:56+0200] [ALPM] running 'dbus-reload.hook'...
[2023-04-02T14:37:56+0200] [ALPM] running 'update-desktop-database.hook'...

NOTE: Before doing so I tried to switch from nvidia-dkms to nvidia to see if it helps (it didn't)

Last edited by Wolfyxon (2023-04-02 13:16:23)

seth · 2023-04-02 13:40:12

NOTE: Before doing so I tried to switch from nvidia-dkms to nvidia to see if it helps (it didn't)

seth wrote:

you're using dkms anyway

The non-dkms package is compiled for the current kernel, downgrading that will require you to downgrade the kernel as well.
=> move bakc to the dkms package…

Wolfyxon · 2023-04-02 14:03:07

Ok I went back to nvidia-dkms.
I tried downgrading but now dkms build failed: http://0x0.st/HH6i.txt

[wolfyxon@WolfArch ~]$ sudo downgrade nvidia-dkms nvidia-utils lib32-nvidia-utils nvidia-settings opencl-nvidia
[sudo] password for wolfyxon: 
loading packages...
warning: downgrading package nvidia-settings (530.41.03-1 => 520.56.06-1)
warning: downgrading package opencl-nvidia (530.41.03-1 => 520.56.06-2)
warning: downgrading package lib32-nvidia-utils (530.41.03-1 => 520.56.06-1)
warning: downgrading package nvidia-dkms (530.41.03-1 => 520.56.06-2)
warning: downgrading package nvidia-utils (530.41.03-1 => 520.56.06-2)
resolving dependencies...
looking for conflicting packages...

Packages (5) lib32-nvidia-utils-520.56.06-1  nvidia-dkms-520.56.06-2  nvidia-settings-520.56.06-1  nvidia-utils-520.56.06-2  opencl-nvidia-520.56.06-2

Total Installed Size:  927.66 MiB
Net Upgrade Size:      -62.90 MiB

:: Proceed with installation? [Y/n] y
(5/5) checking keys in keyring                                                                                               [############################################################################] 100%
(5/5) checking package integrity                                                                                             [############################################################################] 100%
(5/5) loading package files                                                                                                  [############################################################################] 100%
(5/5) checking for file conflicts                                                                                            [############################################################################] 100%
(5/5) checking available disk space                                                                                          [############################################################################] 100%
:: Running pre-transaction hooks...
(1/1) Remove DKMS modules
==> dkms remove --no-depmod nvidia/530.41.03 -k 6.2.9-arch1-1
==> depmod 6.2.9-arch1-1
:: Processing package changes...
(1/5) downgrading nvidia-utils                                                                                               [############################################################################] 100%
If you run into trouble with CUDA not being available, run nvidia-modprobe first.
If you use GDM on Wayland, you might have to run systemctl enable --now nvidia-resume.service
(2/5) downgrading nvidia-settings                                                                                            [############################################################################] 100%
(3/5) downgrading opencl-nvidia                                                                                              [############################################################################] 100%
(4/5) downgrading lib32-nvidia-utils                                                                                         [############################################################################] 100%
(5/5) downgrading nvidia-dkms                                                                                                [############################################################################] 100%
:: Running post-transaction hooks...
(1/7) Creating system user accounts...
(2/7) Reloading system manager configuration...
(3/7) Reloading device manager configuration...
(4/7) Arming ConditionNeedsUpdate...
(5/7) Install DKMS modules
==> dkms install --no-depmod nvidia/520.56.06 -k 6.2.9-arch1-1
Error! Bad return status for module build on kernel: 6.2.9-arch1-1 (x86_64)
Consult /var/lib/dkms/nvidia/520.56.06/build/make.log for more information.
==> WARNING: `dkms install --no-depmod nvidia/520.56.06 -k 6.2.9-arch1-1' exited 10
(6/7) Reloading system bus configuration...
(7/7) Updating the desktop file MIME type cache...
add nvidia-dkms to IgnorePkg? [y/N] n

seth · 2023-04-02 14:15:53

/var/lib/dkms/nvidia/520.56.06/build/nvidia-drm/nvidia-drm-drv.c:245:21: error: ‘struct drm_mode_config’ has no member named ‘fb_base’

https://forums.developer.nvidia.com/t/4 … nel/243573
The 470 patch will of course not work, try the lts kernel.

Arch Linux

#51 2023-03-29 21:21:16

Re: Display randomly freezes and 2nd monitor goes unresponsive

#52 2023-03-30 07:31:52

Re: Display randomly freezes and 2nd monitor goes unresponsive

#53 2023-03-30 12:22:27

Re: Display randomly freezes and 2nd monitor goes unresponsive

#54 2023-03-30 17:23:22

Re: Display randomly freezes and 2nd monitor goes unresponsive

#55 2023-03-30 18:16:39

Re: Display randomly freezes and 2nd monitor goes unresponsive

#56 2023-03-30 19:00:42

Re: Display randomly freezes and 2nd monitor goes unresponsive

#57 2023-03-30 19:08:26

Re: Display randomly freezes and 2nd monitor goes unresponsive

#58 2023-03-30 19:13:51

Re: Display randomly freezes and 2nd monitor goes unresponsive

#59 2023-03-30 19:20:40

Re: Display randomly freezes and 2nd monitor goes unresponsive

#60 2023-03-30 19:22:34

Re: Display randomly freezes and 2nd monitor goes unresponsive

#61 2023-03-30 19:28:22

Re: Display randomly freezes and 2nd monitor goes unresponsive

#62 2023-03-30 19:31:46

Re: Display randomly freezes and 2nd monitor goes unresponsive

#63 2023-03-30 20:04:15

Re: Display randomly freezes and 2nd monitor goes unresponsive

#64 2023-03-30 20:16:32

Re: Display randomly freezes and 2nd monitor goes unresponsive

#65 2023-03-31 04:35:34

Re: Display randomly freezes and 2nd monitor goes unresponsive

#66 2023-03-31 06:58:42

Re: Display randomly freezes and 2nd monitor goes unresponsive

#67 2023-03-31 16:30:23

Re: Display randomly freezes and 2nd monitor goes unresponsive

#68 2023-03-31 16:52:07

Re: Display randomly freezes and 2nd monitor goes unresponsive

#69 2023-03-31 19:03:34

Re: Display randomly freezes and 2nd monitor goes unresponsive

#70 2023-03-31 20:58:52

Re: Display randomly freezes and 2nd monitor goes unresponsive

#71 2023-03-31 21:38:24

Re: Display randomly freezes and 2nd monitor goes unresponsive

#72 2023-04-02 12:36:56

Re: Display randomly freezes and 2nd monitor goes unresponsive

#73 2023-04-02 13:40:12

Re: Display randomly freezes and 2nd monitor goes unresponsive

#74 2023-04-02 14:03:07

Re: Display randomly freezes and 2nd monitor goes unresponsive

#75 2023-04-02 14:15:53

Re: Display randomly freezes and 2nd monitor goes unresponsive

Board footer