public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Will Haines <will.haines@embedded-sys.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: Kernel Panic
Date: Tue, 19 Jul 2005 16:34:56 +0000 (UTC)	[thread overview]
Message-ID: <loom.20050719T182347-661@post.gmane.org> (raw)
In-Reply-To: 20050718215238.C2CA43525B0@atlas.denx.de

Wolfgang Denk <wd <at> denx.de> writes:

> 
> Sounds like a memory probem to me. Are you absolutely sure  that  the
> kernel  sees  the  correct  size  of  your RAM, and that all of it is
> actually working, without any gaps or overlaps or mirroring?
> 

If you mean the UPM RAM words, my setup perfectly matches the table in the
manual.  Also, I have 64 Mb of ram, and u-boot recognizes it as such.  As 
for all of it working, I am going to run the u-boot memory test on the whole 
thing to see if there are any problems.  Do you have any other suggestions 
that might make it more apparent if my memory is not correct?

> 
> It may have to do  with  U-Boot,  more  precisely  with  your  memory
> initialization.
> 

Am I right in saying that the following problem is indicative of a memory
problem?  When I plugged the BDI into the board in an attempt to figure out
where the problem occured exactly, I got the following output:

...

VFS: Mounted root (ext2 filesystem).
Oops: Kernel Mode Software FPU Emulation, sig: 8
NIP: C0048000 XER: 20000000 LR: C0048224 SP: C3A25E30 REGS: c3a25d80 
TRAP: 1000    Not tainted
MSR: 00009032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
TASK = c3a24000[1] 'swapper' Last syscall: 6
last math 00000000 last altivec 00000000
GPR00: 00000000 C3A25E30 C3A24000 C3A15960 C3A15960 C00FE4CC 00000000 
C3BEB1A8
GPR08: C3A30580 00000000 C3A15970 C3A15970 22008082 00000000 03FFE000 
00000001
GPR16: 007FFF40 00000000 00000001 007FFF00 03FF8B5C FFFFFFFF 00000000 
03BCF308
GPR24: 00000000 C3A25F60 C00FE4CC C0110000 C3A306D0 C0111314 C3A1B800 
C3A15960
Call backtrace:
C3BEC5D0 C0065DC8 C0045BBC C00360A0 C0036758 C00367D0 C004AAC0
C004AE38 C011DF84 C00026A0 C0002280 C0006B60
Kernel panic: Attempted to kill init!
 <0>Rebooting in 180 seconds..

I read in the FAQ that memory misconfigured PowerPCs tend to have floating 
point exceptions.  I am not able to look at the memory indicated in the call
backtrace without killing the board.  Is there some other way to better
understand this backtrace?

I am starting to be convinced that somehow to SDRAM is not initialized
correctly, but past the UPM RAM words and writing the MAR and MCR, I am not 
sure what else has to be done to initialize it correctly.  Any guidance 
would be greatly appreciated.  I'm very new to this, and your help has
been invaluable.

Thanks again,
Will Haines

  reply	other threads:[~2005-07-19 16:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-18 18:12 [U-Boot-Users] Kernel Panic Will Haines
2005-07-18 19:23 ` [U-Boot-Users] " Will Haines
2005-07-18 20:32 ` [U-Boot-Users] " Wolfgang Denk
2005-07-18 21:03   ` [U-Boot-Users] U-boot and linux at91rm9200 CG
2005-07-18 21:49     ` Wolfgang Denk
2005-07-19  7:16       ` Steven Scholz
2005-07-18 21:12   ` [U-Boot-Users] Re: Kernel Panic Will Haines
2005-07-18 21:52     ` Wolfgang Denk
2005-07-19 16:34       ` Will Haines [this message]
2005-07-19 16:51         ` Wolfgang Denk

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=loom.20050719T182347-661@post.gmane.org \
    --to=will.haines@embedded-sys.com \
    --cc=u-boot@lists.denx.de \
    /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