Sudden Unresponsiveness, nvidia-modeset Running Wild

Out of a sudden without me doing anything special my PC suddenly starts to hang and becomes nearly unresponsive, the process nvidia-modeset starts to take over a core (or two?). It's hard to close the running applications and reboot the PC.

Jän 17 22:42:49 runlikehell dbus-daemon[551]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.5' (uid=0 pid=557 comm="/usr/bin/NetworkManager --no-da>
Jän 17 22:42:49 runlikehell dbus-daemon[551]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
Jän 17 22:45:03 runlikehell kernel: NVRM: GPU at PCI:0000:07:00: GPU-e7a7f7d7-0e9c-e22e-3f65-a579688ede47
Jän 17 22:45:03 runlikehell kernel: NVRM: GPU Board Serial Number: 
Jän 17 22:45:03 runlikehell kernel: NVRM: Xid (PCI:0000:07:00): 61, pid=622, 0cec(3098) 00000000 00000000
Jän 17 22:46:19 runlikehell dbus-daemon[551]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.5' (uid=0 pid=557 comm="/usr/bin/NetworkManager --no-da>
Jän 17 22:46:19 runlikehell dbus-daemon[551]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
Jän 17 22:47:49 runlikehell dbus-daemon[551]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.5' (uid=0 pid=557 comm="/usr/bin/NetworkManager --no-da>
Jän 17 22:47:49 runlikehell dbus-daemon[551]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
Jän 17 22:48:46 runlikehell msm_notifier[1070]: Shutting down MSM Notifier...
Jän 17 22:48:46 runlikehell systemd-logind[558]: System is rebooting.
-- Subject: System shutdown initiated
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/technical-issues-and-assistance
-- 
-- System shutdown has been initiated. The shutdown has now begun and
-- all system services are terminated and all file systems unmounted.

The line containing NVRM: Xid (PCI:0000:07:00) seems to be where the problem starts.

$ inxi -Fxxz
System:
  Host: runlikehell Kernel: 4.19.91-1-MANJARO x86_64 bits: 64 compiler: gcc 
  v: 9.2.0 Desktop: Xfce 4.14.1 tk: Gtk 3.24.12 wm: xfwm4 dm: LightDM 
  Distro: Manjaro Linux 
Machine:
  Type: Desktop Mobo: Gigabyte model: X570 GAMING X v: x.x serial: <filter> 
  UEFI [Legacy]: American Megatrends v: F11 date: 12/06/2019 
CPU:
  Topology: 8-Core model: AMD Ryzen 7 3700X bits: 64 type: MT MCP arch: Zen 
  L2 cache: 4096 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 114985 
  Speed: 2109 MHz min/max: 2200/3600 MHz Core speeds (MHz): 1: 2109 2: 2250 
  3: 3634 4: 2229 5: 2516 6: 2124 7: 3803 8: 2675 9: 3830 10: 2261 11: 3736 
  12: 2163 13: 2922 14: 3685 15: 2096 16: 2336 
Graphics:
  Device-1: NVIDIA TU106 [GeForce RTX 2060 Rev. A] vendor: Micro-Star MSI 
  driver: nvidia v: 440.44 bus ID: 07:00.0 chip ID: 10de:1f08 
  Display: x11 server: X.Org 1.20.6 driver: nvidia 
  resolution: 1920x1080~60Hz, 1920x1080~60Hz 
  OpenGL: renderer: GeForce RTX 2060/PCIe/SSE2 v: 4.6.0 NVIDIA 440.44 
  direct render: Yes 
Audio:
  Device-1: NVIDIA TU106 High Definition Audio vendor: Micro-Star MSI 
  driver: snd_hda_intel v: kernel bus ID: 07:00.1 chip ID: 10de:10f9 
  Device-2: AMD Starship/Matisse HD Audio vendor: Gigabyte 
  driver: snd_hda_intel v: kernel bus ID: 09:00.4 chip ID: 1022:1487 
  Sound Server: ALSA v: k4.19.91-1-MANJARO 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: Gigabyte driver: r8168 v: 8.047.05-NAPI port: f000 bus ID: 03:00.0 
  chip ID: 10ec:8168 
  IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 223.57 GiB used: 133.91 GiB (59.9%) 
  ID-1: /dev/sda vendor: Kingston model: SHSS37A240G size: 223.57 GiB 
  speed: 6.0 Gb/s serial: <filter> 
Partition:
  ID-1: / size: 204.82 GiB used: 133.91 GiB (65.4%) fs: ext4 dev: /dev/sda3 
  ID-2: swap-1 size: 15.26 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 
Sensors:
  Message: No sensors data was found. Is sensors configured? 
Info:
  Processes: 316 Uptime: 6m Memory: 15.67 GiB used: 2.98 GiB (19.0%) 
  Init: systemd v: 242 Compilers: gcc: 9.2.0 Shell: bash v: 5.0.11 
  running in: xfce4-terminal inxi: 3.0.37 

Today it happened twice, there are days when it doesn't happen. It's really strange. It started with either the latest bigger update or the one before that.

Can anyone please help me out here?

Maybe you meant to share more of that log?
Its mainly just some NetworkManager stuff and initializing reboot.
(and yes some gpu output .. but its just a print of the serial number and pci address ...)

Can you please be more specific what you need? If you look at the timestamps there isn't much going on before that. Afterwards it's a hell lot of shutting down log. Too big for a post.

Maybe some other log makes sense? Which one? Some command output?

Wherever and however you found/saw nvidia-modeset 'running wild'.

(besides that the 'usual' logs are probably to be found through dmesg and journalctl)

I saw in the XFCE-panel with the CPU-load that two cores were up at 100% and after I succeeded to login on another TTY and did htop I noticed nvidia-modeset was causing that. So I can't prove that part by logs or something (at least I don't know how).

The log in the OP is from journalctl -xe -b -1 and dmesg doesn't seem to hold info from previous sessions.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by