Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750961AbVKYE4J (ORCPT ); Thu, 24 Nov 2005 23:56:09 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1161094AbVKYE4J (ORCPT ); Thu, 24 Nov 2005 23:56:09 -0500 Received: from gateway-1237.mvista.com ([12.44.186.158]:3580 "EHLO hermes.mvista.com") by vger.kernel.org with ESMTP id S1750961AbVKYE4I (ORCPT ); Thu, 24 Nov 2005 23:56:08 -0500 In-Reply-To: <20051124203250.GA9086@in.ibm.com> References: <20051118092909.GC4858@elte.hu> <20051118132137.GA5639@in.ibm.com> <20051118132715.GA3314@elte.hu> <8311ADE9-5855-11DA-BBAB-000A959BB91E@mvista.com> <20051118174454.GA2793@elte.hu> <43822480.6080301@mvista.com> <20051121212653.GA6143@elte.hu> <20051124145734.GA2717@elte.hu> <20051124202637.GB9098@in.ibm.com> <20051124203250.GA9086@in.ibm.com> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit Cc: "David F. Carlson" , linux-kernel@vger.kernel.org, Ingo Molnar From: david singleton Subject: Re: PI BUG with -rt13 Date: Thu, 24 Nov 2005 20:56:06 -0800 To: dino@in.ibm.com X-Mailer: Apple Mail (2.619) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1737 Lines: 57 On Nov 24, 2005, at 12:32 PM, Dinakar Guniguntala wrote: > On Fri, Nov 25, 2005 at 01:56:37AM +0530, Dinakar Guniguntala wrote: >> On Thu, Nov 24, 2005 at 03:57:34PM +0100, Ingo Molnar wrote: >>> >>> * david singleton wrote: >>> >>>> Sure. Attached is the locking fix patch. [...] >>> >>> thanks, applied - it should show up in -rt15. >>> >> >> 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. e.g. pthread_mutexattr_setrobust_np (&mutex_attr, PTHREAD_MUTEX_ROBUST_NP); pthread_mutexattr_setprotocol(&state->mutex_attr, PTHREAD_PRIO_INHERIT); pthread_mutexes that don't have either of these attributes set on the pthread_mutex will exercise the original futex code. 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? If you are not in the OOM path then the bad news is this looks like an SMP timer problem. David > > -Dinakar > - 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/