Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
anshanlove opened this issue Oct 13, 2024 · 6 comments

Comments

@anshanlove
Copy link

anshanlove commented Oct 13, 2024

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
Copy link

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
Copy link

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
Copy link

inflatebot commented Oct 25, 2024

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
Copy link
Owner

Syllo commented Nov 3, 2024

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
Copy link
Owner

Syllo commented Nov 3, 2024

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
Copy link

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants