Ok, the fsck reported nothing wrong...
I still got the same bug again... while doing `emerge -e @system`...
It got stuck right after the ">>> Installing" line below...

Dale, I just checked my python version and it was already 2.6, i set
it to 2.6 again, just in case, and continued my emerge (the ctrl-z +
%% worked at this point).

I'll reply here again with the next issue...

Thanks,
  Simon

////////////////////////////////////////////////////////
>>> Emerging (35 of 151) sys-devel/binutils-config-1.9-r4
 * Package:    sys-devel/binutils-config-1.9-r4
 * Repository: gentoo
 * Maintainer: toolch...@gentoo.org
 * USE:  elibc_glibc kernel_linux userland_GNU x86
>>> Unpacking source...
>>> Source unpacked in /mnt/tmp/portage/sys-devel/binutils-config-1.9-r4/work
>>> Compiling source in /mnt/tmp/portage/sys-devel/binutils-config-1.9-r4/work 
>>> ...
>>> Source compiled.
>>> Test phase [not enabled]: sys-devel/binutils-config-1.9-r4

>>> Install binutils-config-1.9-r4 into 
>>> /mnt/tmp/portage/sys-devel/binutils-config-1.9-r4/image/ category sys-devel
>>> Completed installing binutils-config-1.9-r4 into 
>>> /mnt/tmp/portage/sys-devel/binutils-config-1.9-r4/image/

ecompressdir: bzip2 -9 /usr/share/man

>>> Installing (35 of 151) sys-devel/binutils-config-1.9-r4
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\




On Fri, Jan 7, 2011 at 1:22 PM, Dale <rdalek1...@gmail.com> wrote:
> Simon wrote:
>>
>> Hi there,
>>   something went wrong during a previous update and now revdep-rebuild
>> will kind-of freeze around 30%.  When it freezes like that, the
>> hosting company shows one of it's CPU core is used at 100% non-stop
>> and the rest is idle.  I have tried `emerge -e world` and with system,
>> they all fail similarly.
>>
>>   I managed to reconfigure it to have a working console and started
>> the `emerge -e system` from the console.  After a while it froze, but
>> typed a ctrl-z to suspend the process, then %% to resume it and it
>> "unlocked" it.  It often hung like in between two phases of the emerge
>> process (like after unpacking source, or just before doing the
>> install, etc).  I was able to resume the emerge like that a good dozen
>> times until now, and now it's really locked, not responding at all...
>> seems like all 4 cores are used at 100%.
>>
>>   It hung while emerging perl and I've included the output on the
>> console below so you can see exactly where it hung.  I will now force
>> a reboot on it and retry emerging just perl, I will reply to the list
>> with my results of that.
>>
>
> <<SNIP>>
>
> Have you enabled python3 by any chance?  eselect python list should show 2.6
> as the active python.
>
> Just a thought.  Someone else did this the other day and had troubles.
>
> Dale
>
> :-)  :-)
>
>

Reply via email to