On 20/10/2015 16:27, Boris Ostrovsky wrote:
> On 10/20/2015 09:43 AM, Jan Beulich wrote:
> On 20.10.15 at 15:22, wrote:
>>> The reason I think its this commit is that RAX, RDX and RCX look very
>>> much like arguments to xsetbv (which xstate_enable_boot_cpu() executes)
>>> and RAX value is 0x1
>>> On 20.10.15 at 16:27, wrote:
> On 10/20/2015 09:43 AM, Jan Beulich wrote:
> On 20.10.15 at 15:22, wrote:
>>> The reason I think its this commit is that RAX, RDX and RCX look very
>>> much like arguments to xsetbv (which xstate_enable_boot_cpu() executes)
>>> and RAX value is 0x1f, which h
On 10/20/2015 09:43 AM, Jan Beulich wrote:
On 20.10.15 at 15:22, wrote:
The reason I think its this commit is that RAX, RDX and RCX look very
much like arguments to xsetbv (which xstate_enable_boot_cpu() executes)
and RAX value is 0x1f, which has two new bits that this commit defined.
That wou
>>> On 20.10.15 at 15:22, wrote:
> The reason I think its this commit is that RAX, RDX and RCX look very
> much like arguments to xsetbv (which xstate_enable_boot_cpu() executes)
> and RAX value is 0x1f, which has two new bits that this commit defined.
That would be the two MPX related bits, ye
On 10/20/2015 08:11 AM, John Doe wrote:
On 20/10/2015 11:51, Jan Beulich wrote:
On 19.10.15 at 18:25, wrote:
On 10/19/2015 06:16 AM, John Doe wrote:
[0.00] general protection fault: [#1] SMP
[0.00] Modules linked in:
[0.00] CPU: 0 PID: 0 Comm: swapper Not tainted
On 20/10/2015 11:51, Jan Beulich wrote:
On 19.10.15 at 18:25, wrote:
>> On 10/19/2015 06:16 AM, John Doe wrote:
> [0.00] general protection fault: [#1] SMP
> [0.00] Modules linked in:
> [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted
>> 4.1.9-6.pvops.q
>>> On 19.10.15 at 18:25, wrote:
> On 10/19/2015 06:16 AM, John Doe wrote:
[0.00] general protection fault: [#1] SMP
[0.00] Modules linked in:
[0.00] CPU: 0 PID: 0 Comm: swapper Not tainted
> 4.1.9-6.pvops.qubes.x86_64 #1
[0.00] Hardware na
On 10/19/2015 06:16 AM, John Doe wrote:
[0.00] general protection fault: [#1] SMP
[0.00] Modules linked in:
[0.00] CPU: 0 PID: 0 Comm: swapper Not tainted
4.1.9-6.pvops.qubes.x86_64 #1
[0.00] Hardware name: To Be Filled By O.E.M. To Be Filled By
O.E.M./Z170
On 19/10/2015 09:56, Ingo Molnar wrote:
>
> Please Cc: the Xen maintainers as this appears to be Xen specific. Also,
> please
> Cc: linux-ker...@vger.kernel.org.
>
> Thanks,
>
> Ingo
>
> * John Doe wrote:
>
>> Hello,
>> I get a kernel panic on QubesOS 3.0 during boot with kernels newe
