From: Wolfgang Denk <wd@denx.de>
To: "Sebastian Theiss" <st12@inf.tu-dresden.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: pthread / TQM5200 problem
Date: Sat, 02 Feb 2008 05:24:24 +0100 [thread overview]
Message-ID: <20080202042424.8E6AA247A1@gemini.denx.de> (raw)
In-Reply-To: Your message of "Fri, 01 Feb 2008 13:47:45 +0100." <002c01c864d0$a4ad11c0$0101a8c0@tis>
In message <002c01c864d0$a4ad11c0$0101a8c0@tis> you wrote:
>
> I've been having some headache using the pthread library with a TB5200 box
> (based on a TQM5200 board with a Freescale MPC5200 PowerPC-CPU). I created a
> small program to pin down the problem and it runs fine on all my Unix- and
NOTE: It is really bad behaviour to post the same question indepen-
dently in several mailing list. Your question has already been
answered on the ELDK list.
> Linux-machines but fails on the embedded box: The program contains a class
> CSignal that provides thread-synchronisation based on the
> pthread_cond_signal and pthread_cond_wait calls and takes care of the
> "spurious wakeup" and "lost signal" problems. The program runs 159
> additional threads (that seems to be some internal limit), each of them
And this strange "internal limit" is an indication that you are
running code that is more than 1.5 years old, as the bug was fixed in
September 2006. It was caused by bad PCI mappings that overlap with
CONFIG_TASKSIZE.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
It would seem that evil retreats when forcibly confronted
-- Yarnek of Excalbia, "The Savage Curtain", stardate 5906.5
prev parent reply other threads:[~2008-02-02 4:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 12:47 pthread / TQM5200 problem Sebastian Theiss
2008-02-01 14:56 ` Sebastian Theiss
2008-02-01 15:17 ` Grant Likely
2008-02-02 4:24 ` Wolfgang Denk [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=20080202042424.8E6AA247A1@gemini.denx.de \
--to=wd@denx.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=st12@inf.tu-dresden.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).