Re: [Powertop] SIGSEGV (Address boundary error) on Ubuntu 19.04 with kernel 5.0

Re: [Powertop] SIGSEGV (Address boundary error) on Ubuntu 19.04 with kernel 5.0

[Kammela, Gayatri]

[-- Attachment #1: Type: text/plain, Size: 1679 bytes --]

Hi,
The issue was  first noticed on 2/11 and it was due to this patch https://lkml.org/lkml/2019/2/12/452 . The fix was suggested by Peter Z and I believe the fix is not merged yet to the mainline. Please use the above link to try the fix and build the kernel. It should work with the fix. I had tested it yesterday and it worked fine!

Thanks,
Gayatri

From: PowerTop [mailto:powertop-bounces(a)lists.01.org] On Behalf Of Sparr
Sent: Wednesday, February 13, 2019 4:13 PM
To: powertop(a)lists.01.org
Subject: [Powertop] SIGSEGV (Address boundary error) on Ubuntu 19.04 with kernel 5.0

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.

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 4848 bytes --]

[Powertop] SIGSEGV (Address boundary error) on Ubuntu 19.04 with kernel 5.0

[Sparr]

[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]

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.

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 1236 bytes --]