Weird micro-freezes on fresh installation caused by NVIDIA drivers for Geforce GTX 1050 Ti

Dear Manjaro users,

I've been running Manjaro for a few weeks and encountered a weird bug. Whenever I'm using the NVIDIA drivers for my GPU, I get a short freeze around once every second, which renders my system largely unusable. I supposed I'd done something wrong and resorted to the free video-linux drivers, those didn't have the problem, but performance was a lot worse overall (apart from the bug). But today, I did a fresh install and the bug persists, so I guess this might be the right moment to ask.

My GPU is a Geforce GTX 1050 Ti, the problem appears with any of the nvidia-video drivers offered to me by mhwd, namely versions 440xx, 435xx, 430xx, 418xx and 390xx. As I said, I did a fresh install and a full upgrade ("pacman -Syyu"), then installed the 440xx drivers, nothing else.

"inxi -Fxxxz" gives the following:

System:
  Host: fabian-desktop-manjaro Kernel: 5.4.40-1-MANJARO x86_64 bits: 64 
  compiler: gcc v: 9.3.0 Desktop: Xfce 4.14.2 tk: Gtk 3.24.20 
  info: xfce4-panel wm: xfwm4 dm: LightDM 1.30.0 Distro: Manjaro Linux 
Machine:
  Type: Desktop Mobo: MSI model: 970A-G43 (MS-7693) v: 3.0 serial: <filter> 
  BIOS: American Megatrends v: 10.3 date: 03/28/2013 
CPU:
  Topology: 6-Core model: AMD FX-6300 bits: 64 type: MCP arch: Bulldozer 
  L2 cache: 2048 KiB 
  flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 42015 
  Speed: 1471 MHz min/max: 1400/3500 MHz boost: enabled Core speeds (MHz): 
  1: 1405 2: 1409 3: 1400 4: 1399 5: 1399 6: 1399 
Graphics:
  Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] 
  vendor: Gigabyte GV-N105TOC-4GD driver: nvidia v: 440.82 bus ID: 01:00.0 
  chip ID: 10de:1c82 
  Display: x11 server: X.Org 1.20.8 driver: nvidia 
  resolution: 1920x1080~60Hz 
  OpenGL: renderer: GeForce GTX 1050 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 440.82 
  direct render: Yes 
Audio:
  Device-1: AMD SBx00 Azalia vendor: Micro-Star MSI driver: snd_hda_intel 
  v: kernel bus ID: 00:14.2 chip ID: 1002:4383 
  Device-2: NVIDIA GP107GL High Definition Audio vendor: Gigabyte 
  driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:0fb9 
  Device-3: Microdia SNAPPY Smart Webcam type: USB 
  driver: snd-usb-audio,uvcvideo bus ID: 1-2:3 chip ID: 0c45:054a 
  Sound Server: ALSA v: k5.4.40-1-MANJARO 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: Micro-Star MSI driver: r8169 v: kernel port: d000 bus ID: 05:00.0 
  chip ID: 10ec:8168 
  IF: enp5s0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 447.14 GiB used: 8.90 GiB (2.0%) 
  ID-1: /dev/sda vendor: SanDisk model: SDSSDA240G size: 223.57 GiB 
  speed: 6.0 Gb/s serial: <filter> rev: 10RL scheme: MBR 
  ID-2: /dev/sdb vendor: SanDisk model: SSD PLUS 240GB size: 223.57 GiB 
  speed: 6.0 Gb/s serial: <filter> rev: 04RL scheme: MBR 
Partition:
  ID-1: / size: 219.06 GiB used: 8.90 GiB (4.1%) fs: ext4 dev: /dev/sdb1 
Sensors:
  System Temperatures: cpu: 34.5 C mobo: N/A gpu: nvidia temp: 43 C 
  Fan Speeds (RPM): N/A gpu: nvidia fan: 0% 
Info:
  Processes: 194 Uptime: 10m Memory: 7.73 GiB used: 1.31 GiB (16.9%) 
  Init: systemd v: 245 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.16 
  running in: xfce4-terminal inxi: 3.0.37 

Thanks in advance, and apologies if the answer is obvious. On my old install, I tried most of the answers to similar questions, without any success, so I did not repeat that on the fresh install.

Fabian

Have you tried different kernels, like 4.19 or 5.6?

have you checked in the log

sudo journalctl -b0 -p4

Hello stephane,

output is as follows:

-- Logs begin at Fri 2020-05-22 15:02:34 CEST, end at Fri 2020-05-22 17:02:41 CEST. --
Mai 22 16:44:11 fabian-desktop-manjaro kernel: ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x0000000000000000/0x1 (20190816/tbfadt-615)
Mai 22 16:44:11 fabian-desktop-manjaro kernel: Warning! ehci_hcd should always be loaded before uhci_hcd and ohci_hcd, not after
Mai 22 16:44:11 fabian-desktop-manjaro kernel: ata1.01: limited to UDMA/33 due to 40-wire cable
Mai 22 16:44:11 fabian-desktop-manjaro kernel: nvidia: loading out-of-tree module taints kernel.
Mai 22 16:44:11 fabian-desktop-manjaro kernel: nvidia: module license 'NVIDIA' taints kernel.
Mai 22 16:44:11 fabian-desktop-manjaro kernel: Disabling lock debugging due to kernel taint
Mai 22 16:44:11 fabian-desktop-manjaro kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  440.82  Wed Apr  1 20:04:33 UTC 2020
Mai 22 16:44:12 fabian-desktop-manjaro kernel: r8169 0000:05:00.0: can't disable ASPM; OS doesn't have ASPM control
Mai 22 16:44:12 fabian-desktop-manjaro systemd-vconsole-setup[637]: KD_FONT_OP_GET failed while trying to get the font metadata: Function not implemented
Mai 22 16:44:12 fabian-desktop-manjaro systemd-vconsole-setup[637]: Fonts will not be copied to remaining consoles
Mai 22 16:44:13 fabian-desktop-manjaro kernel: usb 1-2: 3:1: cannot get freq at ep 0x84
Mai 22 16:44:13 fabian-desktop-manjaro kernel: usb 1-2: Warning! Unlikely big volume range (=8191), cval->res is probably wrong.
Mai 22 16:44:13 fabian-desktop-manjaro kernel: usb 1-2: [3] FU [Mic Capture Volume] ch = 1, val = 0/8191/1
Mai 22 16:44:13 fabian-desktop-manjaro kernel: uvcvideo 1-2:1.0: Entity type for entity Extension 4 was not initialized!
Mai 22 16:44:13 fabian-desktop-manjaro kernel: uvcvideo 1-2:1.0: Entity type for entity Processing 3 was not initialized!
Mai 22 16:44:13 fabian-desktop-manjaro kernel: uvcvideo 1-2:1.0: Entity type for entity Camera 1 was not initialized!
Mai 22 16:44:14 fabian-desktop-manjaro kernel: kauditd_printk_skb: 25 callbacks suppressed
Mai 22 16:44:14 fabian-desktop-manjaro kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window]
Mai 22 16:44:14 fabian-desktop-manjaro kernel: caller _nv000908rm+0x1bf/0x1f0 [nvidia] mapping multiple BARs
Mai 22 16:44:25 fabian-desktop-manjaro lightdm[1139]: gkr-pam: unable to locate daemon control file
Mai 22 16:44:28 fabian-desktop-manjaro kernel: kauditd_printk_skb: 7 callbacks suppressed
Mai 22 16:44:29 fabian-desktop-manjaro kernel: usb 1-2: 3:1: cannot get freq at ep 0x84
Mai 22 16:44:29 fabian-desktop-manjaro blueman-mechani[1438]: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
Mai 22 16:44:29 fabian-desktop-manjaro kernel: usb 1-2: 3:1: cannot get freq at ep 0x84
Mai 22 16:52:39 fabian-desktop-manjaro manjaro-settings-manager[2382]: Attribute Qt::AA_EnableHighDpiScaling must be set before QCoreApplication is created.
Mai 22 16:52:39 fabian-desktop-manjaro manjaro-settings-manager[2382]: Attribute Qt::AA_EnableHighDpiScaling must be set before QCoreApplication is created.
Mai 22 17:02:06 fabian-desktop-manjaro manjaro-settings-manager[2579]: Attribute Qt::AA_EnableHighDpiScaling must be set before QCoreApplication is created.
Mai 22 17:02:06 fabian-desktop-manjaro manjaro-settings-manager[2579]: Attribute Qt::AA_EnableHighDpiScaling must be set before QCoreApplication is created.
Mai 22 17:02:31 fabian-desktop-manjaro manjaro-settings-manager[2591]: Attribute Qt::AA_EnableHighDpiScaling must be set before QCoreApplication is created.
Mai 22 17:02:31 fabian-desktop-manjaro manjaro-settings-manager[2591]: Attribute Qt::AA_EnableHighDpiScaling must be set before QCoreApplication is created.
Mai 22 15:03:17 fabian-desktop-manjaro manjaro-settings-manager[2661]: Attribute Qt::AA_EnableHighDpiScaling must be set before QCoreApplication is created.
Mai 22 15:03:17 fabian-desktop-manjaro manjaro-settings-manager[2661]: Attribute Qt::AA_EnableHighDpiScaling must be set before QCoreApplication is created.

Hello kresimir,
yes, I did that on the previous install, both with 4.19.122-1 and 5.6.10_rt5-1, to no avail, but I can try it again.

check this point , if cables are all ok
( see sudo journalctl -b0 | grep ata )

It's still the same on all three kernel versions.

Cable should be fine for all I know, isn't it a hard-drive cable anyways?

The message persists when using video-linux, while the bug is gone then. Is it still a possible cause?

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

Forum kindly sponsored by