Bug 738463
| Summary: | cpuspeed init script still tries to adjust cpufreq sysfiles on a per core basis | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Travis Gummels <tgummels> | ||||||
| Component: | cpuspeed | Assignee: | Petr Šabata <psabata> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | John Brier <jbrier> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 6.1 | CC: | ddumas, emcnabb, ovasik | ||||||
| Target Milestone: | rc | Keywords: | Patch | ||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | cpuspeed-1.5-18.el6 | Doc Type: | Bug Fix | ||||||
| Doc Text: |
Cause: The cpuspeed init script still tries to adjust cpufreq sysfiles on a per core basis eventhough the cpufreq drivers complain that this is a deprecated procedure.
Consequence: The log files are full of warnings.
Fix: Tresholds are set globally, instead of deprecated per unit setting.
Result: No warnings in dmesg. Tresholds are set globally on all cpus.
|
Story Points: | --- | ||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2012-10-25 13:11:09 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 767187, 836169 | ||||||||
| Attachments: |
|
||||||||
|
Description
Travis Gummels
2011-09-14 21:04:02 UTC
Created attachment 523338 [details]
Set thresholds globally instead of per CPU
The attached patch should fix the issue. Requesting acks. Created attachment 524993 [details]
Init file for cpuspeed at customer site.
Original problem reproduced: [root@amd-annapurna-02 ~]# rpm -q cpuspeed cpuspeed-1.5-15.el6.x86_64 [root@amd-annapurna-02 ~]# egrep ^UP /etc/sysconfig/cpuspeed UP_THRESHOLD=30 [root@amd-annapurna-02 ~]# service cpuspeed restart Disabling ondemand cpu frequency scaling: [ OK ] Enabling ondemand cpu frequency scaling: [ OK ] [root@amd-annapurna-02 ~]# dmesg | grep CPUFREQ CPUFREQ: Per core ondemand sysfs interface is deprecated - up_threshold CPUFREQ: Per core ondemand sysfs interface is deprecated - up_threshold [root@amd-annapurna-02 ~]# Latest version of cpuspeed in errata doesn't produce additional CPUFREQ warning/error but it does have the same error the customer reported in comment 7: [root@amd-annapurna-02 ~]# rpm -Uvh cpuspeed-1.5-17.el6.x86_64.rpm Preparing... ########################################### [100%] 1:cpuspeed ########################################### [100%] [root@amd-annapurna-02 ~]# service cpuspeed restart Disabling ondemand cpu frequency scaling: [ OK ] /etc/init.d/cpuspeed: line 86: cpufreq/ondemand/up_threshold: No such file or directory Enabling ondemand cpu frequency scaling: [ OK ] [root@amd-annapurna-02 ~]# dmesg | grep CPUFREQ CPUFREQ: Per core ondemand sysfs interface is deprecated - up_threshold CPUFREQ: Per core ondemand sysfs interface is deprecated - up_threshold Is the error from the init script expected? (In reply to comment #23) > Is the error from the init script expected? Petr can you respond to the above comment? (In reply to comment #24) > (In reply to comment #23) > > Is the error from the init script expected? > > Petr can you respond to the above comment? Hmm, I see the changes pushed here come from the original (not working) patch I posted last year. I posted an updated version in Comment 12, however there was no feedback back then and both the test SRPM and the patch are not available anymore. I hope to find it somewhere on my system :) This bug was not fixed in 1.5-17. I'd suggest FailedQA for now. 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. http://rhn.redhat.com/errata/RHBA-2012-1404.html |