Description of problem: Getting the following attempting to install the 2.6.18-62.el5.i686 kernel on top of a 5.1 installation: 2:kernel ########################################### [ 50%] WARNING: /lib/modules/2.6.18-62.el5/kernel/drivers/cpufreq/cpufreq_ondemand.ko needs unknown symbol __udivdi3 WARNING: /lib/modules/2.6.18-62.el5/kernel/drivers/cpufreq/cpufreq_ondemand.ko needs unknown symbol __udivdi3 Version-Release number of selected component (if applicable): 2.6.18-62.el5.i686 How reproducible: Every time
Proposing for 5.2 with a target of the beta.
Created attachment 290778 [details] trivial revert of the offending change in linux-2.6-xen-kernel-cpu-frequency-scaling.patch Changing idle_ticks and total_ticks to 64 bit variables caused the __udivdi3 issue. -static void dbs_check_cpu(struct cpu_dbs_info_s *this_dbs_info) +#ifndef CONFIG_XEN +static int dbs_calc_load(struct cpu_dbs_info_s *this_dbs_info) { - unsigned int idle_ticks, total_ticks; - unsigned int load; - cputime64_t cur_jiffies; - struct cpufreq_policy *policy; + cputime64_t cur_jiffies; + cputime64_t total_ticks, idle_ticks; unsigned int j;
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
Just as an information point, these errors are still occurring with -71.el5 . . . not sure if that's expected or not.
Seeing as the fix was not actually committed (still in POST state), I'd say yes.
in 2.6.18-72.el5 You can download this test kernel from http://people.redhat.com/dzickus/el5
Things are all better with the -72.el5 kernel. Moving to Verified.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2008-0314.html