On Tue, Mar 9, 2010 at 4:54 PM, dann frazier <[email protected]> wrote: > --- SIGVTALRM (Virtual timer expired) @ 0 (0) --- > rt_sigreturn() = -819 > clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, > child_tidptr=0x40002b28) = -513 > --- SIGVTALRM (Virtual timer expired) @ 0 (0) --- > rt_sigreturn() = -819 > clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, > child_tidptr=0x40002b28) = -513 > --- SIGVTALRM (Virtual timer expired) @ 0 (0) --- > rt_sigreturn() = -819 > clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, > child_tidptr=0x40002b28) = -513 > --- SIGVTALRM (Virtual timer expired) @ 0 (0) --- > rt_sigreturn() = -819 > >> Anyway, this seems to be something that was introduced with 6.12. I >> wonder what we can do about this, besides p-a-s.
Error -513 is ERESTARTNOINTR. It appears that the process is executing clone when it gets a SIGVTALRM, after which the kernel restart the clone, but the whole process repeats over and over again? I don't know what's wrong in this case, somebody will have to debug this. Cheers, Carlos. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
