With the recent release of RHEL 7.5, we've been seeing issues where the latest kernel doesn't appear to be compatible with the latest driver build (390.48-1.el7_4) [line breaks added for readability]; the modules weren't carried forward, so I tried to do some debugging:
bash-4.2# weak-modules --add-kernel --verbose 3.10.0-862.el7.x86_64 Module nvidia-drm.ko from kernel 3.10.0-693.21.1.el7.x86_64 is not compatible with kernel 3.10.0-862.el7.x86_64 in symbols: drm_framebuffer_cleanup drm_atomic_helper_plane_destroy_state drm_kms_helper_poll_fini drm_mode_object_find drm_kms_helper_poll_disable drm_connector_register drm_kms_helper_poll_init drm_framebuffer_init drm_modeset_unlock_all drm_mode_probed_add drm_atomic_helper_disable_plane drm_modeset_lock_all drm_atomic_state_default_clear drm_helper_hpd_irq_event drm_mode_config_init drm_crtc_cleanup drm_gem_create_mmap_offset drm_encoder_cleanup drm_connector_unregister drm_atomic_clean_old_fb drm_gem_prime_handle_to_fd drm_atomic_helper_connector_dpms reservation_object_add_excl_fence drm_gem_object_lookup drm_crtc_send_vblank_event drm_gem_private_object_init drm_atomic_helper_commit dma_fence_default_wait drm_atomic_helper_check drm_atomic_helper_connector_destroy_state drm_atomic_helper_plane_duplicate_state drm_mode_create drm_plane_cleanup drm_mode_connector_update_edid_property drm_connector_init dma_fence_signal drm_gem_object_release drm_atomic_state_init drm_gem_dumb_destroy drm_gem_handle_create drm_atomic_helper_plane_reset drm_crtc_init_with_planes drm_atomic_state_default_release drm_helper_mode_fill_fb_struct drm_gem_object_unreference_unlocked dma_fence_init drm_mode_set_name drm_mode_create_dvi_i_properties drm_dev_unregister drm_mode_connector_attach_encoder drm_atomic_helper_set_config __drm_atomic_helper_crtc_duplicate_state drm_atomic_helper_connector_duplicate_state drm_atomic_set_mode_for_crtc drm_connector_cleanup drm_universal_plane_init drm_atomic_helper_crtc_reset __drm_atomic_helper_crtc_destroy_state drm_object_property_set_value drm_encoder_init drm_vblank_init drm_dev_unref drm_kms_helper_hotplug_event drm_helper_probe_single_connector_modes drm_atomic_helper_disable_all drm_atomic_helper_page_flip drm_atomic_helper_commit_hw_done drm_atomic_helper_connector_reset drm_mode_config_cleanup drm_dev_alloc drm_atomic_helper_update_plane drm_dev_register drm_gem_prime_export Module nvidia-uvm.ko from kernel 3.10.0-693.21.1.el7.x86_64 is not compatible with kernel 3.10.0-862.el7.x86_64 in symbols: radix_tree_insert Module nvidia.ko from kernel 3.10.0-693.21.1.el7.x86_64 is not compatible with kernel 3.10.0-862.el7.x86_64 in symbols: efi_enabled screen_info i2c_del_adapter i2c_add_adapter acpi_bus_unregister_driver acpi_bus_get_device acpi_bus_register_driver Module nvidia-modeset.ko from kernel 3.10.0-693.21.1.el7.x86_64 is not compatible with kernel 3.10.0-862.el7.x86_64 in symbols: nv_kthread_q_flush nvidia_register_module nv_kthread_q_schedule_q_item nvidia_get_rm_ops nv_kthread_q_item_init nv_kthread_q_stop nvidia_unregister_module nv_kthread_q_init Has anyone else experience this issue, or am I doing something wrong? I would try rebuilding the driver packages myself, but in the past when I've done that I seem to not be building them correctly, as they only like to work on the kernel I build them on and not subsequent ones (whereas the binaries distributed by this project do typically continue to work). Thanks, --Ray
_______________________________________________ elrepo mailing list elrepo@lists.elrepo.org http://lists.elrepo.org/mailman/listinfo/elrepo
