Nvidia logging problems

Ask Fedora
, , , ,
1

I am having a ton of the following errors, all of which pop up as a notification at the top of the screen about every 5 seconds.

Jul 16 12:06:54 eagle.home.domain gnome-shell[2155829]: error: Execution of nvidia-settings -q GPUUtilization -q [GPU]/GPUCoreTemp -q UsedDedicatedGPUMemory -q TotalDedicatedGPUMemory -q GPUCurrentFanSpeed -t failed:: ERROR: Error resolving target specification '' (No targets match target specification), specified in query 'GPUUtilization'.
Jul 16 12:06:59 eagle.home.domain gnome-shell[2155829]: error: Execution of nvidia-settings -q GPUUtilization -q [GPU]/GPUCoreTemp -q UsedDedicatedGPUMemory -q TotalDedicatedGPUMemory -q GPUCurrentFanSpeed -t failed:: ERROR: Error resolving target specification '' (No targets match target specification), specified in query 'GPUUtilization'.
Jul 16 12:07:04 eagle.home.domain gnome-shell[2155829]: error: Execution of nvidia-settings -q GPUUtilization -q [GPU]/GPUCoreTemp -q UsedDedicatedGPUMemory -q TotalDedicatedGPUMemory -q GPUCurrentFanSpeed -t failed:: ERROR: Error resolving target specification '' (No targets match target specification), specified in query 'GPUUtilization'.
Jul 16 12:07:09 eagle.home.domain gnome-shell[2155829]: error: Execution of nvidia-settings -q GPUUtilization -q [GPU]/GPUCoreTemp -q UsedDedicatedGPUMemory -q TotalDedicatedGPUMemory -q GPUCurrentFanSpeed -t failed:: ERROR: Error resolving target specification '' (No targets match target specification), specified in query 'GPUUtilization'.

I am using the nvidia drivers from rpmfusion, keep my system fully updated, and don’t remember exactly when these errors began. Possibly as far back as my upgrade to fedora 36, but not certain.

Just in case it matters here is the output from inxi

$ inxi -Fzx
System:
  Kernel: 5.18.9-200.fc36.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.37-27.fc36 Desktop: GNOME v: 42.3.1
    Distro: Fedora release 36 (Thirty Six)
Machine:
  Type: Desktop Mobo: ASRock model: B550M Pro4 serial: <superuser required>
    UEFI: American Megatrends v: L1.42 date: 11/06/2020
Battery:
  Device-1: hidpp_battery_76 model: Logitech MX Ergo Multi-Device Trackball
    charge: 55% (should be ignored) status: discharging
  Device-2: hidpp_battery_77 model: Logitech K350
    charge: 70% (should be ignored) status: discharging
CPU:
  Info: 6-core model: AMD Ryzen 5 3600 bits: 64 type: MT MCP arch: Zen 2
    rev: 0 cache: L1: 384 KiB L2: 3 MiB L3: 32 MiB
  Speed (MHz): avg: 2336 high: 3607 min/max: 2200/4208 boost: enabled
    cores: 1: 2165 2: 2338 3: 2096 4: 2196 5: 2822 6: 2052 7: 2104 8: 3607
    9: 2072 10: 2194 11: 2196 12: 2196 bogomips: 86238
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: NVIDIA GP107 [GeForce GTX 1050] vendor: Gigabyte driver: nvidia
    v: 515.57 arch: Pascal bus-ID: 08:00.0
  Display: wayland server: X.Org v: 1.22.1.2 with: Xwayland v: 22.1.3
    compositor: gnome-shell driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia,nvidia-nvswitch
    resolution: 1920x1080~60Hz
  OpenGL: renderer: NVIDIA GeForce GTX 1050/PCIe/SSE2
    v: 4.6.0 NVIDIA 515.57 direct render: Yes
Audio:
  Device-1: NVIDIA GP107GL High Definition Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel bus-ID: 08:00.1
  Device-2: AMD Starship/Matisse HD Audio vendor: ASRock
    driver: snd_hda_intel v: kernel bus-ID: 0a:00.4
  Sound Server-1: ALSA v: k5.18.9-200.fc36.x86_64 running: yes
  Sound Server-2: PulseAudio v: 15.0 running: no
  Sound Server-3: PipeWire v: 0.3.55 running: yes
Network:
  Device-1: Qualcomm Atheros AR93xx Wireless Network Adapter driver: ath9k
    v: kernel bus-ID: 04:00.0
  IF: wlp4s0 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASRock driver: r8169 v: kernel port: f000 bus-ID: 06:00.0
  IF: enp6s0 state: down mac: <filter>
  IF-ID-1: virbr0 state: down mac: <filter>
RAID:
  Device-1: md127 type: mdraid level: raid-6 status: active size: 5.37 TiB
  Info: report: 4/4 UUUU blocks: 5766400000 chunk-size: 512k
  Components: Online: 1: sde 3: sdd 4: sdb 5: sdc
Drives:
  Local Storage: total: raw: 11.13 TiB usable: 5.59 TiB
    used: 4.77 TiB (85.4%)
  ID-1: /dev/sda vendor: SanDisk model: SSD PLUS 240GB size: 223.58 GiB
    temp: 36 C
  ID-2: /dev/sdb vendor: Western Digital model: WD30EZRZ-00Z5HB0
    size: 2.73 TiB temp: 32 C
  ID-3: /dev/sdc vendor: Western Digital model: WD30EZRZ-00GXCB0
    size: 2.73 TiB temp: 35 C
  ID-4: /dev/sdd vendor: Western Digital model: WD30EZRZ-00GXCB0
    size: 2.73 TiB temp: 37 C
  ID-5: /dev/sde vendor: Western Digital model: WD30EZRZ-00GXCB0
    size: 2.73 TiB temp: 35 C
Partition:
  ID-1: / size: 146.59 GiB used: 108.12 GiB (73.8%) fs: ext4 dev: /dev/dm-0
    mapped: fedora-root
  ID-2: /boot size: 958.2 MiB used: 188.5 MiB (19.7%) fs: ext4
    dev: /dev/sda2
  ID-3: /boot/efi size: 249.7 MiB used: 14.1 MiB (5.6%) fs: vfat
    dev: /dev/sda1
  ID-4: /home size: 5.29 TiB used: 4.66 TiB (88.3%) fs: ext4 dev: /dev/dm-1
    mapped: fedora_raid-home
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 1.48 GiB (18.4%) dev: /dev/zram0
Sensors:
  Message: No sensor data found. Is lm-sensors configured?
Info:
  Processes: 397 Uptime: 10d 1h 23m Memory: 31.17 GiB used: 8.14 GiB (26.1%)
  Init: systemd target: graphical (5) Compilers: gcc: 12.1.1 clang: 14.0.0
  Packages: 21 note: see --pkg Shell: Bash v: 5.1.16 inxi: 3.3.19

I also have secure boot enabled and the modules signed with the key created with kmodkeygenca and used mokutil to load the key to bios. akmod-nvidia is used to build the driver so it is signed properly. The system boots with no secure boot related errors that I can see.

I have tried different kernels, checking the nvidia drivers and packages, used lsof to try and find what is triggering this every 5 seconds, all to no avail. I do normally have gkrellm running but even stopping it makes no difference in what is logged.

Any suggestions?

1 Like
2

Are you sure the errors didn’t start after the update from the 5.10 drivers to the 5.15 .It kind of looks like nvidia-settings isn’t refreshing.I have the latest driver 5.15.57 and haven’t noticed any issues.Just a thought but maybe the latest driver didn’t install like it should have.

3

As stated I don’t know when it actually started. The errors are definitely related to gnome-shell and nvidia-settings though.

I will uninstall the drivers, reboot, then reinstall and reboot again just in case your idea is correct.

4

No change with a complete removal of all nvidia related packages, reboot, reinstall of nvidia, then another reboot.

Jul 16 14:12:46 eagle.home.domain gnome-shell[2889]: error: Execution of nvidia-settings -q GPUUtilization -q [GPU]/GPUCoreTemp -q UsedDedicatedGPUMemory -q TotalDedicatedGPUMemory -q GPUCurrentFanSpeed -t failed:: ERROR: Error resolving target specification '' (No targets match target specification), specified in query 'GPUUtilization'.
Jul 16 14:12:51 eagle.home.domain gnome-shell[2889]: error: Execution of nvidia-settings -q GPUUtilization -q [GPU]/GPUCoreTemp -q UsedDedicatedGPUMemory -q TotalDedicatedGPUMemory -q GPUCurrentFanSpeed -t failed:: ERROR: Error resolving target specification '' (No targets match target specification), specified in query 'GPUUtilization'.
Jul 16 14:12:56 eagle.home.domain gnome-shell[2889]: error: Execution of nvidia-settings -q GPUUtilization -q [GPU]/GPUCoreTemp -q UsedDedicatedGPUMemory -q TotalDedicatedGPUMemory -q GPUCurrentFanSpeed -t failed:: ERROR: Error resolving target specification '' (No targets match target specification), specified in query 'GPUUtilization'.
Jul 16 14:13:01 eagle.home.domain gnome-shell[2889]: error: Execution of nvidia-settings -q GPUUtilization -q [GPU]/GPUCoreTemp -q UsedDedicatedGPUMemory -q TotalDedicatedGPUMemory -q GPUCurrentFanSpeed -t failed:: ERROR: Error resolving target specification '' (No targets match target specification), specified in query 'GPUUtilization'.
Jul 16 14:13:06 eagle.home.domain gnome-shell[2889]: error: Execution of nvidia-settings -q GPUUtilization -q [GPU]/GPUCoreTemp -q UsedDedicatedGPUMemory -q TotalDedicatedGPUMemory -q GPUCurrentFanSpeed -t failed:: ERROR: Error resolving target specification '' (No targets match target specification), specified in query 'GPUUtilization'.

I know that this error was not there when running fedora 34, and I did a direct upgrade to fedora 36. At some time after that upgrade the errors started.

When I manually do the nvidia-settings -q GPUUtilization portion of that command it also gives the same error, but if I run the same command but eliminate the ‘-q GPUUtilization’ part of the command it completes properly from the command line.

I guess that may be a bug in whatever is calling that command, and/or in nvidia-settings itself with the change that no longer allows that query. I have no clue what is making the call to nvidia-settings every 5 seconds, so am stuck in trying to track it further.

Since nvidia-settings is installed from rpmfusion I would like to file a bug report but cannot since rpmfusion does not allow any users to file a bug from a gmail email address. Cannot even set up an account there.

5

I found the issue, and this is a :scream: moment.

On this machine I have been running wayland, which I had forgotten.
I just switched to xorg and the errors are gone, so :exploding_head:

As soon as I realized that I often ask others to check for differences between wayland and xorg but had not done so on my own machine I slapped myself and checked that. Apparently the errors started when I switched to wayland and I did not recognize the timing.

This is definitely a bug in nvidia-settings but related directly to wayland.

1 Like