From: "Robboy, David G" <david.g.robboy@intel.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] pthread_mutex_lock sometimes fails on Linux 2.4.5
Date: Wed, 27 Jun 2001 18:06:12 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005787@msgid-missing> (raw)
On a 4P Lion with Red Hat 7.0.98 installed and a 2.4.5 kernel, a 4P fft
application sometimes hangs in a barrier. All 4 threads get into the
barrier and none get out because a count gets up to 3 and they are waiting
for it to get to 4. I changed my barrier code to use an assembly language
lock instead of pthread_mutex_lock(), and it works reliably now. Either
there is a bug in pthread_mutex_lock, or else a memory management bug in the
kernel. I've worked around this and it is not causing me a problem now. If
anyone wants to investigate and debug this, I'll be glad to supply a test
case.
David Robboy
reply other threads:[~2001-06-27 18:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=marc-linux-ia64-105590693005787@msgid-missing \
--to=david.g.robboy@intel.com \
--cc=linux-ia64@vger.kernel.org \
/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.