linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollis@austin.ibm.com>
To: "Muaddi, Cecilia" <cecilia.muaddi@alloptic.com>
Cc: "'linuxppc-embedded@lists.linuxppc.org'"
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: BDI-2000
Date: 08 Jan 2003 10:20:33 -0600	[thread overview]
Message-ID: <1042042834.1207.86.camel@granite.austin.ibm.com> (raw)
In-Reply-To: <885489B3B89FB6449F93E525DF78777F064531@srvnt506.ALLOPTIC.COM>


On Tue, 2003-01-07 at 18:40, Muaddi, Cecilia wrote:
>
> BDI>info
>     Target state      : debug mode
>     Debug entry cause : entering check stop state
>     Current PC        : 0x00000220

You seem to have caused a machine check. For clues look at SRR0 and
SRR1, as well as any other registers your CPU sets on machine check (I
don't know 8xx - look in your user manual for information on machine
checks).

-Hollis
--
PowerPC Linux
IBM Linux Technology Center


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2003-01-08 16:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-08  0:40 BDI-2000 Muaddi, Cecilia
2003-01-08  9:23 ` BDI-2000 Marius Groeger
2003-01-08 16:20 ` Hollis Blanchard [this message]
     [not found] <0065D0B7.C21188@alloptic.com>
2003-01-08 11:47 ` BDI-2000 Jerry Van Baren
  -- strict thread matches above, loose matches on Subject: below --
2003-01-08 13:59 BDI-2000 James Don
2003-01-08 14:01 BDI-2000 James Don
     [not found] <DF2B720CF774D21189EE00805FA7FA22051782FD@nmrusdunsx3.nielsenmedia.com>
2003-01-08 17:21 ` BDI-2000 Marius Groeger
2003-01-08 17:44 BDI-2000 Kerl, John
2003-01-08 20:12 BDI-2000 Muaddi, Cecilia
2003-01-09  0:09 ` BDI-2000 Wolfgang Denk
2003-01-09  0:21 BDI-2000 Muaddi, Cecilia
2003-01-09  0:33 ` BDI-2000 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=1042042834.1207.86.camel@granite.austin.ibm.com \
    --to=hollis@austin.ibm.com \
    --cc=cecilia.muaddi@alloptic.com \
    --cc=linuxppc-embedded@lists.linuxppc.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).