From: "Mark Chambers" <markc@mail.com>
To: "gautam borad" <gautam@eisodus.com>, <linuxppc-embedded@ozlabs.org>
Subject: Re: kernel access of bad area, sig: 11 ( mpc852t)
Date: Tue, 11 Apr 2006 10:39:19 -0400 [thread overview]
Message-ID: <00c201c65d75$b89e0b80$5800000a@CHUCK2> (raw)
In-Reply-To: 443BB7E2.9040903@eisodus.com
> Hi,
> Im having problem porting linux kernel 2.4.21 to our mpc852T custom
> board.The kernel
> panics randomly with sig 11.
> The board boots up fine and we also get to the prompt.When we open 3-4
> telnet sessions
> and try to run some command the kernel panics.This is completely
> random.Sometimes it
> even panics before opening the telnet session.
>
> One of the oops dump is:
>
> -----------------------------------------------------------------------------------------------------------------------------
> Oops: kernel access of bad area, sig: 11
> NIP: C0019FD0 XER: 00000000 LR: C001A06C SP: C1C33AD0 REGS: c1c33a20
> TRAP: 0300 Not tainted
> MSR: 00009032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
> DAR: 725F6578, DSISR: 0000000B
> TASK = c1c32000[48] 'insmod' Last syscall: 5
> last math 00000000 last altivec 00000000
> GPR00: 7361726D C1C33AD0 C1C32000 00000000 C0113678 C0150000 C0150000
> C014B210
> GPR08: C014B210 C012D060 00000000 725F6578 04000024 00000000 00000000
> 00000000
> GPR16: 00000000 00000000 00000000 00000000 00001032 01C33BA0 00000000
> C0000000
> GPR24: C014BE38 C0150000 C0110000 C0110000 C0140000 00000001 00000000
> 00000001
> Call backtrace:
> C001A0C8 C0016174 C0015FEC C0015CC0 C0005E38 C0004668 C1C33D10
> C0004670 C004A380 C003FFD4 C00404D8 C0040AD4 C0040FF8 C00330D8
> C00334AC C000443C 1006EF48 1001FCF0 1002023C 10003A18 100036A0
> 300591AC 00000000
> -----------------------------------------------------------------------------------------------------------------------------
>
> The call trace back is of not much help because it is different on all
> oops.
> We are using u-boot 1-1-3.
>
> Thanks in advance.
>
You almost certainly have SDRAM problems. If you have thoroughly checked
out the
complete address range statically, remember that burst accesses will not
occur until the
cache is turned on, so your problem may be with bursting. But you can also
have severe
problems like a missing address line and linux still run for a few seconds.
Mark Chambers
next prev parent reply other threads:[~2006-04-11 14:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-11 14:06 Oops: kernel access of bad area, sig: 11 ( mpc852t) gautam borad
2006-04-11 14:39 ` Mark Chambers [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-17 11:35 Akshay Mishra
2006-04-19 12:58 Kenneth Poole
2006-04-19 13:45 ` Mark Chambers
2006-04-19 14:33 Rune Torgersen
2006-04-21 15:10 Akshay Mishra
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='00c201c65d75$b89e0b80$5800000a@CHUCK2' \
--to=markc@mail.com \
--cc=gautam@eisodus.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).