Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: I updated my laptop today to latest kernel after rebooting the laptop i try using powertop then i get this error Version-Release number of selected component: powertop-2.9-9.fc29 Additional info: reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: powertop --auto-tune crash_function: perf_event::process executable: /usr/sbin/powertop journald_cursor: s=6bbfa9a5606843e6951963cbd8a98695;i=1088b;b=7311a581d018477899f5a699a6f85e0d;m=4223010;t=58205c4dbd066;x=16fe86b0f6e3ebaf kernel: 4.20.8-200.fc29.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (4 frames) #0 perf_event::process at perf/perf.cpp:233 #1 perf_bundle::process at perf/perf_bundle.cpp:326 #2 process_cpu_data at cpu/cpu.cpp:1024 #3 one_measurement at main.cpp:254
Created attachment 1535532 [details] File: backtrace
Created attachment 1535533 [details] File: cgroup
Created attachment 1535534 [details] File: core_backtrace
Created attachment 1535535 [details] File: cpuinfo
Created attachment 1535536 [details] File: dso_list
Created attachment 1535537 [details] File: environ
Created attachment 1535538 [details] File: exploitable
Created attachment 1535539 [details] File: limits
Created attachment 1535540 [details] File: maps
Created attachment 1535541 [details] File: mountinfo
Created attachment 1535542 [details] File: open_fds
Created attachment 1535543 [details] File: proc_pid_status
Similar problem has been detected: Noticed that the PowerTOP autotune during bootup was showing as FAILED. When I manually tried running powertop from the command line (no parameters) it also immediately crashed. reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/sbin/powertop --auto-tune crash_function: perf_event::process executable: /usr/sbin/powertop journald_cursor: s=3686470e66ac444cb1d547244d586b9c;i=5e6;b=47e2cd02eb694184b134a58dcdc9aa15;m=20b1d8e;t=5822070717b8e;x=d07411177a172cf3 kernel: 4.20.8-200.fc29.x86_64 package: powertop-2.9-9.fc29 reason: powertop killed by SIGSEGV rootdir: / runlevel: unknown type: CCpp uid: 0
Similar problem has been detected: using powertop command line, I get Segmentation fault reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: powertop --calibrate crash_function: perf_event::process executable: /usr/sbin/powertop journald_cursor: s=86a787da8de342eca79e98ea061cdb3e;i=3bb7;b=b54fe167d73746279b12ab3bc4860541;m=e1c7226;t=5821578701a16;x=1bb7eca6cda00b4a kernel: 4.20.8-200.fc29.x86_64 package: powertop-2.9-9.fc29 reason: powertop killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 0
Similar problem has been detected: I regularly run sudo powertop --auto-tune after a system boot to optimize for when I run on batery power. This may be the first time I've run that since updating to F29 reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: powertop --auto-tune crash_function: perf_event::process executable: /usr/sbin/powertop journald_cursor: s=30195c5db0a44b19a25a070376342697;i=10047a;b=804379820b8a4c1c88600a3ee86ffc04;m=19543509;t=58236c6f8ba9f;x=5664fa307409c6f2 kernel: 4.20.8-200.fc29.x86_64 package: powertop-2.9-9.fc29 reason: powertop killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 0
*** Bug 1678846 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Simply ran "sudo powertop" and it crashed immediately. reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: powertop crash_function: perf_event::process executable: /usr/sbin/powertop journald_cursor: s=a8e2948215424abcbc021965933530f3;i=1d6a86;b=4386bc6bd8aa4efe8343cfd9f99761fa;m=18ffcb542f;t=5824fc33b2e79;x=95253337cc7637cb kernel: 4.20.8-200.fc29.x86_64 package: powertop-2.9-9.fc29 reason: powertop killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 0
Similar problem has been detected: start powertop on kernel 4.20.8 reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/sbin/powertop --auto-tune crash_function: perf_event::process executable: /usr/sbin/powertop journald_cursor: s=0aee45beff554c2d8924d420cd186ab6;i=3aa25e;b=2c027c4cca7e49e190d97b0a3a96deb1;m=b81ed8;t=5822d51343dbf;x=17588bcae3d3fb24 kernel: 4.20.8-200.fc29.x86_64 package: powertop-2.9-9.fc29 reason: powertop killed by SIGSEGV rootdir: / runlevel: unknown type: CCpp uid: 0
Similar problem has been detected: Just ran powertop and it crashed. Kernel version is kernel-4.20.8-200.fc29.x86_64. Prints the following before clearing the screen and segfaulting: $ sudo powertop modprobe cpufreq_stats failedLoaded 168 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 glob returned GLOB_ABORTED reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: powertop crash_function: perf_event::process executable: /usr/sbin/powertop journald_cursor: s=0d4d3b0127d9416f87bb4d07b61debf5;i=158197e;b=569ca3ae7bb84e4d96218b6a8f7bd829;m=12b701c4b8;t=5822f1099da60;x=70036e077d2d9d9c kernel: 4.20.8-200.fc29.x86_64 package: powertop-2.9-9.fc29 reason: powertop killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 0
*** Bug 1679262 has been marked as a duplicate of this bug. ***
Found this bug on other distro too like arch this issue has not even resolved with kernel 4.20.10 i dont know about 4.20.11 https://bbs.archlinux.org/viewtopic.php?id=244225 https://bugs.archlinux.org/task/61767?string=powertop&project=1&type%5B0%5D=&sev%5B0%5D=&pri%5B0%5D=&due%5B0%5D=&reported%5B0%5D=&cat%5B0%5D=&status%5B0%5D=open&percent%5B0%5D=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=&closedto= https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=528871b456026e6127d95b1b2bd8e3a003dc1614
Kernel 4.20.11 has been submitted for testing: F29: https://bodhi.fedoraproject.org/updates/FEDORA-2019-7bdeed7fc5 F28: https://bodhi.fedoraproject.org/updates/FEDORA-2019-16de0047d4
with Kernel 4.20.11 from F29: https://bodhi.fedoraproject.org/updates/FEDORA-2019-7bdeed7fc5 powertop starts without segfault
Confirmed, it's no longer crashing on 4.20.11-200.fc29.x86_64.
*** Bug 1680215 has been marked as a duplicate of this bug. ***
Similar problem has been detected: From kernel 4.20.8 until latest during start powertop or powertop.service sigsev error kill powertop reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/sbin/powertop --auto-tune crash_function: perf_event::process executable: /usr/sbin/powertop journald_cursor: s=74c4a340e6a5437db86ff86e44ca2c7e;i=6995;b=6699b52193594d9280029cc139d28826;m=a5ebd9;t=5823589193d7a;x=dae5fbd188ba6568 kernel: 4.20.8-200.fc29.x86_64 package: powertop-2.9-9.fc29 reason: powertop killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 0
Similar problem has been detected: I closed my laptop lid. reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/sbin/powertop --auto-tune crash_function: perf_event::process executable: /usr/sbin/powertop journald_cursor: s=e4741db81e924e588350b48be3413258;i=10fa83;b=ca76c4de9216436fa06c79d081ebb3a2;m=1275aa3;t=582cb1b1ed949;x=ab354eeb20951de8 kernel: 4.20.10-200.fc29.x86_64 package: powertop-2.9-9.fc29 reason: powertop killed by SIGSEGV rootdir: / runlevel: unknown type: CCpp uid: 0
Similar problem has been detected: Running "sudo powertop" is enough to reproduce this problem. This seems to be a regression for Linux 4.20. I can reproduce this on 4.20.10 and as far as I can tell this didn't happen on 4.19.13 before. reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: powertop --auto crash_function: perf_event::process executable: /usr/sbin/powertop journald_cursor: s=9fb2249477fe4350b69c444ab2188edc;i=56814;b=3c9b4b6957b34bafa8911e800fb22d6d;m=29c4d3b;t=582dc13c35d02;x=86a7e1fe33eeb8b3 kernel: 4.20.10-200.fc29.x86_64 package: powertop-2.9-9.fc29 reason: powertop killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 0
I can confirm that kernel 4.20.11 from https://bodhi.fedoraproject.org/updates/FEDORA-2019-7bdeed7fc5 fixes the problem for me.
Similar problem has been detected: Just started powertop as root user. It crashed imediatelly. reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: powertop crash_function: perf_event::process executable: /usr/sbin/powertop journald_cursor: s=559dd0c523c943ea8d2493f9cd9aad54;i=1fb93;b=9acf4e8067fc44ebbfd99ef1a6272d07;m=10812a9d33;t=582f485cd4f9d;x=a9d37090ba0bdbb2 kernel: 4.20.10-200.fc29.x86_64 package: powertop-2.9-9.fc29 reason: powertop killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 0
Similar problem has been detected: Always after executing powertop. reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: powertop crash_function: perf_event::process executable: /usr/sbin/powertop journald_cursor: s=aabad073e7894233b8f7280604b1c1e0;i=ab5d8d8;b=1e8764c99707456bba35731e43bac77d;m=354cf5ea40;t=582d94f7d58db;x=d6b69f8a6c835b07 kernel: 4.20.10-200.fc29.x86_64 package: powertop-2.9-9.fc29 reason: powertop killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 0
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.