From: Jim Lewis <jlewis@mvista.com>
To: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Strange behavior on FADS with ICTRL==0
Date: Fri, 08 Oct 1999 21:17:47 -0500 [thread overview]
Message-ID: <37FEA5CA.57808DB3@mvista.com> (raw)
Hello,
I am working with 2.2.5 on a FADS 823. If the ISCT_SER field of the
ICTRL register is set to 0 (which is the value on reset), the system is
very unstable. This field controls whether the core is serialized and
provides options for placing instruction fetches from cache on the
external pins for tracing and debugging purposes. Mainly, I get one of
two errors after init has started:
Panic: Kernel Mode Software FPU Emulation
page fault in interrupt handler
When ISCT_SER is set to 0, the core is fully serialized and all
instruction fetches are shown. On the other hand, if I set the ISCT_SER
to 7 (the recommended "production" value), the core is not serialized
and no fetches are shown. The system is stable with this setting.
Has anyone else experienced anything like this?
Thanks
--
Jim Lewis
Sr. Field Applications Engineer
MontaVista Software, Inc.
(817)261-9088 http://www.mvista.com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~1999-10-09 2:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-09 2:17 Jim Lewis [this message]
1999-10-09 13:17 ` Strange behavior on FADS with ICTRL==0 Dan Malek
1999-10-09 14:05 ` Claude Robitaille
1999-10-09 15:18 ` Jim Lewis
1999-10-14 0:44 ` Enet on FADS Claude Robitaille
1999-10-14 22:59 ` Jim Lewis
1999-10-15 0:48 ` Claude Robitaille
1999-10-18 20:19 ` Dan Malek
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=37FEA5CA.57808DB3@mvista.com \
--to=jlewis@mvista.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).