From: Jojy Varghese <jojyv@juniper•net>
To: Scott Wood <scottwood@freescale•com>
Cc: "hongtao.jia@freescale•com" <hongtao.jia@freescale•com>,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
Guenter Roeck <groeck@juniper•net>,
Paul Mackerras <paulus@samba•org>,
"linuxppc-dev@lists•ozlabs.org" <linuxppc-dev@lists•ozlabs.org>,
Guenter Roeck <linux@roeck-us•net>
Subject: Re: [PATCH] powerpc/fsl: Add support for pci(e) machine check exception on E500MC / E5500
Date: Tue, 30 Sep 2014 20:20:03 +0000 [thread overview]
Message-ID: <D0505E5A.10E46%jojyv@juniper.net> (raw)
In-Reply-To: <1412108227.13320.309.camel@snotra.buserror.net>
On 9/30/14 1:17 PM, "Scott Wood" <scottwood@freescale•com> wrote:
>On Tue, 2014-09-30 at 20:15 +0000, Jojy Varghese wrote:
>>=20
>> On 9/30/14 8:50 AM, "Guenter Roeck" <linux@roeck-us•net> wrote:
>>=20
>> >On Mon, Sep 29, 2014 at 06:31:06PM -0500, Scott Wood wrote:
>> >> Which specific chip and revision did you see this on? What is the
>>value
>> >> in MCSR?
>> >>=20
>> >Jojy can answer that, at least for P5020. We have seen it on P5040 as
>> >well,
>> >though, so it is not just limited to one chip/revision.
>>=20
>> The specifics are:
>> PVR: 0x80240012
>> Instruction that causes the MC exception: lwbrx
>> The faulty load address is also present in RB. So we could change the
>> logic to use that
>> instead of DEAR. What I don=B9t know is of there are other cases also
>>which
>> escapes the current logic.
>
>Could you find out what MCSR was when that happened? I'm most
>interested in whether MAV was set, but the other bits would be
>interesting as well.
MCSR=3Da000 ( Load Error Report)
>
>-Scott
>
>
Thanks
Jojy
next prev parent reply other threads:[~2014-09-30 20:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 16:48 [PATCH] powerpc/fsl: Add support for pci(e) machine check exception on E500MC / E5500 Guenter Roeck
2014-09-29 18:36 ` Scott Wood
2014-09-29 19:06 ` Guenter Roeck
2014-09-29 23:03 ` Jojy Varghese
2014-09-29 23:31 ` Scott Wood
2014-09-30 15:50 ` Guenter Roeck
2014-09-30 20:15 ` Jojy Varghese
2014-09-30 20:17 ` Scott Wood
2014-09-30 20:20 ` Jojy Varghese [this message]
2014-10-01 0:43 ` Scott Wood
2014-10-08 3:10 ` Hongtao Jia
2014-10-08 3:08 ` Hongtao Jia
2014-10-08 23:48 ` Scott Wood
2014-10-09 2:18 ` Hongtao Jia
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=D0505E5A.10E46%jojyv@juniper.net \
--to=jojyv@juniper$(echo .)net \
--cc=groeck@juniper$(echo .)net \
--cc=hongtao.jia@freescale$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux@roeck-us$(echo .)net \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=paulus@samba$(echo .)org \
--cc=scottwood@freescale$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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