Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
This is a placeholder bug to handle rebuilds of kmod-kvdo any time a new kernel is available that is no longer kABI compatible with the current version of kmod-kvdo.
A previous example of this bug can be found at BZ2000926.
Steps to Reproduce:
1. Install RHEL-9.1.0
2. Install package versions referenced (kernel and kmod-kvdo)
3. Attempt to run `modprobe uds` or `modprobe kvdo`.
Expected results:
Modules loaded
I think something went wrong with automated tagging from over the weekend. kmod-kvdo-8.1.1.360-31.el9 is what should be used with kernel-5.14.0-101.el9.
Thanks. I am going to do a new build today just in case that just fixes the problem. If not, I'll raise an issue with the infrastructure admins to work out the details.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (kmod-kvdo bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2022:8333
Needs to get reopened. kmod-kvdo-8.2.0.21-47.el9_1.x86_64 does not work with kernel release 5.14.0-162.23.1.el9_1.x86_64
When trying to load it:
modprobe: FATAL: Module kvdo not found in directory /lib/modules/5.14.0-162.23.1.el9_1.x86_64
Symlinking the module to weak-updates of current kernel, running depmod and modprobe after it :
modprobe: ERROR: could not insert 'kvdo': Invalid argument
Syslog contains this:
[ 823.069879] kvdo: disagrees about version of symbol wake_up_process
[ 823.069912] kvdo: Unknown symbol wake_up_process (err -22)