CoreDump on version 2.9 and git.
by Pablo Catalina
Hi,
I have an Ubuntu 18.04 with kernel 4.20.10 (compiled manually with default Ubuntu options but changing the processor type to Xeon)
I tested the version 2.9 and the latest code from git (tag 2.10):
# git log
e8765b5 (HEAD -> master, tag: v2.10, origin/master, origin/HEAD) src/wakeup/wakeup.h: Fix a minor issue in the wakeup.h file
And I got a coredump when I run it normally and with --auto-tune (I dont have the coredump with --debug).
The same coredump on normal run and with --auto-autotune.
See attached the output of gdb (bt, registers, ...) and the coredump.
Let me know if I can do anything else to help you to fix the bug, I'm not C developer but I have a minimal knowledge about compiling code, patching, debug, ...
Regards,
Pablo
3 years, 2 months
Re: [Powertop] CoreDump on version 2.9 and git.
by Kammela, Gayatri
Hi Harvey,
Great! Thanks for the update.
Thanks,
Gayatri
> -----Original Message-----
> From: Harvey [mailto:harv@gmx.de]
> Sent: Friday, February 22, 2019 5:25 AM
> To: Kammela, Gayatri <gayatri.kammela(a)intel.com>
> Subject: Re: [Powertop] CoreDump on version 2.9 and git.
>
> Hi all
>
> as Pablo already stated the issue has gone with kernel 4.20.11. All my
> machines using powertop are back to normal now.
>
> Greetings
> Harvey
>
> Am 20.02.19 um 11:21 schrieb Kammela, Gayatri:
> > Hi Harvey,
> > Thanks for the report! I will try and reproduce the issue on ArchLinux. Just
> curious if Archlinux has any issues with PowerTop v2.9 on 4.20 kernel as well.
> >
> > Thanks,
> > Gayatri
> >
> >> -----Original Message-----
> >> From: PowerTop [mailto:powertop-bounces@lists.01.org] On Behalf Of
> >> Harvey
> >> Sent: Tuesday, February 19, 2019 2:05 AM
> >> To: powertop(a)lists.01.org
> >> Subject: Re: [Powertop] CoreDump on version 2.9 and git.
> >>
> >> Hello,
> >>
> >> please forgive me to chime in here, but...
> >>
> >> this happens as well on Archlinux with a vanilla kernel
> >> 4.20.10-arch1-1-ARCH and powertop 2.10
> >> (https://www.archlinux.org/packages/community/x86_64/powertop/)
> >>
> >> If one starts powertop it bails out with
> >>
> >> Feb 19 11:03:13 obelix systemd-coredump[14698]: Process 14692
> >> (powertop) of user 0 dumped core.
> >>
> >> Stack trace of thread 14692:
> >> #0 0x000055868ba1d157 n/a (powertop)
> >> #1 0x000055868ba1df22 n/a (powertop)
> >> #2 0x000055868b9f7cb3 n/a (powertop)
> >> #3 0x000055868b9f2556 n/a (powertop)
> >> #4 0x000055868b9e8a16 n/a (powertop)
> >> #5
> >> 0x00007f7215905223 __libc_start_main
> >> (libc.so.6)
> >> #6
> >> 0x000055868b9e9b5e n/a (powertop)
> >>
> >>
> >> HTH
> >>
> >> Greetings
> >> Harvey
> >>
> >> Am 19.02.19 um 10:30 schrieb Kammela, Gayatri:
> >>> Hi Pablo,
> >>> Thanks for reporting! I have tried powertop v2.9 and v2.10 on kernel
> >>> 4.20
> >> with Ubuntu generic+ additional config options and didn't notice any
> >> core dump issues. I have changed the processor type to Xeon and I
> >> couldn't reproduce it. Could you please share the kernel config that
> >> you've used to reproduce this issue? Also, could you try running
> >> latest powertop with latest kernel to see if it is still reproducible?
> >>>
> >>> Thanks,
> >>> Gayatri
> >>>
> >>>> -----Original Message-----
> >>>> From: PowerTop [mailto:powertop-bounces@lists.01.org] On Behalf Of
> >>>> Pablo Catalina
> >>>> Sent: Monday, February 18, 2019 1:46 PM
> >>>> To: powertop(a)lists.01.org
> >>>> Subject: [Powertop] CoreDump on version 2.9 and git.
> >>>>
> >>>> Hi,
> >>>>
> >>>> I have an Ubuntu 18.04 with kernel 4.20.10 (compiled manually with
> >>>> default Ubuntu options but changing the processor type to Xeon)
> >>>>
> >>>>
> >>>> I tested the version 2.9 and the latest code from git (tag 2.10):
> >>>>
> >>>> # git log
> >>>>
> >>>> e8765b5 (HEAD -> master, tag: v2.10, origin/master, origin/HEAD)
> >>>> src/wakeup/wakeup.h: Fix a minor issue in the wakeup.h file
> >>>>
> >>>>
> >>>> And I got a coredump when I run it normally and with --auto-tune (I
> >>>> dont have the coredump with --debug).
> >>>>
> >>>>
> >>>> The same coredump on normal run and with --auto-autotune.
> >>>>
> >>>>
> >>>> See attached the output of gdb (bt, registers, ...) and the coredump.
> >>>>
> >>>>
> >>>> Let me know if I can do anything else to help you to fix the bug,
> >>>> I'm not C developer but I have a minimal knowledge about compiling
> >>>> code, patching, debug, ...
> >>>>
> >>>>
> >>>>
> >>>> Regards,
> >>>>
> >>>>
> >>>> Pablo
> >>>
> >>> _______________________________________________
> >>> PowerTop mailing list
> >>> PowerTop(a)lists.01.org
> >>> https://lists.01.org/mailman/listinfo/powertop
> >>>
> >>
> >> --
> >> I am root. If you see me laughing, you'd better have a backup!
> >
>
> --
> I am root. If you see me laughing, you'd better have a backup!
3 years, 2 months
issue with powertop, linux kernel 4.20 and OpenSuse
by Ivo Nenchev
After upgrade of operation system OpenSuse Tumbleweed to the last version
and after upgrade kernel to 4.20 I received an issue with powertop.
After command :
systemctl enable powertop && systemctl start powertop
I received issue with follow text :
powertop.service - Extend the battery life of laptop
Loaded: loaded (/usr/lib/systemd/system/powertop.service; enabled; vendor
preset: disabled)
Active: failed (Result: core-dump) since Wed 2019-02-13 23:07:48 EET; 5s ago
Process: 15964 ExecStart=/usr/sbin/powertop --auto-tune (code=dumped,
signal=SEGV)
Main PID: 15964 (code=dumped, signal=SEGV)
Feb 13 23:07:47 linux-qx0s powertop[15964]: Devfreq not enabled
Feb 13 23:07:47 linux-qx0s powertop[15964]: glob returned GLOB_ABORTED
Feb 13 23:07:47 linux-qx0s powertop[15964]: failed to mmap with 12 (Не може
да се задели памет)
Feb 13 23:07:47 linux-qx0s powertop[15964]: failed to mmap with 12 (Не може
да се задели памет)
Feb 13 23:07:47 linux-qx0s powertop[15964]: failed to mmap with 12 (Не може
да се задели памет)
Feb 13 23:07:47 linux-qx0s powertop[15964]: failed to mmap with 12 (Не може
да се задели памет)
Feb 13 23:07:47 linux-qx0s powertop[15964]: failed to mmap with 12 (Не може
да се задели памет)
Feb 13 23:07:48 linux-qx0s systemd[1]: powertop.service: Main process
exited, code=dumped, status=11/SEGV
Feb 13 23:07:48 linux-qx0s systemd[1]: powertop.service: Failed with result
'core-dump'.
Feb 13 23:07:48 linux-qx0s systemd[1]: Failed to start Extend the battery
life of laptop.
p.s.
The version of the PowerTop is 2.10
3 years, 2 months
SIGSEGV (Address boundary error) on Ubuntu 19.04 with kernel 5.0
by Sparr
The last time I ran powertop, a few days ago, it worked fine. Since then
I've updated my kernel. Then today I get what looks like the usual initial
behavior, output to the console like this:
modprobe cpufreq_stats failedLoaded 391 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
then the console clears and there is an approx two second delay, which is
also normal. Then when I would expect the first screen of data to appear,
instead powertop crashes with SIGSEGV (Address boundary error). I'm putting
further details of the segfault in this gist, which I can update as I learn
more about using gdb and slowly bisect the kernel commit history to find
the change that triggers the misbehavior.
https://gist.github.com/sparr/fc97f4a265971bf720aedeaeb6874fd6
I would appreciate help in narrowing down the cause of the problem, or even
someone confirming that they do or do not have this problem on kernel 5.
Thank you.
3 years, 3 months
