From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch] 2.6.0-test9 pal/sal/salinfo/mca
Date: Thu, 04 Dec 2003 02:05:18 +0000 [thread overview]
Message-ID: <marc-linux-ia64-107050354326437@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106978478405713@msgid-missing>
On 03 Dec 2003 17:38:19 -0800,
Ben Woodard <woodard@redhat.com> wrote:
>On Tue, 2003-11-25 at 00:37, Keith Owens wrote:
>> Forward port the recent changes to pal.h, sal.h, mca.h, salinfo.c and
>> mca.c from 2.4.23-rc2 to 2.6.0-test9.
>>
>> This converts 2.6 to use salinfo instead of printing CMC/CPE/MCA/INIT
>> records in the kernel. It makes the two kernel versions as close
>> together as possible.
>
>I'd like to inquire a bit more into the state of MCA in 2.4 and 2.6. We
>are assembling a 1000 node ia64 cluster out of intel Tiger 4 servers and
>we want to make sure that MCA works well enough that we can at least get
>a good count of the ECC SBE's and panic if we get a MBE.
>
>We are currently basing our kernel off of the Red Hat Enterprise Linux 3
>kernel and we discovered that the implementation of MCA included with it
>does not work for us. The most obvious problem is that it never calls
>ia64_sal_clear_state_info after fetching a SAL record. Thus the CPE
>reasserts itself and the machine effectively locks up infinitely
>printing out the same CPE to the console.
2.4.23 ia64 BK tree has these lines in ia64_mca_log_sal_error_record().
salinfo_log_wakeup(sal_info_type, buffer, size);
platform_err = ia64_log_print(sal_info_type, (prfunc_t)printk);
/* Clear logs from corrected errors in case there's no user-level logger */
if (sal_info_type = SAL_INFO_TYPE_CPE || sal_info_type = SAL_INFO_TYPE_CMC)
ia64_sal_clear_state_info(sal_info_type);
so you should be clearing CPE records immediately. AS 3.0 is probably
out of date in its MCA handling.
>So what we are trying to do is improve the state of the MCA handling in
>our kernel. I managed a backport of the MCA code from 2.6.0-test9 to 2.4
>and it works much better. However, there are a couple of problems with
>it that could probably be sorted out by someone who understands the code
>better. Keith your message sort of hints that the possibility that the
>2.4 kernel's MCA code is further advanced than the 2.6 code.
With my 2.6 patch of 2003-11-25, 2.4 and 2.6 MCA handling is the same,
and it works for CPE. Grab these files from ia64 2.4 BK and merge them
with the AS 3.0 files, if there is ay doubt, use the ia64 2.4 BK
version.
include/asm-ia64/sal.h
include/asm-ia64/pal.h
include/asm-ia64/mca.h
arch/ia64/Kconfig
arch/ia64/kernel/Makefile
arch/ia64/kernel/salinfo.c
arch/ia64/kernel/mca.c
next prev parent reply other threads:[~2003-12-04 2:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-25 18:20 [patch] 2.6.0-test9 pal/sal/salinfo/mca David Mosberger
2003-11-25 22:06 ` Keith Owens
2003-12-04 1:38 ` Ben Woodard
2003-12-04 2:05 ` Keith Owens [this message]
2003-12-04 6:23 ` Stephane Eranian
2003-12-04 17:45 ` Bjorn Helgaas
2003-12-04 19:44 ` Luck, Tony
2003-12-04 20:05 ` Bjorn Helgaas
-- strict thread matches above, loose matches on Subject: below --
2003-11-25 8:37 Keith Owens
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-107050354326437@msgid-missing \
--to=kaos@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox