Re: Why system panic after sometimes?

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 [ref] you wrote:

quoted

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.

quoted

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?

quoted

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/