From: Dan Malek <dan@netx4.com>
To: Pavel Roskin <pavel_roskin@geocities.com>
Cc: "Wohlgemuth, Jason" <jason_wohlgemuth@gilbarco.com>,
"'linuxppc-embedded@lists.linuxppc.org'"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Software Emulation Exception...
Date: Fri, 07 Apr 2000 11:44:39 -0400 [thread overview]
Message-ID: <38EE0267.FB881499@embeddededge.com> (raw)
In-Reply-To: Pine.LNX.4.21.0004071011570.19406-100000@sunapee.transcept.com
> > "Software Emulation %s/%d NIP: %lx *NIP: 0x%x code: %x"
So, decode the address/instruction and see if it makes sense.
> The problem has gone after upgrading to the Montavista kernel (from their
> CDK 1.0)
Since I know something about both of your custom board designs, I
can say that the software is unlikely to be the trouble, although it
could affect the problem. This exception is typical of custom designs
that haven't properly designed the external device interfaces to the
8xx bus. I strongly suspect one of the external devices isn't working
correctly, and when the processor is executing code from DRAM it gets
some trash from the bus instead of the proper instruction. After
something like this occurs, dump the memory at this address and check
to make sure what the processor claims to have executed is really there.
> However, I have no idea what caused the problem and whether it has been
> fixed.
If you haven't attached a logic analyzer, tripped the error, and verified
the bus timing you will never know what caused it. Things like this
don't fix themselves :-).
These problems are sensitive to the instruction stream (the instruction
pointer, the instruction itself, and access to the device). Moving the
code around may appear to "fix" the problem, but it is still there
waiting to happen once the product is shipping......
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-04-07 15:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-07 13:54 Software Emulation Exception Wohlgemuth, Jason
2000-04-07 15:20 ` Pavel Roskin
2000-04-07 15:44 ` Dan Malek [this message]
2000-04-10 9:37 ` Marcus Sundberg
2000-04-10 16:26 ` Dan Malek
2000-04-11 2:36 ` Jeff Millar
2000-04-11 2:03 ` Dan Malek
2000-04-11 8:50 ` Marcus Sundberg
2000-04-11 12:08 ` Dan Malek
2000-04-11 14:51 ` Marcus Sundberg
2000-04-10 3:14 ` Unpacking the mvista kernel RPMs Graham Stoney
2000-04-10 3:25 ` Jason Wohlgemuth
2000-04-10 4:50 ` Graham Stoney
2000-04-10 17:47 ` Pavel Roskin
2000-04-10 16:18 ` Joe Green
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=38EE0267.FB881499@embeddededge.com \
--to=dan@netx4.com \
--cc=jason_wohlgemuth@gilbarco.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=pavel_roskin@geocities.com \
/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).