All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Walle <bwalle@suse.de>
To: kexec@lists.infradead.org
Cc: jlan@sgi.com
Subject: Re: IA64: copying /proc/vmcore caused kernel MCA'ed
Date: Tue, 9 Sep 2008 18:22:56 +0200	[thread overview]
Message-ID: <20080909182256.5229dee0@kepler.site> (raw)
In-Reply-To: <48C69E4C.2020805@sgi.com>

* Jay Lan <jlan@sgi.com> [2008-09-09]: 
> 
> I talked to Jack Steiner about this problem. He said:
>   The memory at 0xe000006000100000 is part of Altix "fetchop" space
>   (AKA mspec). The memory supports only uncached attributes. A normal
>   "cached" access may cause MCAs.
> 
>   The kernel should not be using this memory for anything. Only the
>   fetchop driver is suppose to access this area.
> 
>   Note: /proc/iomem shows the memory as "System RAM" but that does NOT
>   mean that is can be accessed w/o special code. See efi.c for the
> code that prints the iomem info. Maybe efi.c needs to be changed to
> show a different name for the fetchop memory so that kdump will work.

If it's necessary to register that as "System RAM", then one could
register some special resource as child (like "Kernel text" is done)
and exclude that in kexec (like the reserved area is already excluded
when building the ELF core headers). I think that would be actually the
way to go here without breaking backward compatibility. Of course, you
need to update kexec-tools.


Bernhard

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

      reply	other threads:[~2008-09-09 16:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-08 18:30 IA64: copying /proc/vmcore caused kernel MCA'ed Jay Lan
2008-09-09  8:19 ` Bernhard Walle
2008-09-09 16:03   ` Jay Lan
2008-09-09 16:22     ` Bernhard Walle [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=20080909182256.5229dee0@kepler.site \
    --to=bwalle@suse.de \
    --cc=jlan@sgi.com \
    --cc=kexec@lists.infradead.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.