From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Keir Fraser <keir@xen.org>, xen-devel <xen-devel@lists.xen.org>,
Jacob Shin <Jacob.Shin@amd.com>,
Sherry Hurwitz <sherry.hurwitz@amd.com>
Subject: Re: x86/AMD: Nested hvm crashes in 4.3
Date: Thu, 27 Jun 2013 05:24:44 -0500 [thread overview]
Message-ID: <51CC12EC.7050608@amd.com> (raw)
In-Reply-To: <51CC2B2702000078000E1178@nat28.tlf.novell.com>
On 6/27/2013 5:08 AM, Jan Beulich wrote:
>>>> On 27.06.13 at 11:20, Suravee Suthikulpanit <suravee.suthikulpanit@amd.com> wrote:
>> On 6/27/2013 3:22 AM, Jan Beulich wrote:
>>>>>> On 27.06.13 at 02:24, Suravee Suthikulanit <suravee.suthikulpanit@amd.com> wrote:
>>>> I have found an issue in where the system crash right when I start
>>>> another HVM guest inside an HVM guest. I have traced back to the patch
>>>> which the issue started.
>>>>
>>>> commit f1bde87fc08ce8c818a1640a8fe4765d48923091
>>>> Author: Jan Beulich <jbeulich@suse.com>
>>>> Date: Fri Feb 8 11:06:04 2013 +0100
>>>>
>>>> x86: debugging code for testing 16Tb support on smaller memory systems
>>>>
>>>> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>>>> Acked-by: Keir Fraser <keir@xen.org>
>>> We had issues exposed by this patch before, but any such issue
>>> would just have been masked before that patch (and would
>>> surface on a system with more than 5Tb of memory anyway).
>> The system I am having the issue has 48GB of memory.
> Which is why you're seeing the problem only with the debugging
> code enabled.
Is the "debugging" enabled by default? I didn't specify any debug when
building.
How can I check and disable debugging?
> (And of course I didn't really expect you to have
> tried this on a huge memory system - they're just too rare still
> for this to be likely.)
>
>>> So it is very unlikely for the patch itself to be at fault.
>> I have traced the issue and found that the system crashing starts from this
>> commit id and onward.
>> (i.e. The system does not crash with commit id
>> ed759d20249197cf87b338ff0ed328052ca3b8e7)
>> So, I am still believe that this patch has somehow triggered the issue.
> As said - I'm pretty certain this merely unmasked an already
> lurking issue.
I'm not quite sure what you meant here. Are you saying that this
"crashing" is a known issue?
> And that's what the purpose of that patch is.
This patch is crashing the system. What do you mean by "And that's what
the purpose of that patch is"?
Suravee
>
> Jan
>
>
next prev parent reply other threads:[~2013-06-27 10:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 0:24 x86/AMD: Nested hvm crashes in 4.3 Suravee Suthikulanit
2013-06-27 8:22 ` Jan Beulich
2013-06-27 9:20 ` Suravee Suthikulpanit
2013-06-27 9:50 ` Egger, Christoph
2013-06-27 10:08 ` Jan Beulich
2013-06-27 10:24 ` Suravee Suthikulpanit [this message]
2013-06-27 10:28 ` Andrew Cooper
2013-06-27 10:33 ` Egger, Christoph
2013-06-27 11:14 ` Suravee Suthikulpanit
2013-06-28 0:44 ` Suravee Suthikulanit
2013-06-28 7:58 ` Jan Beulich
2013-06-28 14:20 ` Suravee Suthikulanit
2013-06-28 14:24 ` Andrew Cooper
2013-06-28 14:52 ` Jan Beulich
2013-06-28 15:05 ` Egger, Christoph
2013-06-27 11:20 ` George Dunlap
2013-06-27 11:37 ` Jan Beulich
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=51CC12EC.7050608@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=JBeulich@suse.com \
--cc=Jacob.Shin@amd.com \
--cc=keir@xen.org \
--cc=sherry.hurwitz@amd.com \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).