From: Clark Williams <williams@redhat.com>
To: Darren Hart <dvhltc@us.ibm.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
RT <linux-rt-users@vger.kernel.org>
Subject: Re: futex warning tracback on 2.6.29.1-rt6
Date: Fri, 10 Apr 2009 12:10:48 -0500 [thread overview]
Message-ID: <20090410121048.2d06360d@torg> (raw)
In-Reply-To: <49DF6AC2.4000801@us.ibm.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, 10 Apr 2009 08:50:26 -0700
Darren Hart <dvhltc@us.ibm.com> wrote:
>
> OK, looks like we have some key management issues to sort out. Clark, I presume you weren't running
> the glibc patch to enable requeue_pi? From the trace below this appears to have happened during a
> normal futex_wait() call. Looking at futex_wait_setup() I see a rather obvious bug:
>
That's correct, I was just running the stock F10 glibc.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (GNU/Linux)
iEYEARECAAYFAknffZ0ACgkQHyuj/+TTEp2yXACeJB0p/GlgzjuMXU5MHGdOniNT
J2oAmwREpNfq83JOP+OuxTqPTaXkzLDQ
=tZu+
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2009-04-10 17:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-10 2:55 futex warning tracback on 2.6.29.1-rt6 Clark Williams
2009-04-10 15:50 ` Darren Hart
2009-04-10 17:10 ` Clark Williams [this message]
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=20090410121048.2d06360d@torg \
--to=williams@redhat.com \
--cc=dvhltc@us.ibm.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.