| 1 |
Ok, the fsck reported nothing wrong... |
| 2 |
I still got the same bug again... while doing `emerge -e @system`... |
| 3 |
It got stuck right after the ">>> Installing" line below... |
| 4 |
|
| 5 |
Dale, I just checked my python version and it was already 2.6, i set |
| 6 |
it to 2.6 again, just in case, and continued my emerge (the ctrl-z + |
| 7 |
%% worked at this point). |
| 8 |
|
| 9 |
I'll reply here again with the next issue... |
| 10 |
|
| 11 |
Thanks, |
| 12 |
Simon |
| 13 |
|
| 14 |
//////////////////////////////////////////////////////// |
| 15 |
>>> Emerging (35 of 151) sys-devel/binutils-config-1.9-r4 |
| 16 |
* Package: sys-devel/binutils-config-1.9-r4 |
| 17 |
* Repository: gentoo |
| 18 |
* Maintainer: toolchain@g.o |
| 19 |
* USE: elibc_glibc kernel_linux userland_GNU x86 |
| 20 |
>>> Unpacking source... |
| 21 |
>>> Source unpacked in /mnt/tmp/portage/sys-devel/binutils-config-1.9-r4/work |
| 22 |
>>> Compiling source in /mnt/tmp/portage/sys-devel/binutils-config-1.9-r4/work ... |
| 23 |
>>> Source compiled. |
| 24 |
>>> Test phase [not enabled]: sys-devel/binutils-config-1.9-r4 |
| 25 |
|
| 26 |
>>> Install binutils-config-1.9-r4 into /mnt/tmp/portage/sys-devel/binutils-config-1.9-r4/image/ category sys-devel |
| 27 |
>>> Completed installing binutils-config-1.9-r4 into /mnt/tmp/portage/sys-devel/binutils-config-1.9-r4/image/ |
| 28 |
|
| 29 |
ecompressdir: bzip2 -9 /usr/share/man |
| 30 |
|
| 31 |
>>> Installing (35 of 151) sys-devel/binutils-config-1.9-r4 |
| 32 |
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ |
| 33 |
|
| 34 |
|
| 35 |
|
| 36 |
|
| 37 |
On Fri, Jan 7, 2011 at 1:22 PM, Dale <rdalek1967@×××××.com> wrote: |
| 38 |
> Simon wrote: |
| 39 |
>> |
| 40 |
>> Hi there, |
| 41 |
>> something went wrong during a previous update and now revdep-rebuild |
| 42 |
>> will kind-of freeze around 30%. When it freezes like that, the |
| 43 |
>> hosting company shows one of it's CPU core is used at 100% non-stop |
| 44 |
>> and the rest is idle. I have tried `emerge -e world` and with system, |
| 45 |
>> they all fail similarly. |
| 46 |
>> |
| 47 |
>> I managed to reconfigure it to have a working console and started |
| 48 |
>> the `emerge -e system` from the console. After a while it froze, but |
| 49 |
>> typed a ctrl-z to suspend the process, then %% to resume it and it |
| 50 |
>> "unlocked" it. It often hung like in between two phases of the emerge |
| 51 |
>> process (like after unpacking source, or just before doing the |
| 52 |
>> install, etc). I was able to resume the emerge like that a good dozen |
| 53 |
>> times until now, and now it's really locked, not responding at all... |
| 54 |
>> seems like all 4 cores are used at 100%. |
| 55 |
>> |
| 56 |
>> It hung while emerging perl and I've included the output on the |
| 57 |
>> console below so you can see exactly where it hung. I will now force |
| 58 |
>> a reboot on it and retry emerging just perl, I will reply to the list |
| 59 |
>> with my results of that. |
| 60 |
>> |
| 61 |
> |
| 62 |
> <<SNIP>> |
| 63 |
> |
| 64 |
> Have you enabled python3 by any chance? eselect python list should show 2.6 |
| 65 |
> as the active python. |
| 66 |
> |
| 67 |
> Just a thought. Someone else did this the other day and had troubles. |
| 68 |
> |
| 69 |
> Dale |
| 70 |
> |
| 71 |
> :-) :-) |
| 72 |
> |
| 73 |
> |
Archives