Bug 428204
Summary: | cpuspeed status reports 'cpuspeed dead but subsys locked' | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Geoff Gustafson <grgustaf> |
Component: | kernel-utils | Assignee: | Jarod Wilson <jarod> |
Status: | CLOSED CANTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 4.6 | CC: | jane.lv, jvillalo, youquan.song |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-04-15 21:07:45 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: |
Description
Geoff Gustafson
2008-01-09 21:56:31 UTC
Just reproduced the same issue on a radically different mobile Montevina SDV. So I think this is probably a fairly generic problem with RHEL4.6. Hrm, been unable to reproduce this as of yet, but then I've only tried on two systems, and one of them doesn't support freq scaling at all (which I didn't realize until after installing, of course). If you can reproduce this again, can you grab me /var/log/messages and dmesg output? Oh, hrm, just noticed that I was doing 4.7 installs too, not 4.6... I don't think cpuspeed in the 4.7 trees has changed yet though. Could be kernel-related too though. Ugh. Will try again with 4.6 myself too. Just installed 4.6 on a box, but apparently, not even the newest rhel4 beta kernel supports freq scaling on this box (it works in rhel5 and fedora). I lose again... I haven't noticed this for a while, I'll try to keep my eyes open the next time I do a 4.6/4.7 install. Maybe John or I can try doing a 4.7 install on the Montevina and perhaps Bensley. Geoff and/or John, have either of you been able to reproduce this problem w/4.7? Since we've apparently not been able to hit this in over a year, I'm going to just go ahead and close it out. |