Bug 1286741
Summary: | powertop unknown op '{' | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Ricardson Williams <ricardsonwilliams> |
Component: | powertop | Assignee: | Jaroslav Škarvada <jskarvad> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 23 | CC: | jskarvad |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-02-15 19:02:49 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ricardson Williams
2015-11-30 16:09:15 UTC
Is it virtual machine? Could you provide some information about the machine (architecture, CPU)? I am able to reproduce the problem under VirtualBox. I'm running on my laptop, my configuration: Processor: intel® Core™ i7-5500U CPU @ 2.40GHz × 4 OS Type: 64bit This is probably because PowerTOP is doing bad assumption about available MSRs. I fixed similar problem a while ago, but it seems upstream reintroduced the bug in the new release. I will take a look. I am no longer able to reproduce the problem under VirtualBox (I tried different versions, 4/5). Unfortunately I don't have i7-5500U (only i7-4600U which works OK), I am trying different machines from our pool, but so far I haven't been able to reproduce the problem. So far the most similar behaviour that I was able to reproduce: unknown op '{'Package(s) Model-specific registers (MSR) not found (try enabling CONFIG_X86_MSR). Total size: 555 k read_msr cpu0 0xe8 : Argument list too long When I run it on experimental machine without MSR. Well, the error is quite strange, the upstream could really put some "love" into it, but it is self descriptive - there is no MSR - and different from yours. Could I kindly ask you to report your problem to PowerTOP upstream? Hopefully the community or Intel will have the machine to reproduce the problem on. I was unsuccessful to find such machine in our pool. I looked again on your report. There is 'code=exited, status=0/SUCCESS'. It is one shot service, so it exited successfully. The "unknown op '{'" is harmless message. I will check it's origin. There is also 'Leaving PowerTOP' message in your report. I think your machine is correctly tuned. So I cannot see any functional problem and the problem description provided in comment 0 is not correct, there is just some weird output on STDERR. |