[SOLVED] Internal Compiler Error trying to compile qt5 and PyQt5

maew · 11-09-2016, 05:30 AM

okay, indeed they are at max frequency for the moment.

So with the icepack the compilation went through ><

However I tried to change the frequency with

Code:

#cpufreq-set -c 1 -f  1GHz
Error setting new values. Common errors:
- Do you have proper administration rights? (super-user?)
- Is the governor you requested available and modprobed?
- Trying to set an invalid policy?
- Trying to set a specific frequency, but userspace governor is not available,
   for example because of hardware which cannot be set to a specific frequency
   or because the userspace governor isn't loaded?

andin cpufreq-info they tell me :

current policy: frequency should be within 500 MHz and 3.40 GHz.
The governor "powersave" may decide which speed to use
within this range.

So the frequency is within range, and the cpu's are in governor: powersave.

From my understanding I should be able to change the cpu frequencies.

Am I missing something?

EDIT: and to confirm, yes i am su -

Thanks for your time

bassmadrigal · 11-09-2016, 06:52 AM

I do see an extra space between the -f and the 1GHz frequency. That could be your problem depending on how cpufreq-set parses the options. But it might also need to be using the userspace governor to set specific values, however, I don't believe all processors support that.

You could also try to limit the upper end of frequency scaling to see if that helps.

Code:

echo 1000000 | tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_max_freq

phenixia2003 · 11-09-2016, 07:08 AM

Hello,

Quote:

Originally Posted by maew

okay, indeed they are at max frequency for the moment.

So with the icepack the compilation went through ><

However I tried to change the frequency with

Code:

#cpufreq-set -c 1 -f  1GHz
Error setting new values. Common errors:
- Do you have proper administration rights? (super-user?)
- Is the governor you requested available and modprobed?
- Trying to set an invalid policy?
- Trying to set a specific frequency, but userspace governor is not available,
   for example because of hardware which cannot be set to a specific frequency
   or because the userspace governor isn't loaded?

andin cpufreq-info they tell me :

current policy: frequency should be within 500 MHz and 3.40 GHz.
The governor "powersave" may decide which speed to use
within this range.

So the frequency is within range, and the cpu's are in governor: powersave.

From my understanding I should be able to change the cpu frequencies.

Am I missing something?

EDIT: and to confirm, yes i am su -

Thanks for your time

AFAIK, cpufreq-set does not work with "recent" intel processors (>=sandy bridge) unless pstate is disabled (ie. kernel parameter intel_pstate=disabled). Instead, you can use pstate-frequency for which I recently wrote a slackbuild available here.

To get current CPU values, run it as below :

Code:

$ pstate-frequency --get
    pstate::CPU_DRIVER   -> intel_pstate
    pstate::CPU_GOVERNOR -> powersave
    pstate::TURBO        -> 0 [ON]
    pstate::CPU_MIN      -> 43% [1600000KHz]
    pstate::CPU_MAX      -> 100% [3700000KHz]

To set min/max CPU frequency (expressed in percentage), run it as below :

Code:

$ pstate-frequency --set --min 60 --max 70
pstate-frequency version 3.6.0
    pstate::CPU_DRIVER   -> intel_pstate
    pstate::CPU_GOVERNOR -> powersave
    pstate::TURBO        -> 0 [ON]
    pstate::CPU_MIN      -> 60% [2220000KHz]
    pstate::CPU_MAX      -> 70% [2590000KHz]

You can also use a predefined power plan. The package includes 5 predefined plans (in /etc/pstate-frequency.d) and you can create your own plans. For instance, to select the plan "powersave", run pstate-frequency (as root) as below :

Code:

$ pstate-frequency --set --plan powersave
pstate-frequency version 3.6.0
    pstate::CPU_DRIVER   -> intel_pstate
    pstate::CPU_GOVERNOR -> powersave
    pstate::TURBO        -> 1 [OFF]
    pstate::CPU_MIN      -> 43% [1600000KHz]
    pstate::CPU_MAX      -> 44% [1628000KHz]

--
SeB

maew · 11-10-2016, 08:47 AM

Thanks so much

your help and comments were really helpful.

pstate-frequency is working a charm !

kjhambrick · 11-11-2016, 04:25 AM

Thanks for the SBo files SeB !

Works great and pstate-frequency is an excellent utility.

-- kjh

fgcl2k · 04-03-2017, 03:29 AM

I am reviving this thread because I found a solution which worked for me and could be useful for others with the same problem.
I had exactly the same problem mentioned in post #9 but none of the solutions worked. The error occurred mostly when compiling big packages like qt-creator, or webkit. The compilation stopped always in the same places and with the same errors but could be resumed (with a small change to the SlackBuild.) Usually two or three times was enough to produce the package.

Code:

In file included from /usr/include/c++/5.3.0/random:42:0,
                 from /usr/include/c++/5.3.0/bits/stl_algo.h:66,
                 from /usr/include/c++/5.3.0/algorithm:62,
                 from /usr/include/qt5/QtCore/qglobal.h:94,
                 from .moc/release-shared/../../utils_global.h:28,
                 from .moc/release-shared/../../savedaction.h:28,
                 from .moc/release-shared/moc_savedaction.cpp:9:
/usr/include/c++/5.3.0/limits:1734:10: internal compiler error: Errore di segmentazione
        = round_to_nearest;
          ^
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.

I tried changing RAM, hard disk, patching and recompiling the compiler (and mpc, mpfr, gmp), and many other things without success. CPU temperature was not an issue. I have this CPU:

Quote:

vendor_id : GenuineIntel
cpu family : 6
model : 61
model name : Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz
stepping : 4
microcode : 0x18
cpu MHz : 1936.687
cache size : 4096 KB

After weeks of tests and reading forums, I solved the problem installing the intel-microcode package from Slackbuilds.org and creating a new initrd as explained in the README.
The CPU microcode went from revision=0x18 to revision=0x24 and the compilation problem disappeared: I have successfully recompiled qt-creator and webkit several times.
I removed the microcode update from the initrd and the error returned: therefore I am confident that the new microcode solves the problem.