-
Notifications
You must be signed in to change notification settings - Fork 279
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
nvtop: hiding one GPU aborts with "We should not be processing a client id twice per update" #222
Comments
I have the same problem, but with an RTX2070S (that I want to watch) and a CPU-builtin AMD Radeon (which I don't care about). nvtop v3.0.2 as shipped by Debian. |
Same issue here with a RTX3060 in UBUNTU 23.04 (nvtop used to work, but now I get this error) |
Same problem here
Occurs only in nvidia mode, on-demand is working fine.
|
Hello guys, I'll come up with a patch to avoid needless fdinfo parsing/walk-through for hidden GPUs. |
Can you guys please try with the patch in #247 to see if my reasoning was right? |
Sadly, it doesn't work, message remains and then chrash. |
And now, on my intel Device it does not work anymore, similar message. |
|
Grr, little blind, had installed the wrong package, i build. |
So, applied both MR and it is working on both of my systems. AMD+Nvidia ==> Ok |
Thanks @jackyyf Merging both automatically closed the issue. If anything persists feel free to re-open. |
Hi @Syllo, sorry to trouble you, but could we have a new release for this? (and other patches maybe?) At least for Debian they only catch up with version bump release :) |
Forwarding https://bugs.debian.org/1040892, nvtop/3.0.1-1.
I have a multi-GPU system:
and am presently using both, but debian nvtop isn't compiled with i915 support(? is it just not supported at all?), and I don't really care what happens there, and thus I've disabled the "Xeon" one in Setup, GPU Select>; this caused the following on the next update (and on every subsequent restart with the same config)
config at https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=1040892;filename=interface.ini;msg=5
Watching both GPUs does work.
The text was updated successfully, but these errors were encountered: