-
Notifications
You must be signed in to change notification settings - Fork 26
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
nvidia: Patching of 565.57.01 for Linux kernel 6.12 #417
Comments
Unsurprisingly, my hack of a rebase has caused issues on some systems. Thankfully, NVIDIA has reached out to us with their own patch that should fix things for 6.12 kernels without causing any issues. I have also taken the chance to sync the patch file names with the ones in our tree for coherency and consistency with the patch numbering. Closes #417 Suggested-by: Rahul Rameshbabu <[email protected]> Signed-off-by: Eric Naim <[email protected]>
Acknowledged! Thank you so much for reaching out to us with this. I have created a PR that will use this patch instead of the hacky fix. I have also gotten a few users to test this patch and it seems to work as intended. Once @ptr1337 is available, the PR should get merged and it will be in our repos. I will also sync the patches used in our kernel modules soon. |
Addresses CachyOS/CachyOS-PKGBUILDS#417 and syncs with CachyOS/CachyOS-PKGBUILDS#418. Signed-off-by: Eric Naim <[email protected]>
Addresses CachyOS/CachyOS-PKGBUILDS#417 and syncs with CachyOS/CachyOS-PKGBUILDS#418. Signed-off-by: Eric Naim <[email protected]>
Addresses CachyOS/CachyOS-PKGBUILDS#417 and syncs with CachyOS/CachyOS-PKGBUILDS#418. Signed-off-by: Eric Naim <[email protected]>
Thanks for reaching us out! I will send this also to the rpmfusion maintainers and push it into the archlinux repository. |
Hi,
Commit 6c22aadbf6fd ("drm/fbdev-helper: Remove
drm_fb_helper_output_poll_changed()") in the linux kernel removed support for
the .output_poll_changed interface in drm_mode_config_funcs. This callback was
used to handle hotplug events in place of the hotplug interface provided through
fbdev emulation. We verify if this callback is present in the kernel
installation the driver is being built against and omit it if not present.
If this callback is not present, it is safe to assume that filling modes for the
connectors has become the responsibility of the core DRM stack. No replacement
callback needs to be defined for hotplug support to continue working as it
currently does on released kernel trees. The assumption about the core stack
populating the modes capable per connector is based around
drm_fb_helper_hotplug_event which is called thanks to the following.
Because of this, calling drm_client_register and keeping
nv_drm_output_poll_changed is unnecessary for kernel 6.12 since the core stack
handles hotplug events on our behalf through the DRM fbdev API. We noticed users
reporting issues on the NVIDIA forum with regards to this.
https://forums.developer.nvidia.com/t/getting-kernel-null-pointer-dereference-when-unloading-modprobe-r-nvidia-drm/312331
We see users reporting the patched logic hitting the "Failed to
initialize the nv-hotplug-helper DRM client" failure case based on their
dmesg logs. We believe that what then happens is that we failed to init
the drm device (entered a failure path) but the device pointer is on our
list in nv_drm_remove_devices which leads to the kernel panic seen by
the user.
We believe you can safely reduce your patch to what we have shared on
our forum regarding our current 565 driver release and kernel 6.12
compatibility. Our next 565 driver release will patch this as well, but
it unfortunately will likely be release a couple weeks after Linux
kernel 6.12 is tagged.
Thanks,
Rahul Rameshbabu
The text was updated successfully, but these errors were encountered: