From: Kumar Gala <kumar.gala@freescale.com>
To: "Clemens Koller" <clemens.koller@anagramm.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Instruction Cache Parity Error / 2.6.10 on MPC8540
Date: Thu, 20 Jan 2005 09:31:39 -0600 [thread overview]
Message-ID: <611DB920-6AF8-11D9-A0BF-000393DBC2E8@freescale.com> (raw)
In-Reply-To: <41EF94DB.4090604@anagramm.de>
Clemens,
I dont think there is really and debug to do with this. If this is=20
happening consistently it suppose to be an faulty part. What rev of=20
the silicon do you have (PVR, SVR)?
- kumar
On Jan 20, 2005, at 5:24 AM, Clemens Koller wrote:
> Hello,
>
> Well, I made good progress with Kernel 2.6.10 on my target (PM854,
> Microsys) which is very similar to the MPC8540_ads configuration.
> But now, after working for several minutes, I ran into the following
> Oops:
>
> -----8<-------------------------------------------------------------
> root@PM854:~/openssh-3.9p1$ Machine check in kernel mode.
> Caused by (from MCSR=3D40000000): Instruction Cache Parity Error
> Oops: machine check, sig: 7 [#1]
> PREEMPT
> NIP: C00054F8 LR: C01F8348 SP: C0263E70 REGS: c0232f50 TRAP: 0202=A0=A0=
=A0=20
> Not
> tainted
> MSR: 00021000 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 00
> TASK =3D c0233720[0] 'swapper' THREAD: c0262000
> Last syscall: 120
> GPR00: C01F8348 C0263E70 C0233720 C0233720 C054C400 00000000 00000351
> 00000000
> GPR08: 00000000 00000003 C054C400 0000473A 0000AE53 00000000 10000700
> 007FFF93
> GPR16: 00000000 00000001 007FFF00 C02B0000 C02C0000 C0233884 3B9ACA00
> C02B5C78
> GPR24: 000000F4 C02B5C78 C0233720 C054C400 C02AED00 00000000 00000000
> C0263E90
> NIP [c00054f8] __switch_to+0x14/0x9c
> LR [c01f8348] schedule+0x318/0x704
> Call trace:
> =A0 [c01f8348] schedule+0x318/0x704
> =A0 [c00026c8] resume_kernel+0x38/0x5c
> =A0 [c00039f8] cpu_idle+0x28/0x40
> =A0 [c0001afc] rest_init+0x28/0x38
> =A0 [c0264804] start_kernel+0x16c/0x1a4
> =A0 [c0000364] skpinv+0x294/0x2d0
> Kernel panic - not syncing: Attempted to kill the idle task!
> =A0 <0>Rebooting in 180 seconds..
> -----8<-------------------------------------------------------------
>
> Does this look familiar to anybody? Any ideas where to start
> debugging?
>
> Best greets,
>
> Clemens Koller
> _______________________________
> R&D Imaging Devices
> Anagramm GmbH
> Rupert-Mayer-Str. 45/1
> 81379 Muenchen
> Germany
>
> http://www.anagramm.de
> Phone: +49-89-741518-50
> Fax: +49-89-741518-19
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
next prev parent reply other threads:[~2005-01-20 15:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-20 11:24 Instruction Cache Parity Error / 2.6.10 on MPC8540 Clemens Koller
2005-01-20 15:31 ` Kumar Gala [this message]
2005-01-20 17:03 ` Clemens Koller
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=611DB920-6AF8-11D9-A0BF-000393DBC2E8@freescale.com \
--to=kumar.gala@freescale.com \
--cc=clemens.koller@anagramm.de \
--cc=linuxppc-embedded@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.