1 |
Am Sun, 19 Feb 2017 14:11:29 +0100 |
2 |
schrieb Miroslav Rovis <miro.rovis@××××××××××××××.hr>: |
3 |
|
4 |
> On 170219-13:53+0100, Helmut Jarausch wrote: |
5 |
> > Hi, |
6 |
> > |
7 |
> > sometime I have some memory hungry ebuilds in the background, when |
8 |
> > I |
9 |
> Ebuilds are just text files, they don't run in the background... |
10 |
> |
11 |
> > start (e.g.) Chromium which needs very much memory if you have a |
12 |
> > lot of open tabs. |
13 |
> ( Chromium is the most privacy-invading browser ever. It's a spyware, |
14 |
> I could never use it, but forget about that, it's not what this topic |
15 |
> is about... ) |
16 |
> > In that case my system nearly freezes. I cannot even kill chrome. |
17 |
> > What can I do in that case. (Remote login doesn't work either) |
18 |
> Try Ctrl+Alt+Fx |
19 |
> where x is one of F1 ... F6 |
20 |
> and then issue: |
21 |
> # killa chromium |
22 |
> > |
23 |
> > Can I have any additional program (like Chromium) die if there is |
24 |
> > not enough memory. |
25 |
> > |
26 |
> > Many thanks for a hint, |
27 |
> > Helmut |
28 |
> > |
29 |
> This could be a hardware, not a software issue. Also, not sure, but |
30 |
> looks like, not a memory issue, but a CPU issue. |
31 |
> |
32 |
> It's likely the CPU triggers the BIOS to shut down because CPU gets |
33 |
> too hot, but because it is not properly implemented, what happens is |
34 |
> even worse than doing nothing, and that is: the system freezes, but |
35 |
> the CPU keeps running... Bad! |
36 |
> |
37 |
> How warm does you machine, try to touch it in the back, or under, if |
38 |
> it's a laptop, where ther CPU is? |
39 |
> |
40 |
> It reminds me of what I had. My systems, that had only the original, |
41 |
> run-of-the-mill coolers on the CPUs (I bought a few of same model MBO, |
42 |
> so i can clone my systems)... The usual 80mm coolers. |
43 |
> |
44 |
> As soon as I replaced them with 120mm coolers, no issues any more. |
45 |
|
46 |
I can second this. An optimized parallel emerge is able to keep your |
47 |
cores fully busy at 100% almost all of the time. All components of the |
48 |
cores are needed, so there's a lot of heat produced (artificial |
49 |
benchmarks usually cannot do the same). You should see lines about |
50 |
machine check exceptions (MCE) or CPU throttling logged into dmesg if |
51 |
this hits you. CPU throttling is a real performance killer (ebuilds |
52 |
suddenly take 10x the time) and may well explain what you are |
53 |
seeing. Getting bigger fans and coolers can do magic here, even the |
54 |
cheap ones. |
55 |
|
56 |
I've only lately swapped the stock cooler for a Mars T1 and could now |
57 |
set the turbo frequency limit back to 4.2 GHz without seeing these |
58 |
messages during emerge (3.7 stock limit). Before, I had to turn off |
59 |
turbo. I think the stock cooler was just aging (and dusted, couldn't |
60 |
be removed, stuck like glue to the cooler). |
61 |
|
62 |
So, check your cooler, blow the dust away, check the fan if it still |
63 |
easily rotates when pushed with a finger while turned off. It helps a |
64 |
lot. Maybe swap it with a better cooler/fan if you're experiencing |
65 |
throttling (I recommend it). |
66 |
|
67 |
-- |
68 |
Regards, |
69 |
Kai |
70 |
|
71 |
Replies to list-only preferred. |