From: Zoltan Menyhart <Zoltan.Menyhart_AT_bull.net@nospam.org>
To: linux-ia64@vger.kernel.org
Subject: Re: Yet another MCA handler
Date: Thu, 15 Jan 2004 09:09:34 +0000 [thread overview]
Message-ID: <400658CE.23F6D0B4@nospam.org> (raw)
In-Reply-To: <40051D1B.7912DB91@nospam.org>
Russ Anderson wrote:
>
> Zoltan Menyhart wrote:
> >
> > I was to write the code for the recovery for poisoned memory, too,
> > but I've got no way to provoke this kind of error
> > ( I do not really know what it like is :-) )
>
> If you get that far, take the Intel Itanium 2 Processor
> Specification Update (December 2003) errata 78 into account
>
> 78. L2 cache line with poison data results in unexpected fatal MCA
>
> http://www.intel.com/design/itanium2/specupdt/251141.htm
Thanks for the hint, but as far as I can see, it's not what I look for.
This is a fatal MCA. I need something classified as recoverable
(byte 10: ERR_SEVERITY in the SAL log record header).
Zoltan Menyhart
prev parent reply other threads:[~2004-01-15 9:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 10:42 Yet another MCA handler Zoltan Menyhart
2004-01-14 23:30 ` Luck, Tony
2004-01-14 23:32 ` Russ Anderson
2004-01-15 9:09 ` Zoltan Menyhart [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=400658CE.23F6D0B4@nospam.org \
--to=zoltan.menyhart_at_bull.net@nospam.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox