Bug#1031804: nvtop: Crashes on multi-gpu system

[Jesse Rhodes]

Package: nvtop
Version: 3.0.1-1
Severity: important
X-Debbugs-Cc: je...@sney.ca

Dear Maintainer,

This system has an integrated AMD GPU (Ryzen 7 7700X/"Raphael") and a discrete nVidia GPU (Geforce GTX 1660 Super), configured for PRIME offloading, with the proprietary nvidia driver, and monitors connected to the integrated.

I tried to run nvtop to verify that the Geforce was being used for a jitsi video conference, and it immediately crashed with the following output:

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.
Aborted (core dumped)

I also got a backtrace (attached).

The message "processing a client id twice" indicates maybe it's not expecting to see statistics from two separate video devices? Though the man page at least implies it should support that.

Including the PRIME environment variables '__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia' when running nvtop makes no difference.

This is not an Optimus laptop but rather a desktop that I'm using the same way. I would be interested to know if actual Optimus devices have the same issue, and if not, what the difference is.

Please let me know if you need any more information, and thanks for your work!

sney

-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'testing-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-3-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages nvtop depends on:
ii libc6 2.36-8
ii libncursesw6 6.4-2
ii libsystemd0 252.5-2
ii libtinfo6 6.4-2

nvtop recommends no packages.

nvtop suggests no packages.

-- no debconf information

[Jesse Rhodes]

I took a second look this morning now that the meeting is over, and
I've determined that it only crashes if chromium or google-chrome is
being run with the PRIME environment variables.

nvidia-smi output as well as temp sensor data indicated that the
nvidia gpu was being used for chrome as I had hoped, but something
about this prevents nvtop from working.

chrome prints the following to the console after being launched with
the aforementioned env vars:

MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to open amdgpu: /usr/lib/dri/amdgpu_dri.so: cannot
open shared object file: Permission denied (search paths
/usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix
_dri)
failed to load driver: amdgpu
MESA-LOADER: failed to open zink: /usr/lib/dri/zink_dri.so: cannot
open shared object file: Permission denied (search paths
/usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix
_dri)
failed to load driver: zink
MESA-LOADER: failed to open kms_swrast:
/usr/lib/dri/kms_swrast_dri.so: cannot open shared object file:
Permission denied (search paths
/usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix
_dri)
failed to load driver: kms_swrast
MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: cannot
open shared object file: Permission denied (search paths
/usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix
_dri)
failed to load swrast driver

But otherwise works as expected.

sney