From: Manfred Spraul <manfred@colorfullife.com>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Julia Lawall <julia@diku.dk>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: 2.6.35-rc3 deadlocks on semaphore operations
Date: Sat, 19 Jun 2010 16:43:29 +0200 [thread overview]
Message-ID: <4C1CD791.101@colorfullife.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1006180955141.11575@router.home>
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
next prev parent reply other threads:[~2010-06-19 14:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-18 14:49 2.6.35-rc3 deadlocks on semaphore operations Christoph Lameter
2010-06-18 14:56 ` Christoph Lameter
2010-06-19 14:43 ` Manfred Spraul [this message]
2010-06-21 14:31 ` Christoph Lameter
2010-06-21 16:52 ` Manfred Spraul
2010-06-21 17:13 ` Christoph Lameter
2010-06-18 15:34 ` Julia Lawall
2010-06-19 11:06 ` Manfred Spraul
2010-06-21 17:05 ` Christoph Lameter
2010-06-21 17:16 ` Christoph Lameter
2010-06-21 18:05 ` 2.6.35-rc3 deadlocks on wakeup(?) (was on semaphore operations) Christoph Lameter
2010-06-20 6:55 ` 2.6.35-rc3 deadlocks on semaphore operations Maciej Rutecki
2010-06-21 20:01 ` Luca Tettamanti
2010-06-23 16:29 ` Manfred Spraul
2010-06-23 19:14 ` Luca Tettamanti
2010-06-24 19:22 ` Luca Tettamanti
2010-06-25 21:09 ` Manfred Spraul
2010-06-26 12:52 ` Luca Tettamanti
2010-06-26 15:47 ` 2.6.35-rc3: System unresponsive under load Manfred Spraul
2010-06-26 15:49 ` Manfred Spraul
2010-06-26 16:47 ` Luca Tettamanti
2010-06-30 19:07 ` Manfred Spraul
2010-07-06 16:01 ` Luca Tettamanti
2010-07-07 19:34 ` Luca Tettamanti
2010-07-02 15:53 ` 2.6.35-rc3 deadlocks on semaphore operations Manfred Spraul
2010-06-23 20:27 ` Christoph Lameter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C1CD791.101@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=julia@diku.dk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.