All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Vacca <svacca@valcom.com>
To: "LinuxEmbeddedMailList (E-mail)" <linuxppc-embedded@lists.linuxppc.org>
Subject: mpc860 vs. mpc860T
Date: Mon, 14 Jan 2002 14:02:42 -0500	[thread overview]
Message-ID: <01C19D04.235222E0.svacca@valcom.com> (raw)


I have 2 bds., the BD #1 is custom designed and based very
closely on the design of the BD #2.  The main difference
is BD #1 uses an mpc860T and BD #2 uses an mpc860.

Both have 32 Meg DRAM, 50MHz.

I can use the exact same Flash Boot code on each,
and download the exact same Linux kernel and app to each.

BD #2 (mpc860) works perfectly, all the way thru to the app
executing threads, etc.

BD #1 (mpc860T) works up until at various points between when
the kernel initializes itself, and the app execution begins, it gets
exception errors, usually something similar to the following:

  Kernel panic: kernel access of bad area pc c0023634 lr c00235ec
                      address 813F004C tsk kswapd/5
or,

  Kernel panic: ramdisk: request list destroyed

Does anyone know of any differences between the 2 CPU's, other than
the mpc860T's internal FEC section and the MII interface on port D, that
might cause such problems?

Thanks,

Steven

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

             reply	other threads:[~2002-01-14 19:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-14 19:02 Steven Vacca [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-15 13:52 mpc860 vs. mpc860T Steven Vacca
2002-01-15 14:25 Steven Vacca
2002-01-15 17:55 Steven Vacca

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=01C19D04.235222E0.svacca@valcom.com \
    --to=svacca@valcom.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 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.