From: Scott Wood <scottwood@freescale.com>
To: 郭劲 <guojin02@tsinghua.org.cn>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Unable to handle kernel paging request for instruction fetch???
Date: Tue, 01 Apr 2008 12:09:35 -0500 [thread overview]
Message-ID: <47F26C4F.7000204@freescale.com> (raw)
In-Reply-To: <407023539.21267@tsinghua.org.cn>
郭劲 wrote:
> Hi,all,
>
> I run the iperf tool to test the ethernet throughput for my MPC8360E board, after
> about 20 minutes, the exception is happened. Could you tell me why?
>
>
> Unable to handle kernel paging request for instruction fetch
> Faulting instruction address: 0x4e800020
> Oops: Kernel access of bad area, sig: 11 [#1]
> MPC836x MDS
> Modules linked in: encoder mpc_sync k_spi(P)
Can you reproduce it with kallsyms enabled, and without the out-of-tree
module(s)?
> NIP: 4e800020 LR: c01a08d4 CTR: 00000000
Something branched to a bad address from 0xc01a08d0. Can you look up
what line that is in your kernel?
-Scott
prev parent reply other threads:[~2008-04-01 17:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 4:18 Unable to handle kernel paging request for instruction fetch??? 郭劲
2008-04-01 17:09 ` 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=47F26C4F.7000204@freescale.com \
--to=scottwood@freescale.com \
--cc=guojin02@tsinghua.org.cn \
--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).