parse_drm_fdinfo_amd: Assertion `!cache_entry_check && "We should not be processing a client id twice per update"' failed

[anshanlove]

AMD Ryzen™ 9 7950X +NVIDIA GeForce RTX™ 4090,
Ubuntu 24.04.1 LTS,
3.0.2
nvtop: ./src/extract_gpuinfo_amdgpu.c:964: parse_drm_fdinfo_amd: Assertion `!cache_entry_check && "We should not be processing a client id twice per update"' failed.

[martin-tag24]

same here 💡

AMD Ryzen 7 7700X
NVIDIA GeForce RTX 4090
Ubuntu 24.04.1 LTS

nvtop: ./src/extract_gpuinfo_amdgpu.c:964: parse_drm_fdinfo_amd: Assertion `!cache_entry_check && "We should not be processing a client id twice per update"' failed.

# nvtop --version
nvtop version 3.0.2

[inflatebot]

Also occurring on Debian 12 Bookworm with nvtop 3.0.1.
RTX 4090, Ryzen 9 7950X

nvtop: ./src/extract_gpuinfo_amdgpu.c:946: parse_drm_fdinfo_amd: Assertion `!cache_entry_check && "We should not be processing a client id twice per update"' failed.
[1] 1187319 IOT instruction  nvtop

nvtop --version
nvtop version 3.0.1

I would like to try telling nvtop not to attempt to read the integrated AMD GPU as a potential workaround, but I don't see a way to do this without a config file to edit, but nvtop is unable to make one because of this issue.

[inflatebot]

Notably, the AppImage does work.
It might be that it's version 3.1.0, whereas Debian packages 3.0.1, which is a couple versions out of date. I might try installing 3.1.0 by a manual process.

[Syllo]

There was a bug in version prior to 3.1.0 fixed by this patch where the hash table lookup was not done properly on the full key and would lead to this assertion triggering.

[Syllo]

You can either update if your distribution has a more recent version or use the AppImage available here: https://github.com/Syllo/nvtop/releases/tag/3.1.0

[ArgentVASIMR]

@Syllo Hi, I've experienced the same problem as anshanlove did- how would I go about installing/upgrading it in such a way that I can run it as nvtop in the console instead of as an appimage? Keep in mind that I'm relatively new to Linux Mint, just got into it a few days ago.

[divmgl]

Unfortunately this is happening to me on 3.1.0 on Ubuntu:

❯ inxi -b
System:
  Host: dimgl-server Kernel: 6.11.0-19-generic arch: x86_64 bits: 64
  Desktop: GNOME v: 46.0 Distro: Ubuntu 24.04.2 LTS (Noble Numbat)
Machine:
  Type: Desktop Mobo: Micro-Star model: MPG Z690 CARBON WIFI (MS-7D30) v: 1.0
    serial: <superuser required> UEFI: American Megatrends LLC. v: 1.00
    date: 09/23/2021
CPU:
  Info: 16-core (8-mt/8-st) 12th Gen Intel Core i9-12900K [MST AMCP]
    speed (MHz): avg: 2819
Graphics:
  Device-1: Intel AlderLake-S GT1 driver: i915 v: kernel
  Device-2: NVIDIA AD102 [GeForce RTX 4090] driver: nvidia v: 550.120
  Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6 driver: X:
    loaded: modesetting,nouveau unloaded: fbdev,vesa failed: nvidia dri: iris
    gpu: nvidia,nvidia-nvswitch resolution: 1: 3840x2160~60Hz
    2: 3840x2160~60Hz
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.120
    renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
Network:
  Device-1: Intel Ethernet I225-V driver: igc
  Device-2: Intel Wi-Fi 6E AX210/AX1675 2x2 [Typhoon Peak] driver: iwlwifi
Drives:
  Local Storage: total: 4.55 TiB used: 1.34 TiB (29.4%)
Info:
  Memory: total: 64 GiB note: est. available: 62.59 GiB used: 9.74 GiB (15.6%)
  Processes: 535 Uptime: 1h 18m Shell: fish inxi: 3.3.34

❯ /home/dimgl/Downloads/nvtop-x86_64.AppImage --version
nvtop version 3.1.0

[jcgit1]

This is also happening on the latest stable release of KDE Neon (6.3) . However, as previously recommended, the AppImage does work.

AMD 7800x3d
Asus TUF Nvidia RTX 4090
Kde Neon 6.3

NVIDIA-SMI 565.57.01 Driver Version: 565.57.01 CUDA Version: 12.7

nvtop: ./src/extract_gpuinfo_amdgpu.c:964: parse_drm_fdinfo_amd: Assertion `!cache_entry_check && "We should not be processing a client id twice per update"' failed.
Aborted (core dumped)

$ nvtop --version
nvtop version 3.0.2

[inflatebot]

At this point I think we all know the cause

Unfortunately this is happening to me on 3.1.0 on Ubuntu:

❯ inxi -b
System:
  Host: dimgl-server Kernel: 6.11.0-19-generic arch: x86_64 bits: 64
  Desktop: GNOME v: 46.0 Distro: Ubuntu 24.04.2 LTS (Noble Numbat)
Machine:
  Type: Desktop Mobo: Micro-Star model: MPG Z690 CARBON WIFI (MS-7D30) v: 1.0
    serial: <superuser required> UEFI: American Megatrends LLC. v: 1.00
    date: 09/23/2021
CPU:
  Info: 16-core (8-mt/8-st) 12th Gen Intel Core i9-12900K [MST AMCP]
    speed (MHz): avg: 2819
Graphics:
  Device-1: Intel AlderLake-S GT1 driver: i915 v: kernel
  Device-2: NVIDIA AD102 [GeForce RTX 4090] driver: nvidia v: 550.120
  Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6 driver: X:
    loaded: modesetting,nouveau unloaded: fbdev,vesa failed: nvidia dri: iris
    gpu: nvidia,nvidia-nvswitch resolution: 1: 3840x2160~60Hz
    2: 3840x2160~60Hz
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.120
    renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
Network:
  Device-1: Intel Ethernet I225-V driver: igc
  Device-2: Intel Wi-Fi 6E AX210/AX1675 2x2 [Typhoon Peak] driver: iwlwifi
Drives:
  Local Storage: total: 4.55 TiB used: 1.34 TiB (29.4%)
Info:
  Memory: total: 64 GiB note: est. available: 62.59 GiB used: 9.74 GiB (15.6%)
  Processes: 535 Uptime: 1h 18m Shell: fish inxi: 3.3.34

❯ /home/dimgl/Downloads/nvtop-x86_64.AppImage --version
nvtop version 3.1.0

It looks like there might be an issue with the Nvidia driver stack:

Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6 driver: X:
loaded: modesetting,nouveau unloaded: fbdev,vesa failed: nvidia dri: iris

I'm not sure why this would be causing this issue, but it's something you might want to look at.

[brandontylke]

On Ubuntu 24.04, after cloning the repo and building locally, I was able to work around this.

Specifically this build process from the README.

  sudo docker build --tag nvtop .
  sudo docker run -it --rm --runtime=nvidia --gpus=all --pid=host nvtop