From: Jerry Van Baren <vanbaren_gerald@si.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Why system panic after sometimes?
Date: Fri, 10 May 2002 07:53:14 -0400 [thread overview]
Message-ID: <5.1.0.14.2.20020510074516.0229ffe8@falcon.si.com> (raw)
In-Reply-To: <20020510113725.CF7FB1195C@denx.denx.de>
Sorry to be replying to a reply, but I inadvertently deleted the first one
in this thread...
A panic due to a FPM emulation trap is almost always a memory read
problem. Your processor is erroneously reading the value 0xFFxxxxxx, which
is a floating point instruction. This causes a floating point emulation
trap to occur because your 8xx processor doesn't have hardware floating point.
Your memory subsystem is not stable. Check the usual suspects: burst cache
line reading with marginal UPM parameters is #1, #2, and #3. I would guess
that a board design problem is #4 and bad memory is #5. Since you run for
longer periods of time, burst cache line reading is less likely in your
case (this usually shows up right away, during the boot process of linux).
Good luck, you are going to need it :-(
gvb
At 01:37 PM 5/10/2002 +0200, Wolfgang Denk wrote:
>Hello,
>
>in message <20020510095821.44488.qmail@web15005.mail.bjs.yahoo.com> you wrote:
> >
> > I am sorry i have not described clear.
> > We use HardHat CDK1.2's cross compile.
>
>This is pretty old, but should work for this purpose.
>
> > We have not use USB driver yet, I have writed a driver
> > for a MPEGI coder chip (operate it via data and
> > address bus).I think my driver (just handle interrupts
> > from chip) is safe and will not affect kernel
>
>Well, I think the kernel version you are using is very stable, so
>maybe it _is_ a problem in your driver?
>
> > and i don't know how to decode backtrace?
>
>See Documentation/oops-tracing.txt in youir LInux kernel source
>directory; alternatively, look up the addresses / symbols manually in
>the Systems.map file in your kernel directory.
>
>Wolfgang Denk
>
>--
>Software Engineering: Embedded and Realtime Systems, Embedded Linux
>Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
>You got to learn three things. What's real, what's not real, and
>what's the difference." - Terry Pratchett, _Witches Abroad_
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-05-10 11:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-10 3:18 Why system panic after sometimes? Dross Zhou
2002-05-10 6:43 ` Wolfgang Denk
2002-05-10 9:58 ` Dross Zhou
2002-05-10 11:37 ` Wolfgang Denk
2002-05-10 11:53 ` Jerry Van Baren [this message]
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=5.1.0.14.2.20020510074516.0229ffe8@falcon.si.com \
--to=vanbaren_gerald@si.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).