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.
Bug 1283648 - Update cpupowerutils to upstream
Summary: Update cpupowerutils to upstream
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: cpupowerutils
Version: 6.8
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jacob Tanenbaum
QA Contact: Erik Hamera
URL:
Whiteboard:
Depends On: 1298255
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-19 14:02 UTC by Jacob Tanenbaum
Modified: 2017-06-14 14:49 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1298255 (view as bug list)
Environment:
Last Closed: 2016-05-10 20:29:13 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0785 0 normal SHIPPED_LIVE cpupowerutils bug fix update 2016-05-10 22:36:22 UTC

Description Jacob Tanenbaum 2015-11-19 14:02:40 UTC 
Update cpupowerutils package to reflect most current upstream code
Comment 2 Erik Hamera 2016-03-04 04:23:33 UTC 
There is cpupower 2.6.32 from package cpupowerutils-1.3-1.el6.x86_64 in 6.8.

Is that updated enough? 

There is kernel 2.6.32-621.el6.x86_64, so yes I think.

On the other hand the newest code is cpupowerutils from kernel 4.2 obviously.
Comment 6 Erik Hamera 2016-03-10 16:32:41 UTC 
The question is - from my point of view - if we want to mix old kernel and new cpupowerutils. 

If it will work together, we can say, that the newer is better (less bugs and more features). But is proper functionality guaranteed/wanted from upstream?
If not, I'm inclining to use the same version like version of kernel is.
Comment 7 Erik Hamera 2016-03-24 03:07:39 UTC 
Hi jtaneba,
is possible to use the newer cpupowerutils than kernel, or is right when versions of cpupowerutils and kernel are the same?
Comment 8 Erik Hamera 2016-04-07 01:39:55 UTC 
No reply to my question in c7.

It seems, that the code in ftp://porkchop.devel.redhat.com/mnt/redhat/released/RHEL-6/6.8-Beta/Server/source/SRPMS/cpupowerutils-1.3-1.el6.src.rpm is the same as the code in https://www.kernel.org/pub/linux/utils/kernel/cpufreq/cpufrequtils-008.tar.xz .

Diff is pretty big (over 6k lines), but it changes formatting of code, content of printf()s and things like that mostly (no, I haven't read it character by character).

The newest file in upstream is from 7 Jun 2015 and last update in srpm's spec file is from 19 Jan 2016. 

Based on data available to me I think we have most current upstream code. If anyone think I'm wrong, prove it please and put this bug back to QE.
Comment 10 errata-xmlrpc 2016-05-10 20:29:13 UTC 
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, 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://rhn.redhat.com/errata/RHBA-2016-0785.html
Note You need to log in before you can comment on or make changes to this bug.