From: John Doe <securef33d@gmail.com>
To: Jan Beulich <JBeulich@suse.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: Ingo Molnar <mingo@kernel.org>,
x86@kernel.org, xen-devel@lists.xen.org,
linux-kernel@vger.kernel.org
Subject: Re: [Xen-devel] PROBLEM: kernel panic xsave_init
Date: Tue, 20 Oct 2015 14:11:45 +0200 [thread overview]
Message-ID: <56262F81.804@gmail.com> (raw)
In-Reply-To: <56262AD802000078000ACAA1@prv-mh.provo.novell.com>
On 20/10/2015 11:51, Jan Beulich wrote:
>>>> On 19.10.15 at 18:25, <boris.ostrovsky@oracle.com> wrote:
>> On 10/19/2015 06:16 AM, John Doe wrote:
>>>>> [ 0.000000] general protection fault: 0000 [#1] SMP
>>>>> [ 0.000000] Modules linked in:
>>>>> [ 0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted
>> 4.1.9-6.pvops.qubes.x86_64 #1
>>>>> [ 0.000000] Hardware name: To Be Filled By O.E.M. To Be Filled By
>> O.E.M./Z170 Extreme4, BIOS P1.80 09/18/2015
>>>>> [ 0.000000] task: ffffffff81c154c0 ti: ffffffff81c00000 task.ti:
>> ffffffff81c00000
>>>>> [ 0.000000] RIP: e030:[<ffffffff81d58fad>] [<ffffffff81d58fad>]
>> xstate_enable_boot_cpu+0xde/0x288
>>>>> [ 0.000000] RSP: e02b:ffffffff81c03de8 EFLAGS: 00010046
>>>>> [ 0.000000] RAX: 000000000000001f RBX: 0000000000000008 RCX:
>> 0000000000000000
>>>>> [ 0.000000] RDX: 0000000000000000 RSI: 000000000000001f RDI:
>> 0000000000042660
>>
>>
>> It would be good to see what's at ffffffff81d58fad. My guess would be
>> that it's xsetbv.
>>
>> If it is then you probably want to make sure you are running hypervisor
>> that has commit e8121c54 ("x86/xsave: enable support for new ISA
>> extensions"). Looks like the first version that has it is 4.5 and you
>> seem to be running 4.4.2.
>>
>> Copying Jan to see if there are plans to backport this (probably not
>> since it's a new feature).
>
> Hmm, if there are features getting exposed that lead to crashes like
> this, then while we wouldn't normally backport enhancements, we
> may need to consider adding a one-off patch to hide respective
> features to that stable branch. But first we of course need to
> understand what is going on here.
>
> Jan
>
I will try with 4.6.0 asap, unfortunately the 4.4.2 image i have is not
built with debug enabled and i'm unable to run gdb at boot, i'm building
a new one right now.
If you need anything else please be very step-specific since i'm not
very practical at this.
Thank you,
John.
next prev parent reply other threads:[~2015-10-20 12:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <562430E6.6010205@gmail.com>
[not found] ` <20151019075618.GA22488@gmail.com>
2015-10-19 10:16 ` John Doe
2015-10-19 16:25 ` [Xen-devel] " Boris Ostrovsky
2015-10-20 9:51 ` Jan Beulich
2015-10-20 12:11 ` John Doe [this message]
2015-10-20 13:22 ` Boris Ostrovsky
2015-10-20 13:43 ` Jan Beulich
2015-10-20 14:27 ` Boris Ostrovsky
2015-10-20 14:41 ` Jan Beulich
2015-10-21 0:17 ` John Doe
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=56262F81.804@gmail.com \
--to=securef33d@gmail.com \
--cc=JBeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=x86@kernel.org \
--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
Powered by JetHome