From: "David Bryan" <Dave@ThePTRGroup.com>
To: "Michael R. Zucca" <mrz5149@acm.org>
Cc: "Rudy Klinksiek" <klink@arlut.utexas.edu>,
<linuxppc-dev@lists.linuxppc.org>
Subject: RE: "Illegal instruction" traps on smp clients - 2.4.19
Date: Thu, 27 Feb 2003 15:32:26 -0500 [thread overview]
Message-ID: <NEBBLKDMGLOGOAOIDAIDMEMFEHAA.Dave@ThePTRGroup.com> (raw)
In-Reply-To: <3E5E584E.2020703@acm.org>
Michael,
Certainly, be glad to... however, I would make sure you fully understand
the operation of these bits and their applicability to your system.
On the 7400/7410 the MSSCR0 is accessed as SPR 1014.
At reset, the MSSCR0 is initialized to all 0s.
We OR'd 0x8000 with MSSCR0.
Bit 0 (MSB) controls whether the 7400 runs MEI or MESI coherency protocol.
Setting Bit 0 (SHDEN) causes the 7400 to implement "a 4-state MESI protocol
similar to the MPC604e family of processors". Bit 1 (SHDPEN3) is valid only
in MEI mode, so its value is ignored when SHDEN is set. In this
configuration, the 7400 will drive/sample the SHD/0/1 pins depending on the
bus mode (MPX or 60x).
Dave
David Bryan www.ThePTRGroup.com
----------------------------------------------
-----Original Message-----
From: Michael R. Zucca [mailto:mrz5149@acm.org]
Sent: Thursday, February 27, 2003 1:26 PM
To: David Bryan
Cc: Rudy Klinksiek; linuxppc-dev@lists.linuxppc.org
Subject: Re: "Illegal instruction" traps on smp clients - 2.4.19
David Bryan wrote:
> These modes are controlled by two bits in
> the Memory subsystem control register (MSSCR0). At reset, the MSSCR0
> defaults to MEI mode with the SHD signal disabled. By placing the 7400 in
> MESI mode at boot, we solved the problem.
Would you care to share what MSSCR0 bits these were and what you set
them to? :-)
--
----------------------------------------------
Michael Zucca - mrz5149@acm.org
----------------------------------------------
"I'm too old to use Emacs." -- Rod MacDonald
----------------------------------------------
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-02-27 20:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-27 14:44 "Illegal instruction" traps on smp clients - 2.4.19 Rudy Klinksiek
2003-02-27 15:57 ` Ethan Weinstein
2003-02-27 16:23 ` Benjamin Herrenschmidt
2003-02-27 16:37 ` David Bryan
2003-02-27 18:26 ` Michael R. Zucca
2003-02-27 20:32 ` David Bryan [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=NEBBLKDMGLOGOAOIDAIDMEMFEHAA.Dave@ThePTRGroup.com \
--to=dave@theptrgroup.com \
--cc=klink@arlut.utexas.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mrz5149@acm.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).