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 20:49:57 -0400 [thread overview]
Message-ID: <393704B5.6B809CE6@embeddededge.com> (raw)
In-Reply-To: 3936A547.7C34A0BF@lucent.com
Steve Tarr wrote:
>
> Sorry for the confusion. I am not familiar with the
> Linux PANIC messages.
You will be soon :-).
> 1. NIP 0xC0010D90 is in wake_up_process()
> 3. Disasembling sched.o gave me a file offset of 0x1dc0 for
> wake_up_process(). The failing
Thanks, this was good and it all makes sense now......
> 1dd4: 7c 7e 1b 78 mr r30,r3
> >> 1e00: 81 3e 00 3c lwz r9,60(r30)
> Note: r30 is loaded from the paramenter passed in, r3.
Yep.
> 4. I made a seemingly foolish assumption that the TRAP: 0300
> was the exception vector. Hence that it was a DSI exception.
Not foolish, that's correct.
> Looking at the register dump shows r30 = 0xc0100000. Hence
> my question.
Mistake. R30 is zero. Null pointer. Decimal 60 is the offset 0x3c.
The wake_up_process() was passed a NULL task pointer. Track it down
through the stack backtrace.
> 5. The SUNI-lite is an SDH/ATM framer for the Fiber that uses FCC2.
Cool. That shouldn't be causing any trouble at this point.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-06-02 0:49 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
2000-06-01 18:02 ` Steve Tarr
2000-06-02 0:49 ` Dan Malek [this message]
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=393704B5.6B809CE6@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.