On Wed, Apr 17, 2013 at 10:25:36PM +0200, Toralf Förster wrote: > trinity forgot the name of syscall 11 (while running within a UML instance) > > ... > [watchdog] 21055 iterations. [F:16827 S:4223] > [watchdog] pid 2481 hasn't made progress in 30 seconds! (last:1366229784 now:1366229814 diff:30). Stuck in syscall 267:clock_nanosleep. Sending SIGKILL. > [watchdog] pid 2500 hasn't made progress in 30 seconds! (last:1366229804 now:1366229834 diff:30). Stuck in syscall 267:clock_nanosleep. Sending SIGKILL. > [watchdog] pid 2519 hasn't made progress in 30 seconds! (last:1366229816 now:1366229846 diff:30). Stuck in syscall 11:. Sending SIGKILL. > [watchdog] pid 2522 hasn't made progress in 30 seconds! (last:1366229818 now:1366229848 diff:30). Stuck in syscall 11:. Sending SIGKILL. Stuck in execve. Don't know why it couldn't print out the name, but I knew about the problem of children not coming back from execve. I guess I should do that syscall in a child of the child. Dave -- To unsubscribe from this list: send the line "unsubscribe trinity" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
