From: David Vrabel <david.vrabel@citrix.com>
To: "Zhang, Yang Z" <yang.z.zhang@intel.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Daniel Kiper <dkiper@net-space.pl>
Subject: Re: kexec and kdump on Xen??
Date: Thu, 17 Apr 2014 11:01:31 +0100 [thread overview]
Message-ID: <534FA67B.2010805@citrix.com> (raw)
In-Reply-To: <A9667DDFB95DB7438FA9D7D576C3D87E0AA96B00@SHSMSX104.ccr.corp.intel.com>
On 17/04/14 02:19, Zhang, Yang Z wrote:
>
> After investigation, I found some bugs (One is the segment overlap
> check failure and another one is related to x2apic). With some
> workarounds, now I am able to kexec from Xen into Linux. But it still
> fails to run kdump(Xen->linux). I add some debug messages in the key
> code path. It shows kexec_reloc() will cause machine reboot. Is it a
> known issue?
Rebooting after the kexec_reloc() call could be triggered from Xen,
purgatory or the kernel.
Can you turn on purgatory debug output (--console-serial
--serial-baud=115200 options to kexec for serial) and earlyprintk in the
kernel?
You may also want to specify a crashregion location. e.g., we use the
Xen option "crashkernel=128M@32M".
David
next prev parent reply other threads:[~2014-04-17 10:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 3:38 kexec and kdump on Xen？ Zhang, Yang Z
2014-04-14 8:11 ` kexec and kdump on Xen?? Daniel Kiper
2014-04-14 8:15 ` Zhang, Yang Z
2014-04-14 13:26 ` Daniel Kiper
2014-04-15 2:13 ` Zhang, Yang Z
2014-04-16 11:10 ` Daniel Kiper
2014-04-17 1:19 ` Zhang, Yang Z
2014-04-17 9:50 ` Andrew Cooper
2014-04-18 1:45 ` Zhang, Yang Z
2014-04-18 12:50 ` Don Slutz
2014-04-18 16:26 ` Andrew Cooper
2014-04-17 10:01 ` David Vrabel [this message]
2014-04-22 10:14 ` David Vrabel
2014-04-15 6:57 ` Zhang, Yang Z
2014-04-14 9:51 ` kexec and kdump on Xen？ David Vrabel
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=534FA67B.2010805@citrix.com \
--to=david.vrabel@citrix.com \
--cc=dkiper@net-space.pl \
--cc=xen-devel@lists.xen.org \
--cc=yang.z.zhang@intel.com \
/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.