From: Jack Steiner <steiner@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Reliably creating MCA on white box Itanium-1
Date: Fri, 04 Jul 2003 01:42:41 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105728333228553@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105721395828393@msgid-missing>
>
> On Thu, 3 Jul 2003 08:27:36 -0500 (CDT),
> Jack Steiner <steiner@sgi.com> wrote:
> >>
> >> Is there a way of reliably creating an MCA on a white box Itanium 1?
> >> B3 processors, firmware is B117A. Failing that, what about creating an
> >> MCA on a white box Itanium-2?
> >>
> >> Loading a duplicate ITC is no good, I need an MCA that actually enters
> >> ia64_mca_ucmc_handler in mca.c. A working example using
> >> PAL_CACHE_WRITE would be nice.
> >
> >
> >Why doesnt loading a duplicate TR (not TC) work for you? I've used that
> >method and found it to be reliable.
>
> Because mca_asm.S does not call the C code for TLB errors. I want to
> test the C code on standard hardware.
Seems to me that a TLB error caused by a duplicate TR dropin *should* call
C code. A MCA caused by a duplicate TR is a software bug that should
panic the system.
I understand that TLB parity errors would be silently corrected in mca_asm.S
by reloading the TLB.
--
Thanks
Jack Steiner (651-683-5302) (vnet 233-5302) steiner@sgi.com
next prev parent reply other threads:[~2003-07-04 1:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-03 6:29 Reliably creating MCA on white box Itanium-1 Keith Owens
2003-07-03 13:27 ` Jack Steiner
2003-07-04 1:26 ` Keith Owens
2003-07-04 1:42 ` Jack Steiner [this message]
2003-07-04 12:56 ` Grant Grundler
2003-07-09 15:27 ` Luck, Tony
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=marc-linux-ia64-105728333228553@msgid-missing \
--to=steiner@sgi.com \
--cc=linux-ia64@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.