Messages in this thread | | | Date | Wed, 3 May 2006 18:25:21 +0200 (MEST) | From | Jan Engelhardt <> | Subject | Re: [ck] 2.6.16-ck9 |
| |
> >I tried to run SetiAtHome at IDLEPRIO, but it competes equally with a >while(1); loop run at nice 19. I'm starting to wonder if there isn't >some kind of bug in the kernel which results in a program returning from >a system call with an in-kernel semaphore held. After all, according to >top, SetiAtHome consumes over 90% CPU, and the system consumes only >about 1%, so it can't be making system calls all the time either.
SAH does make very few system calls in relation to its computing, in fact. [It's a guess, not a proven answer.] The boinc supervisor process is mostly the syscall, filesystem and networking part.
>This pattern just keeps on repeating, endlessly. Occasionally it also >has > >kill(5432, SIG_0) = 0 > >attached to it. 5432 is the parent process, the FAH502-Linux.exe.
You don't use boinc?
>There is something very strange going on here...
Jan Engelhardt -- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |