From: Shawn Jin <shawnxjin@gmail.com>
To: ppcembed <linuxppc-embedded@ozlabs.org>
Subject: Machine check - D-Cache search parity error occurs on a ppc440 core
Date: Wed, 31 Aug 2005 18:49:31 -0700 [thread overview]
Message-ID: <c3d0340b0508311849654fcdad@mail.gmail.com> (raw)
Hi,
When the kernel starts /sbin/init, a machine check occurs showing it's
a d-cache search parity error. The CPU is a ppc440 core.
What usually causes this kind of exception? The user's manual of 440
core lists three possible situation where such an exception will
occur.
1) Multi-hit parity error on any instr that does a CAM lookup
2) Tag or data parity errors on load instr
3) Tag parity erros on dcbf, dcbi, dcbst instr
Both 1) and 3) are excluded in this case because the internal cpu core
signals show dcrTagEvenSearchParityError is set. Why did this error
happen? It's a cpu bug?
Anyone has seen this error before? Please share your experience.
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 72k init
Machine check in kernel mode.
D-Cache Search Parity Error
Oops: machine check, sig: 7 [#1]
NIP: C0000D20 LR: 30001BA8 SP: 7FFFFC80 REGS: c00e5f50 TRAP: 0202 Not ta=
inted
MSR: 00021000 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 00
TASK =3D c016cab0[1] 'init' THREAD: c1fca000
Last syscall: 11=20
GPR00: 00000001 7FFFFC80 00000000 00000000 AAAA0000 30025160 30024B18 00000=
DF8=20
GPR08: 30024B80 0000012A 0000037E 30000AC8 00000254 00000000 02004D00 00000=
000=20
GPR16: 00000000 00000001 FFFFFFFF 01FFDF58 00000000 007FFF00 00000003 7FFFF=
F10=20
GPR24: 00000002 7FFFFC90 300002C4 7FFFFC88 3000195C 30000000 C00011C8 30001=
8C0=20
NIP [c0000d20] DataTLBError+0x0/0xa0
LR [30001ba8] 0x30001ba8
Kernel panic - not syncing: Attempted to kill init!
Best regards,
-Shawn.
reply other threads:[~2005-09-01 1:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=c3d0340b0508311849654fcdad@mail.gmail.com \
--to=shawnxjin@gmail.com \
--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 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).