For a while now I have noticed this utterly baffling behaviour during emerges. While compiling the ebuild, the entire process just.. stops every now and then. Not for every package and not necessarily twice for the same package.. and even if it does, it will most probably happen in a different place. Then again it might do that more than once in one emerge.
Nothing happens in the emerge process during that time, but everything else works just normally. I have never seen that kind of behaviour on anything else except during those emerge compiles. And the duration seems to vary as well, usually around 1-2 minutes. I started to run htop and dstat in the background every time I emerge something. According to those, nothing is hogging up the CPU or IO or anything, the CPU is just twiddling its thumbs while being idle and all emerge related processes are sleeping. The system is otherwise working just normally. Which means that if nothing else is going on, and the emerge has lasted long enough to heat up the CPU, even the fan slows down before the emerge wakes up again.
I can't really say when this has started since I don't usually monitor the emerges, only the results. But since I haven't done any changes to configuration files for a long time, I can be fairly certain that none of that could have caused this.
Just what on earth is going on? I can't even begin to guess where should I start figuring this one out. Anyone got a theory?


