From: Dan Malek <dan@netx4.com>
To: Lucinda Schafer <lucsch@adaptivemicro.com>
Cc: linuxppc-embedded@lists.linuxppc.org, cort@cs.nmt.edu,
paulus@cs.anu.edu.au
Subject: Re: Software Emulation Kernel Panic
Date: Mon, 12 Jun 2000 15:43:54 -0400 [thread overview]
Message-ID: <39453D7A.10E9AF8C@embeddededge.com> (raw)
In-Reply-To: A109131318C4D1119AC20060088DECE330F374@amwmail.adaptivemicro.com
Lucinda Schafer wrote:
> On our MPC823-based custom boards, we are experiencing the "Kernel Mode
> Software FPU Emulation" panic
This has little to do with floating point. Nearly all instructions
the processor can't decode are vectored to this function. It assumes
the primary reason you are here is to emulate floating point instructions.
If the function can't decode the instruction as a floating point operation,
it is really something the processor can't execute, so the panic message
spews forth.
> Could you shed some light on some situations where this may happen?
This can be either a software or hardware bug. If it is a software
bug, just unravel the stack backtrace and debug it. It could be a
trashed stack frame, resulting in a bad function return address, or
some indirect function call that was not properly computed.
It could also happen because of a hardware bug while fetching instructions
from memory. Verify the NIP instruction that it tried to decode is
what is really supposed to be at that location in memory. This is
a typical failure when the UPM is not programmed correctly. Since
this is a custom board, have you verified all memory cycles? Disable
the cache and try again, you will probably get a different result.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-06-12 19:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-12 18:16 Software Emulation Kernel Panic Lucinda Schafer
2000-06-12 19:43 ` Dan Malek [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-06-12 19:49 Wohlgemuth, Jason
2000-06-12 20:16 Lucinda Schafer
2000-06-13 0:47 ` Dan Malek
2000-06-13 7:07 ` 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=39453D7A.10E9AF8C@embeddededge.com \
--to=dan@netx4.com \
--cc=cort@cs.nmt.edu \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=lucsch@adaptivemicro.com \
--cc=paulus@cs.anu.edu.au \
/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).