From: Dan Malek <dan@netx4.com>
To: Steve Tarr <tarr@lucent.com>
Cc: LINUX-PPC <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Motorola MPC8260-ADS Boot hassel
Date: Thu, 01 Jun 2000 19:25:38 -0400 [thread overview]
Message-ID: <3936F0F2.DDA90328@embeddededge.com> (raw)
In-Reply-To: 3936790D.9BD7680E@lucent.com
Steve Tarr wrote:
I haven't tried ramdisks recently......
> RAMDISK: Compressed image found at block 0
> NIP: C0010D90 XER: 20000000 LR: C0010D8C REGS: c085f260 TRAP: 0300
What function is this (0xc0010d90)? It is hard to help without some
basic information like this.
> GPR08: C085E000 C0008540 00000000 C085F358 00000000 FFFFFFFF 00000000
> 00000400
> Kernel panic: kernel access of bad area pc c0010d90 lr c0010d8c address
> 3C tsk 1Rebooting in 180 seconds..
>
> Based on my simple attempts it appears that I am taking a DSI exception
> on an access to
> 0xC010000......
How did you determine this? The panic message prints the faulting
address, which happens to be 0x3c. GPR8, 9, 10, 11, and 12 are typical
sources for intermediate pointers, two of those are zero. I would
guess a NULL pointer to a data structure trying to access the contents
at offset 0x3c.
> I noticed in System.map that data does not the first data entry.....
Next time notice and tell us the function at NIP....much more useful.
> Note: they put the SUNI-Lite and board registers at
> 0x04500000-0x04700000.
Who is they, what's a SUNI-Lite, and does it matter? Best of all,
if you don't like the address you can change it.
We need more info.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-06-01 23:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-01 14:54 Motorola MPC8260-ADS Boot hassel Steve Tarr
2000-06-01 23:25 ` Dan Malek [this message]
2000-06-01 18:02 ` Steve Tarr
2000-06-02 0:49 ` Dan Malek
2000-06-02 4:29 ` Murray Jensen
2000-06-02 14:06 ` Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2000-06-02 21:13 Steve Tarr
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=3936F0F2.DDA90328@embeddededge.com \
--to=dan@netx4.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=tarr@lucent.com \
/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).