From: Scott Wood <scottwood@freescale.com>
To: <Jay_Chen@alphanetworks.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Data Cache Push Parity Error
Date: Mon, 15 Sep 2014 23:23:20 -0500 [thread overview]
Message-ID: <1410841400.24184.494.camel@snotra.buserror.net> (raw)
In-Reply-To: <5538ce4d2de54f2fb7a29a66b33d70b0@HQMBS02.alphanetworks.com>
On Mon, 2014-09-15 at 08:15 +0000, Jay_Chen@alphanetworks.com wrote:
> Hi all,
>
>
>
> I am using P2020 with Linux kernel 3.8.13.
>
> Sometimes my system encounters machine check exception and it shows
> “Caused by (from MCSR=20000000): Data Cache Push Parity Error”.
>
> Could anyone show me some hints to dig into this issue? Any comment is
> welcome.
>
> Thanks in advance.
I suggest contacting Freescale support about this
(support@freescale.com) -- I don't think this is the type of error that
you'd normally see from software misbehavior.
-Scott
prev parent reply other threads:[~2014-09-16 4:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 8:15 Data Cache Push Parity Error Jay_Chen
2014-09-16 4:23 ` Scott Wood [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=1410841400.24184.494.camel@snotra.buserror.net \
--to=scottwood@freescale.com \
--cc=Jay_Chen@alphanetworks.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox