Re: 2.6.35-rc3 deadlocks on semaphore operations

[Manfred Spraul]

Hello Christoph,

On 06/18/2010 04:56 PM, Christoph Lameter wrote:
> One important fact that I forgot to mention: This is on a dual quad core
> dell box (8 hardware threads) with CONCURRENCY_LEVEL set to 9.
>    

- Which version of make do you use? That would be one suspect that might 
use semop().

- If I run make -j5 bzImage, then no semaphore arrays are used.
Could you try to figure out which executable is doing the 'semop()' call?
Or: what's the output of ps xawwwww_

- You are able to attach to the sleeping process with strace - and the 
process continues to wait.
I think this means that the semaphore counter is really 0: Somehow, we 
leak semaphore values.

But I did not change this code, what was changed was the wake-up code.

--
    Manfred
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/