1 |
On 2017-12-06, Mick <michaelkintzios@×××××.com> wrote: |
2 |
> On Wednesday, 6 December 2017 21:01:25 GMT Grant Edwards wrote: |
3 |
>> On 2017-12-06, Mick <michaelkintzios@×××××.com> wrote: |
4 |
>> > I discovered that building Chromium with gcc-6.4.0 is taking an |
5 |
>> > inordinately> |
6 |
>> > longer time on a laptop with 1st gen i7 and 4G of RAM, e.g.: |
7 |
> [snip ...] |
8 |
> |
9 |
>> Did the CPU throttling stuff somehow get broken when you updated to |
10 |
>> gcc-6.4.0? |
11 |
[...] |
12 |
> Hmm ... I have not changed anything related to CPU throttling I can remember. |
13 |
> Which reminds me, perhaps I should 'make clean' my kernel now that I have |
14 |
> switched to gcc-6.4.0? |
15 |
|
16 |
Shouldn't need to. I think my throttling got broken when I updated |
17 |
kernels. |
18 |
|
19 |
> i7z shows turbo mode kicks in too and hyperthreading is on (attached). Under |
20 |
> turbo it jumps up to 2.8GHz. So cpu throttling is probably not the cause of |
21 |
> my problem, unless it throttles more now than it used to do before? :-/ |
22 |
|
23 |
If throttling were broken it would be pretty obvious: when you do 'cat |
24 |
/proc/cpuinfo' in the middle of an emerge, it would show 500MHz (or |
25 |
whatever) as the core frequency. [It still took me half a day to |
26 |
find out that's what was wrong.] |
27 |
|
28 |
-- |
29 |
Grant Edwards grant.b.edwards Yow! I want to dress you |
30 |
at up as TALLULAH BANKHEAD and |
31 |
gmail.com cover you with VASELINE and |
32 |
WHEAT THINS ... |