From: "David N. Lombard" <dnlombar@ichips.intel.com>
To: Jack Steiner <steiner@sgi.com>
Cc: "Siddha, Suresh B" <suresh.b.siddha@intel.com>,
"gleb@redhat.com" <gleb@redhat.com>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
"ebiederm@xmission.com" <ebiederm@xmission.com>,
"mingo@elte.hu" <mingo@elte.hu>,
"tglx@linutronix.de" <tglx@linutronix.de>
Subject: Re: kdump/kexec on EFI-enabled x2apic platforms
Date: Wed, 31 Mar 2010 15:24:50 -0700 [thread overview]
Message-ID: <20100331222449.GB8257@nlxcldnl2.cl.intel.com> (raw)
In-Reply-To: <20100329200104.GA23760@sgi.com>
On Mon, Mar 29, 2010 at 01:01:04PM -0700, Jack Steiner wrote:
> All -
>
> I just started debugging kdump/kexec on our UV platform and
> have run into some problems. I suspect others have encountered these
> same or similar problems. Any help would be appreciated.
>
>
>
> Our platform uses EFI boot. It is Nehalem based & has a large number of cpus.
> The BIOS enables x2apic mode and the kernel runs with interrupt remapping enabled.
> Note that some apicids have more than 8 bits - x2apic mode is required.
What are you using as a boot loader? I've tested kexec with elilo 3.8 and
got good results. But, that was early last year, so I'll need to try it out
with production hardware and the current firmware and sw stack. I'll try to
get to that this week, and let you know the results.
--
David N. Lombard, Intel, Irvine, CA
I do not speak for Intel Corporation; all comments are strictly my own.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2010-03-31 22:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 20:01 kdump/kexec on EFI-enabled x2apic platforms Jack Steiner
2010-03-29 22:13 ` Eric W. Biederman
2010-03-30 17:59 ` Jack Steiner
2010-03-31 22:24 ` David N. Lombard [this message]
2010-04-01 0:47 ` Jack Steiner
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=20100331222449.GB8257@nlxcldnl2.cl.intel.com \
--to=dnlombar@ichips.intel.com \
--cc=ebiederm@xmission.com \
--cc=gleb@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=mingo@elte.hu \
--cc=steiner@sgi.com \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
/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.