From: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch] Memory Error Handling Improvement
Date: Fri, 24 Jun 2005 01:12:41 +0000 [thread overview]
Message-ID: <42BB5E09.4020606@jp.fujitsu.com> (raw)
In-Reply-To: <200506231730.j5NHUNa96698484@clink.americas.sgi.com>
Hi Russ,
Russ Anderson wrote:
> void
> -mca_handler_bh(unsigned long paddr)
> +mca_handler_bh(unsigned long paddr, void *iip, unsigned long ipsr)
> {
> - printk(KERN_DEBUG "OS_MCA: process [pid: %d](%s) encounters MCA.\n",
> - current->pid, current->comm);
> + printk(KERN_DEBUG "OS_MCA: process [cpu %d, pid: %d, uid: %d, iip: %p, psr: 0x%lx, paddr: 0x%lx](%s) encounters MCA.\n",
> + smp_processor_id(), current->pid, current->uid, iip, ipsr, paddr, current->
> +comm);
Printing detail would be good.
> + pmsa = (pal_min_state_area_t *)(sal_to_os_handoff_state->pal_min_state | (6ul<<61));
> + if (psr1->cpl != 0 || (pmsa->pmsa_iip >= (unsigned long)&interrupt &&
> + pmsa->pmsa_iip < (unsigned long)&interrupt_pnr)) {
It seems that the latter state just means "this was in early of interrupt."
You shoud also make sure that the interrupt has happen in user context, right?
Thanks,
H.Seto
next prev parent reply other threads:[~2005-06-24 1:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-23 17:30 [patch] Memory Error Handling Improvement Russ Anderson
2005-06-23 17:52 ` David Mosberger
2005-06-23 19:30 ` Russ Anderson
2005-06-23 22:11 ` Andreas Schwab
2005-06-23 22:18 ` David Mosberger
2005-06-23 22:22 ` Russ Anderson
2005-06-23 22:54 ` Andreas Schwab
2005-06-24 1:12 ` Hidetoshi Seto [this message]
2005-06-24 20:11 ` Russ Anderson
2005-06-24 20:18 ` Russ Anderson
2005-06-24 20:36 ` David Mosberger
2005-06-24 21:05 ` Luck, Tony
2005-06-24 21:11 ` David Mosberger
2005-06-24 21:20 ` Luck, Tony
2005-06-24 21:25 ` David Mosberger
2005-06-24 21:31 ` Luck, Tony
2005-06-24 21:36 ` Russ Anderson
2005-06-24 21:36 ` David Mosberger
2005-06-24 21:53 ` David Mosberger
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=42BB5E09.4020606@jp.fujitsu.com \
--to=seto.hidetoshi@jp.fujitsu.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