public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dinakar Guniguntala <dino@in.ibm.com>
To: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Cc: Lee Revell <rlrevell@joe-job.com>, Ingo Molnar <mingo@elte.hu>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.14-rt21 & evolution
Date: Sun, 4 Dec 2005 20:28:23 +0530	[thread overview]
Message-ID: <20051204145823.GA5756@in.ibm.com> (raw)
In-Reply-To: <1133653696.16477.47.camel@cmn3.stanford.edu>

[-- Attachment #1: Type: text/plain, Size: 454 bytes --]

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

	-Dinakar


[-- Attachment #2: revert-timeout.patch --]
[-- Type: text/plain, Size: 501 bytes --]

Index: linux-2.6.14-rt21-rayrt4/kernel/futex.c
===================================================================
--- linux-2.6.14-rt21-rayrt4.orig/kernel/futex.c	2005-12-02 16:55:26.000000000 +0530
+++ linux-2.6.14-rt21-rayrt4/kernel/futex.c	2005-12-02 17:21:20.000000000 +0530
@@ -1527,7 +1527,7 @@
 			  int val3)
 {
 	struct timespec t;
-	unsigned long timeout = 0;
+	unsigned long timeout = MAX_SCHEDULE_TIMEOUT;
 	int val2 = 0;
 
 	if ((op == FUTEX_WAIT || op == FUTEX_WAIT_ROBUST) && utime) {

  reply	other threads:[~2005-12-04 14:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-03 20:47 2.6.14-rt21 & evolution Fernando Lopez-Lezcano
2005-12-03 22:08 ` Lee Revell
2005-12-03 23:48   ` Fernando Lopez-Lezcano
2005-12-04 14:58     ` Dinakar Guniguntala [this message]
2005-12-05  0:40       ` Fernando Lopez-Lezcano
2005-12-05 17:38       ` Fernando Lopez-Lezcano
2005-12-05 17:43         ` Ingo Molnar
2005-12-20 11:17           ` 2.6.15-rc5-rt2 and Kconfig Esben Nielsen

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=20051204145823.GA5756@in.ibm.com \
    --to=dino@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nando@ccrma.Stanford.EDU \
    --cc=rlrevell@joe-job.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox