-
Notifications
You must be signed in to change notification settings - Fork 301
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
Comments
same here 💡 AMD Ryzen 7 7700X
|
Also occurring on Debian 12 Bookworm with nvtop 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. |
Notably, the AppImage does work. |
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. |
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 |
@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 |
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.
The text was updated successfully, but these errors were encountered: