From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch] 2.6.0-test9 pal/sal/salinfo/mca
Date: Thu, 04 Dec 2003 17:45:01 +0000 [thread overview]
Message-ID: <marc-linux-ia64-107056007816216@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106978478405713@msgid-missing>
On Wednesday 03 December 2003 6:38 pm, Ben Woodard wrote:
> 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.
I believe this is bug #104667 in the Red Hat bugzilla. The patch
should be attached to the bug report. I can't get bugzilla to show
me the report, so I don't know the current status.
> So my question is: should we continue forward with our backport of the
> 2.6 MCA code or is the 2.4 code actually functional enough to support
> our needs and we are missing something in our quick inspection of the
> code.
As Keith mentioned, the current 2.4 and 2.6 MCA code should be
essentially identical.
Bjorn
next prev parent reply other threads:[~2003-12-04 17:45 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
2003-12-04 6:23 ` Stephane Eranian
2003-12-04 17:45 ` Bjorn Helgaas [this message]
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-107056007816216@msgid-missing \
--to=bjorn.helgaas@hp.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.