Date: Wed, 3 May 2006 18:25:21 +0200 (MEST)
From: Jan Engelhardt <jengelh@linux01.gwdg.de>
To: Juho Saarikko <juhos@mbnet.fi>
cc: Con Kolivas <kernel@kolivas.org>, ck list <ck@vds.kolivas.org>,
       linux list <linux-kernel@vger.kernel.org>
Subject: Re: [ck] 2.6.16-ck9
In-Reply-To: <1146603461.5213.32.camel@a88-112-69-25.elisa-laajakaista.fi>
Message-ID: <Pine.LNX.4.61.0605031821140.13546@yvahk01.tjqt.qr>
References: <200605022338.20534.kernel@kolivas.org>
 <1146603461.5213.32.camel@a88-112-69-25.elisa-laajakaista.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1156
Lines: 31

>
>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/