From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Li.Wang" <Li.Wang@windriver.com>
Cc: "Xiong, Wei" <Wei.Xiong@windriver.com>,
Lans Zhang <jia.zhang@windriver.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: Help about Freescale p2020ds problem under cpu load test
Date: Mon, 29 Mar 2010 17:24:15 +1100 [thread overview]
Message-ID: <1269843855.7101.7.camel@pasglop> (raw)
In-Reply-To: <4BB02886.2010307@windriver.com>
On Mon, 2010-03-29 at 12:11 +0800, Li.Wang wrote:
> Hi Benjamin Herrenschmidt,
Well, I'm sure you'll have more chance with this one asking somebody
from Freescale :-)
It does look like there may be a coherency problem but I don't know
those chips well enough to tell
Cheers,
Ben.
> I use Freescale p2020ds board and kernel linux 2.6.33.
> Under cpu load test which test case is in attachment
> (#./cpu_load_multi.sh 500),
> the follow issues happen after a long time:
> =======================
> find: md5sum terminated by signal 6
>
> find: md5sum terminated by signal 11
> =======================
>
> If use kernel linux 2.6.27(porting p2020ds bsp to it), it's easy to
> reproduce the issue:
> =======================
> find: ../nptl/sysdeps/unix/sysv/linux/powerpc/../i386/../fork.c:138:
> __libc_fork: Assertion `((void)(self), (((struct pthread *)
> (__thread_register - 0x7000 - (sizeof (struct pthread) + ((sizeof
> (tcbhead_t) + __alignof__ (struct pthread) - 1)& ~(__alignof__ (struct
> pthread) - 1))))))->tid) != ppid' failed.
>
> find: md5sum terminated by signal 6
>
> find: md5sum terminated by signal 11
>
> ./cpu_load.sh: line 6: 7944 Segmentation fault find /usr -type f
> -exec md5sum {} \;> /dev/null
> =======================
>
> If turn off CONFIG_SMP, the issue disappear.
>
> If use Freescale 8572ds board, the issue disappear, too.
> I know the two board is same about cpu(e500v2), but their version have a
> little difference:
> ===================
> fsl_8572ds:
> cpu : e500v2
> revision : 3.0 (pvr 8021 0030)
>
> fsl_p2020ds:
> cpu : e500v2
> revision : 4.0 (pvr 8021 1040)
> ===================
>
> Please help me to check the problem.
> Thanks,
> LiWang.
prev parent reply other threads:[~2010-03-29 6:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 4:11 Help about Freescale p2020ds problem under cpu load test Li.Wang
2010-03-29 6:24 ` Benjamin Herrenschmidt [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=1269843855.7101.7.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=Li.Wang@windriver.com \
--cc=Wei.Xiong@windriver.com \
--cc=jia.zhang@windriver.com \
--cc=linuxppc-dev@lists.ozlabs.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.