On Fri, Jan 7, 2011 at 7:56 AM, Simon <turne...@gmail.com> 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.
Uhhg....doesn't sound good at all. If it's dieing on emerge -e system I'd be a little suspicious of a drive or file system failure of some type. Do you have access to smartctl to get to info on the drive? fsck possibly? Good luck, Mark
