This happens when kerneld has failed and doesn't read its message
queue. As I read ipc/msg.c, it should receive every message in one
second.
> strange stuff ('(route-request <zombie>)' x 8).
If kerneld has stopped, run into an endless loop, forgot its signal
handler or other stuff that should not happen, this is likely to occur
along with the "Ouch, no kerneld" messages. Same if your system is
severely overloaded.
I have seen this myself at times. Stop and restart kerneld is the
easiest way to fix the situation.
olaf
--
___ Olaf.Titz@inka.de or @{stud,informatik}.uni-karlsruhe.de ____
__ o <URL:http://www.inka.de/~bigred/> <IRC:praetorius>
__/<_ >> Just as long as the wheels keep on turning round
_)>(_)______________ I will live for the groove 'til the sun goes down << ____