"unknown op" error on running powertop --auto-tune

Bug #1588747 reported by Christopher Barrington-Leigh
36
This bug affects 8 people
Affects Status Importance Assigned to Milestone
powertop
New
Undecided
auto-powertop
powertop (ALT Linux)
Unknown
Unknown
powertop (Ubuntu)
Confirmed
Low
Unassigned
powertop (openSUSE)
Fix Released
Medium

Bug Description

powertop reports an unknown op error. I cannot claim that it's not functioning normally, otherwise. Running it looks like this:

$ sudo powertop --auto-tune
Loaded 750 prior measurements
RAPL device for cpu 0
RAPL Using PowerCap Sysfs : Domain Mask f
RAPL device for cpu 0
RAPL Using PowerCap Sysfs : Domain Mask f
RAPL device for cpu 0
RAPL Using PowerCap Sysfs : Domain Mask f
Devfreq not enabled
  unknown op '{'
Leaving PowerTOP

I don't see the error without --auto-tune.
This seems distinct from https://bugs.launchpad.net/ubuntu/+source/powertop/+bug/1541837

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: powertop 2.8-1build1
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Jun 3 06:15:11 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-02-12 (111 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: powertop
UpgradeStatus: Upgraded to xenial on 2016-05-24 (9 days ago)

Revision history for this message
In , Gp-v (gp-v) wrote :

On current Factory, powertop --auto-tune issues a warning:

powertop --auto-tune
Loaded 7 prior measurements
RAPL device for cpu 0
RAPL device for cpu 0
RAPL device for cpu 0
Devfreq not enabled
  unknown op '{' <=================================

This is with powertop-2.7-1.1.x86_64 and kernel-default-3.17.4-1.2.x86_64.

Revision history for this message
In , Sywang (sywang) wrote :

This issue can also be reproduced by installing powertop-2.7-1.1.x86_64.rpm manually in openSUSE13.2.

Hi Marcus,

Seems the bugowner "<email address hidden>" who is not available anymore, would you please take a look at this issue? Or reassign it to the right person,Thanks!

Revision history for this message
In , Tiwai-r (tiwai-r) wrote :

This is a known bug of powertop itself, see the kown bug section:
   https://01.org/powertop/downloads/powertop-v2.7-0

"Know Bugs:

We plan to fix these bugs in future releases.

* Problem with traceevent lib it prints string: unknown op '{'. This bug doesn’t impact the correct functionality of PowerTOP."

Revision history for this message
Christopher Barrington-Leigh (cpbl) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in powertop (Ubuntu):
status: New → Confirmed
Changed in powertop (Ubuntu):
importance: Undecided → Low
Revision history for this message
Ivan Zakharyaschev (imz) wrote :

Its discussion -- https://lists.01.org/pipermail/powertop/2016-April/001880.html :

From: Joe Konno joe.konno at linux.intel.com

Nope, you didn't miss anything. That's a bug. If you feel so inclined,
feel free to file a bug on our bugzilla (doesn't have to be elaborate).

https://app.devzing.com/powertopbugs/bugzilla/

On Wed, Mar 30, 2016 at 04:04:40AM +0100, Ciprian Tomoiaga wrote:

> When running powertop --configure for the first time, I saw this error on
> the output:
> Calibrating idle
> System is not available
> unknown op '{'
> System is not available
> Calibrating: disk usage
>
> The configuration continued though until completion.
> Did I miss anything?

https://bugzilla.suse.com/show_bug.cgi?id=911626#c2 :

This is a known bug of powertop itself, see the kown bug section:
   https://01.org/powertop/downloads/powertop-v2.7-0

"Know Bugs:

We plan to fix these bugs in future releases.

* Problem with traceevent lib it prints string: unknown op '{'. This bug doesn’t impact the correct functionality of PowerTOP."

Changed in powertop (openSUSE):
importance: Unknown → Medium
status: Unknown → Confirmed
Revision history for this message
Gábor Lipták (gliptak) wrote :

Corrected in Artful

➜ cat /etc/*release* | grep RELEASE
DISTRIB_RELEASE=17.10
~
➜ sudo powertop --auto-tune
modprobe cpufreq_stats failedLoaded 281 prior measurements
RAPL device for cpu 0
RAPL Using PowerCap Sysfs : Domain Mask f
RAPL device for cpu 0
RAPL Using PowerCap Sysfs : Domain Mask f
Devfreq not enabled
after count is 0 gpu c0
after count is 0 gpu rc6
after count is 0 gpu rc6p
after count is 0 gpu rc6pp
after count is 0 gpu c0
after count is 0 gpu rc6
after count is 0 gpu rc6p
after count is 0 gpu rc6pp
Leaving PowerTOP

Revision history for this message
In , Dominique Leuenberger aka DimStar (dimstar) wrote :

(In reply to Takashi Iwai from comment #2)
> This is a known bug of powertop itself, see the kown bug section:
> https://01.org/powertop/downloads/powertop-v2.7-0
>
> "Know Bugs:
>
> We plan to fix these bugs in future releases.
>
> * Problem with traceevent lib it prints string: unknown op '{'. This bug
> doesn’t impact the correct functionality of PowerTOP."

As far as I can find, this was fixed in powertop version 2.8 - released back in Nov 2015

Revision history for this message
In , Gp-v (gp-v) wrote :

Verified with powertop-2.12-1.1.x86_64 on current Tumbleweed.

Changed in powertop (openSUSE):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.