From: "SIP COP 009" <sipcop009@gmail.com>
To: linuxppc-embedded@ozlabs.org
Cc: sipcop009@gmail.com
Subject: MPC83xx and Gianfar Drive Oops
Date: Mon, 28 Aug 2006 16:33:46 -0700 [thread overview]
Message-ID: <5a4792c00608281633p4921016fn62a6f7cedba9e03@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1830 bytes --]
Folks,
Anyone seen this before ?
We have the MPC8349 based EVM board which has 2 GigEs. IP forwarding is
enabled on the system. The kernel/gianfar is 2.6.11 based.
We were trying to stress the GigE interfaces by sending bidirectional
smartbits traffic.
We observe the following kernel oops:
e-99-0-21-1# Oops: Exception in kernel mode, sig: 5 [#1]
NIP: C016EB80 LR: C016EB80 SP: C0241DE0 REGS: c0241d30 TRAP: 0700
Tainted: P
MSR: 00029032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11 TASK = c022bdb0[0] 'swapper'
THREAD: c0240000 Last syscall: 120
GPR00: C016EB80 C0241DE0 C022BDB0 00000030 C0263BF4 000001A1 DF700060
3B9ACA00
GPR08: C0263BF8 C023DB24 DEA5DE9C C0241CF0 00003C9B 1001A1F8 1FFF8000
00000000
GPR16: FFFFFFFF 00000001 00000000 1FFF297C 1FF9E330 00000001 007FFF00
C0230000
GPR24: 00000001 0000FFFC DFD6B800 0000003F DDC42F48 00000000 D7FA9140
DFD6BA20 Call trace: [c01495d4] [c0149748] [c0176078] [c0018d34]
[c0018e00] [c0005438] [c000460c] [c00038ac] [c00054d0] [c0003928]
[c0242674] [000035fc] Kernel panic - not syncing: Aiee, killing interrupt
handler!
<0>Rebooting in 180 seconds..
After decoding this it looks like the following:
Enter hex value: c01495d4
0xc01495d4:gfar_error(0xc01494bc)+0x118
Enter hex value: c0149748
0xc0149748:gfar_gdrvinfo(0xc0149718)+0x30
Enter hex value: c0176078
0xc0176078:dev_ioctl(0xc0175f0c)+0x16c
Enter hex value: c0018d34
0xc0018d34:__do_softirq(0xc0018cb4)+0x80
Enter hex value: c0018e00
0xc0018e00:do_softirq(0xc0018da8)+0x58
Enter hex value: c0005438
0xc0005438:do_IRQ(0xc00053b4)+0x84
Enter hex value: c000460c
0xc000460c:ret_from_except(0xc000460c)+0x0
Enter hex value: c00038ac
0xc00038ac:ppc6xx_idle(0xc00037c8)+0xe4
Enter hex value: c00054d0
0xc00054d0:cpu_idle(0xc00054a8)+0x28
Any idea on this one ? Any new fixes that went in for such issues ?
Thanks!
ashutosh
[-- Attachment #2: Type: text/html, Size: 2075 bytes --]
next reply other threads:[~2006-08-28 23:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-28 23:33 SIP COP 009 [this message]
2006-08-29 2:12 ` MPC83xx and Gianfar Drive Oops Liu Dave-r63238
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=5a4792c00608281633p4921016fn62a6f7cedba9e03@mail.gmail.com \
--to=sipcop009@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