Subject: Re: 2.6.14-rt21 & evolution
From: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: dino@in.ibm.com
Cc: Lee Revell <rlrevell@joe-job.com>, Ingo Molnar <mingo@elte.hu>,
       linux-kernel <linux-kernel@vger.kernel.org>
In-Reply-To: <20051204145823.GA5756@in.ibm.com>
References: <1133642866.16477.11.camel@cmn3.stanford.edu>
	 <1133647737.5890.2.camel@mindpipe>
	 <1133653696.16477.47.camel@cmn3.stanford.edu>
	 <20051204145823.GA5756@in.ibm.com>
Content-Type: text/plain
Date: Sun, 04 Dec 2005 16:40:21 -0800
Message-Id: <1133743221.20894.3.camel@cmn34.stanford.edu>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1011
Lines: 27

On Sun, 2005-12-04 at 20:28 +0530, Dinakar Guniguntala wrote:
> On Sat, Dec 03, 2005 at 03:48:16PM -0800, Fernando Lopez-Lezcano wrote:
> > 
> > To tell the truth this does not seem like a -rt related problem except
> > that it started happening the day I booted into -rt21. 
> > 
> 
> Can you try this patch below. Ingo has already included it in his tree
> and will probably show up in -rt22.
> 
> This was changed in -rt14 and returns spurious -ETIMEDOUT from
> FUTEX_WAIT calls which I just checked that evo does a lot of

I'll definitely try this and report back. Thanks!

I just double checked, and had no trouble starting evolution with a
previous kernel on a different machine (after several days of having the
same problem running on -rt21). 

-- Fernando


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