emerge => unresponsive system. [Solved]

Anything that pertains to Portage

Moderator: Moderators

emerge => unresponsive system. [Solved]

Postby colector » Wed Aug 06, 2008 6:00

Hi,
I have a core2 duo system.
when compiling "large ebuilds" (ex crossdev mingw) I've noticed that my system becomes mostly unresponsive after while, consuming 99% of both cores.
I don't know if this is a scheduling problem of kernel linux-2.6.20-sabayon-r3.
Considering that it is not, and that on any other kernel I would get the same behavior, I was wondering if it is possible to run emerge on just one core, to leave the other core for system stuff and user applications?
This is considering that this could be a solution to this problem.
colector
Young Hen
 
Posts: 35
Joined: Wed Aug 06, 2008 5:48

Re: emerge => unresponsive system. Emerge on a single core.

Postby deadfool » Wed Aug 06, 2008 6:54

is your nice value >1? if not put it at something like 5
deadfool
Growing Hen
 
Posts: 124
Joined: Thu Mar 27, 2008 3:56

Re: emerge => unresponsive system. Emerge on a single core.

Postby wolfden » Wed Aug 06, 2008 7:04

wolfden
Sharecropper
 
Posts: 9050
Joined: Sat Jan 14, 2006 0:55
Location: Midwest USA

Re: emerge => unresponsive system. Emerge on a single core.

Postby colector » Wed Aug 06, 2008 12:02

Thanks I'll be trying that. =)
colector
Young Hen
 
Posts: 35
Joined: Wed Aug 06, 2008 5:48

Re: emerge => unresponsive system. Emerge on a single core.

Postby colector » Fri Jan 23, 2009 9:06

Hello,
after a bit of testing (6 months coff coff)
I noticed that the problem seemed to be the fact that when compiling a big package the computer gets really hot.
lm_sensors report 85 - 90 C, laptop dell xps m1210 dualcore 2GHz.

After buying a cooling base, the max temp (during those long compilations) went down to 75C.
No more unresponsive system. wii!

Maybe because of the high temp, the system would get lots of failed computations and the overhead of the automatic correction was hogging the CPU. (or maybe I'm just imagining things).

Actually I remembered this solution, because I have a PIII 800, and I remember one while emerging KDE (gentoo around ~2003 building from a stage 3) I would get these kernel panics completely freezing the system.
Since I was working on the shell with no real time feedback of the system's temperature, I didn't realized what the problem was.
Then (because of a strange noise) I remembered to open the box and noticed that the CPU fan was almost stopping.

Apparently needed some deep cleaning. Both the CPU and PSU fans were full of dust to a stopping condition.
After a bit of cleaning a a tiny bit of oil they were flying smoothly again.

And that's how the story goes.
I'm writing this because when I have problems I try to find solutions to similar problems.
Let's not keep it to ourselves, as it might be useful to someone else.
colector
Young Hen
 
Posts: 35
Joined: Wed Aug 06, 2008 5:48


Return to Portage|Emerge Package Managers

Who is online

Users browsing this forum: No registered users and 1 guest