From: Dinakar Guniguntala <dino@in.ibm.com>
To: david singleton <dsingleton@mvista.com>
Cc: "David F. Carlson" <dave@chronolytics.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: PI BUG with -rt13
Date: Fri, 25 Nov 2005 13:04:23 +0530 [thread overview]
Message-ID: <20051125073423.GA4825@in.ibm.com> (raw)
In-Reply-To: <C9607B8E-5D6F-11DA-90F9-000A959BB91E@mvista.com>
On Thu, Nov 24, 2005 at 08:56:06PM -0800, david singleton wrote:
> On Nov 24, 2005, at 12:32 PM, Dinakar Guniguntala wrote:
>
> >>I just noticed with the above fix, Paul's testcase completely
> >>hangs up and when killed I hit the BUG mentioned below.
> >>Till -rt13, this testcase just ran to completion
> >
> >Forgot to mention that I notice the same failure with -rt15 as well
>
> Good news and bad news.
> Good news. This test doesn't exercise the robust futex code.
> Pthread mutexes that want priority queuing, priority inheritance and/or
> robustness must have either the robust (PTHREAD_MUTEX_ROBUST_NP)
> attribute set and/or the PTHREAD_PRIO_INHERIT attribute set at mutex
> creation time.
Davi, Thank you for looking into this
Yes, this particular testcase does not exercise the robust futex code.
However, the testcase only hangs when I apply your fix on top of
-rt13. A Vanilla -rt13 works fine
> Now a question before the bad news, Are you in the OOM path when you
> think the system is hung? What does 'top' say about freemem and
> available and used swap space?
Since one of the threads is a SCHED_FIFO, the system takes forever
to respond to simple commands like ls/ps. I'll get back on this
>
> If you are not in the OOM path then the bad news is this looks like an
> SMP timer problem.
>
-Dinakar
next prev parent reply other threads:[~2005-11-25 7:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 16:18 PI BUG with -rt13 Dinakar Guniguntala
2005-11-17 16:41 ` Dinakar Guniguntala
2005-11-17 23:03 ` David Singleton
2005-11-18 9:29 ` Ingo Molnar
2005-11-18 13:21 ` Dinakar Guniguntala
2005-11-18 13:27 ` Ingo Molnar
2005-11-18 17:05 ` david singleton
2005-11-18 17:44 ` Ingo Molnar
2005-11-21 19:48 ` David Singleton
2005-11-21 21:26 ` Ingo Molnar
2005-11-22 2:01 ` david singleton
2005-11-24 14:57 ` Ingo Molnar
2005-11-24 20:26 ` Dinakar Guniguntala
2005-11-24 20:32 ` Dinakar Guniguntala
2005-11-24 22:25 ` david singleton
2005-11-25 4:56 ` david singleton
2005-11-25 7:34 ` Dinakar Guniguntala [this message]
2005-11-25 8:04 ` Dinakar Guniguntala
2005-11-25 5:04 ` Ingo Molnar
2005-11-25 13:27 ` Dinakar Guniguntala
2005-11-25 8:03 ` Ingo Molnar
2005-11-22 2:13 ` david singleton
[not found] ` <8D664A17-5B07-11DA-A840-000A959BB91E@mvista.com>
2005-11-22 9:37 ` Dinakar Guniguntala
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=20051125073423.GA4825@in.ibm.com \
--to=dino@in.ibm.com \
--cc=dave@chronolytics.com \
--cc=dsingleton@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.