| 1 |
On Fri, Jan 7, 2011 at 7:56 AM, Simon <turner25@×××××.com> wrote: |
| 2 |
> Hi there, |
| 3 |
> something went wrong during a previous update and now revdep-rebuild |
| 4 |
> will kind-of freeze around 30%. When it freezes like that, the |
| 5 |
> hosting company shows one of it's CPU core is used at 100% non-stop |
| 6 |
> and the rest is idle. I have tried `emerge -e world` and with system, |
| 7 |
> they all fail similarly. |
| 8 |
> |
| 9 |
> I managed to reconfigure it to have a working console and started |
| 10 |
> the `emerge -e system` from the console. After a while it froze, but |
| 11 |
> typed a ctrl-z to suspend the process, then %% to resume it and it |
| 12 |
> "unlocked" it. It often hung like in between two phases of the emerge |
| 13 |
> process (like after unpacking source, or just before doing the |
| 14 |
> install, etc). I was able to resume the emerge like that a good dozen |
| 15 |
> times until now, and now it's really locked, not responding at all... |
| 16 |
> seems like all 4 cores are used at 100%. |
| 17 |
> |
| 18 |
> It hung while emerging perl and I've included the output on the |
| 19 |
> console below so you can see exactly where it hung. I will now force |
| 20 |
> a reboot on it and retry emerging just perl, I will reply to the list |
| 21 |
> with my results of that. |
| 22 |
|
| 23 |
Uhhg....doesn't sound good at all. |
| 24 |
|
| 25 |
If it's dieing on emerge -e system I'd be a little suspicious of a |
| 26 |
drive or file system failure of some type. Do you have access to |
| 27 |
smartctl to get to info on the drive? fsck possibly? |
| 28 |
|
| 29 |
Good luck, |
| 30 |
Mark |
Archives