Milos Tijanic

> While it seems like it's considered acceptable by nvidia in this case, I'm curious if someone can explain to me why the bug reports for release candidates are not...

As an out of tree driver we adapt our release (and thus QA) schedule not just to linux mainline, but also HW releases, security rollouts across multiple LTS driver branches,...

Hey there. Thanks for the report, but unfortunately there's not a whole lot to go on there without the logs. Was `nvidia-bug-report.sh` unable to run and collect the logs, or...

Hi, thanks for the report! From the attached logs, I see: ``` NVRM: Open nvidia.ko is only ready for use on Data Center GPUs. NVRM: To force use of Open...

Thanks! This is tracked internally as nvbug 4729070. Looks like the fix missed the 565.xx train so it should be in 570.xx.

You can trivially hide the message by setting [RmMsg](https://github.com/NVIDIA/open-gpu-kernel-modules/discussions/197) to `!event_notification.c:289`. Or just compiling it out like: ```diff diff --git a/src/nvidia/src/kernel/rmapi/event_notification.c b/src/nvidia/src/kernel/rmapi/event_notification.c index cf78eadd..d6937cac 100644 --- a/src/nvidia/src/kernel/rmapi/event_notification.c +++ b/src/nvidia/src/kernel/rmapi/event_notification.c @@...

Hey there. Could you try with this change applied? https://github.com/NVIDIA/open-gpu-kernel-modules/commit/7cc00d318f788b7cf186dd4b9e0a886cf0baf82c Similar thing will show up in one of the future release branches. Not sure which though.

The patch should apply cleanly to all branches, even the proprietary closed source driver, so no need to use the latest version. I'll leave the bug open until the changes...

Change has landed in 590.44.01, closing. https://github.com/NVIDIA/open-gpu-kernel-modules/blob/590.44.01/kernel-open/common/inc/nv-lock.h

Tracked as nvbug 5651624. Also, #959 is a possible duplicate.