Re: [Xen-devel] Linux 4.8-rc8 with Xen for-linus-4.9 branch: dom0 crashes on boot

2016-10-02 Thread Boris Ostrovsky 
On 10/02/2016 12:57 PM, Sander Eikelenboom wrote:
> On 2016-10-02 18:53, Boris Ostrovsky wrote:
>> On 10/02/2016 08:50 AM, Sander Eikelenboom wrote:
>>>
> Sure thing:
> addr2line -e vmlinux-4.8.0-rc8-20161002-linus-xennext+
> 8101fdb9
> /usr/src/new/linux-linus/arch/x86/xen/irq.c:34
>
> asmlinkage __visible unsigned long xen_save_fl(void)
> {
> struct vcpu_info *vcpu;
> unsigned long flags;
>
> vcpu = this_cpu_read(xen_vcpu);
>
> /* flag has opposite sense of mask */
> flags = !vcpu->evtchn_upcall_mask;   <== WHICH IS HERE
>
> /* convert to IF type flag
>-0 -> 0x
>-1 -> 0x
> */
> return (-flags) & X86_EFLAGS_IF;
> }


 Can you post your .config file?

 Our tests seem to have run fine yesterday with those branches, until
 apparently electrical problem shut down the whole test farm this
 morning.

 -boris
>>>
>>> Sure, it's attached.
>>
>>
>> I can reproduce this and will send a patch soon.
>>
>> -boris
>
> Hi Boris,
>
> Thx, just wondering though what the specific difference in .config was :)


It's CONFIG_DEBUG_MUTEXES.

When it is defined, spin_lock_mutex() does local_irq_save() which ends
up calling xen_save_fl(). And the latter requires per_cpu(xen_vcpu,
cpu<=0>) to be set, which it is not.

Until now we haven't called mutex_lock() yet at this point but now that
we are registering with hotplug infrastructure we do.


-boris





___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: [Xen-devel] Linux 4.8-rc8 with Xen for-linus-4.9 branch: dom0 crashes on boot

2016-10-02 Thread Boris Ostrovsky 
On 10/02/2016 12:57 PM, Sander Eikelenboom wrote:
> On 2016-10-02 18:53, Boris Ostrovsky wrote:
>> On 10/02/2016 08:50 AM, Sander Eikelenboom wrote:
>>>
> Sure thing:
> addr2line -e vmlinux-4.8.0-rc8-20161002-linus-xennext+
> 8101fdb9
> /usr/src/new/linux-linus/arch/x86/xen/irq.c:34
>
> asmlinkage __visible unsigned long xen_save_fl(void)
> {
> struct vcpu_info *vcpu;
> unsigned long flags;
>
> vcpu = this_cpu_read(xen_vcpu);
>
> /* flag has opposite sense of mask */
> flags = !vcpu->evtchn_upcall_mask;   <== WHICH IS HERE
>
> /* convert to IF type flag
>-0 -> 0x
>-1 -> 0x
> */
> return (-flags) & X86_EFLAGS_IF;
> }


 Can you post your .config file?

 Our tests seem to have run fine yesterday with those branches, until
 apparently electrical problem shut down the whole test farm this
 morning.

 -boris
>>>
>>> Sure, it's attached.
>>
>>
>> I can reproduce this and will send a patch soon.
>>
>> -boris
>
> Hi Boris,
>
> Thx, just wondering though what the specific difference in .config was :)
>

That's what I am trying to understand.

The fix is probably to move

per_cpu(xen_vcpu, 0) = &HYPERVISOR_shared_info->vcpu_info[0];

in enlighten.c:xen_start_kernel() up a little. I am trying to understand
what's changed to trip this error.

-boris


___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: [Xen-devel] Linux 4.8-rc8 with Xen for-linus-4.9 branch: dom0 crashes on boot

2016-10-02 Thread Sander Eikelenboom 

On 2016-10-02 18:53, Boris Ostrovsky wrote:

On 10/02/2016 08:50 AM, Sander Eikelenboom wrote:



Sure thing:
addr2line -e vmlinux-4.8.0-rc8-20161002-linus-xennext+ 
8101fdb9

/usr/src/new/linux-linus/arch/x86/xen/irq.c:34

asmlinkage __visible unsigned long xen_save_fl(void)
{
struct vcpu_info *vcpu;
unsigned long flags;

vcpu = this_cpu_read(xen_vcpu);

/* flag has opposite sense of mask */
flags = !vcpu->evtchn_upcall_mask;   <== WHICH IS HERE

/* convert to IF type flag
   -0 -> 0x
   -1 -> 0x
*/
return (-flags) & X86_EFLAGS_IF;
}



Can you post your .config file?

Our tests seem to have run fine yesterday with those branches, until
apparently electrical problem shut down the whole test farm this
morning.

-boris


Sure, it's attached.



I can reproduce this and will send a patch soon.

-boris


Hi Boris,

Thx, just wondering though what the specific difference in .config was 
:)


--
Sander
Thx

___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: [Xen-devel] Linux 4.8-rc8 with Xen for-linus-4.9 branch: dom0 crashes on boot

2016-10-02 Thread Boris Ostrovsky 
On 10/02/2016 08:50 AM, Sander Eikelenboom wrote:
>
>>> Sure thing:
>>> addr2line -e vmlinux-4.8.0-rc8-20161002-linus-xennext+ 8101fdb9
>>> /usr/src/new/linux-linus/arch/x86/xen/irq.c:34
>>>
>>> asmlinkage __visible unsigned long xen_save_fl(void)
>>> {
>>> struct vcpu_info *vcpu;
>>> unsigned long flags;
>>>
>>> vcpu = this_cpu_read(xen_vcpu);
>>>
>>> /* flag has opposite sense of mask */
>>> flags = !vcpu->evtchn_upcall_mask;   <== WHICH IS HERE
>>>
>>> /* convert to IF type flag
>>>-0 -> 0x
>>>-1 -> 0x
>>> */
>>> return (-flags) & X86_EFLAGS_IF;
>>> }
>>
>>
>> Can you post your .config file?
>>
>> Our tests seem to have run fine yesterday with those branches, until
>> apparently electrical problem shut down the whole test farm this
>> morning.
>>
>> -boris
>
> Sure, it's attached.


I can reproduce this and will send a patch soon.

-boris


___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: [Xen-devel] Linux 4.8-rc8 with Xen for-linus-4.9 branch: dom0 crashes on boot

2016-10-02 Thread Boris Ostrovsky 
On 10/02/2016 08:26 AM, Sander Eikelenboom wrote:
> On 2016-10-02 14:08, Andrew Cooper wrote:
>> On 02/10/2016 12:46, Sander Eikelenboom wrote:
>>> Hi All,
>>>
>>> Since the new merge window is emerging I took the liberty of testing a
>>> linux 4.8-rc8 tree with
>>> the Xen for-linus-4.9 branch pulled on top.
>>> Unfortunately this crashes dom0 early in boot under Xen.
>>> On bare-metal the same kernel boots fine.
>>> Under Xen a linux 4.8-rc8 kernel without the Xen branch pulled on top,
>>> also boots fine.
>>
>> So this looks to be a regression in the Xen for-linux-4.9 branch.
>>
>>>
>>> Hypervisor is a recentish xen-unstable build.
>>>
>>> The serial log is below.
>>> 
>>> (XEN) [2016-10-02 11:31:53.106] Scrubbing Free RAM on 1 nodes using 6
>>> CPUs
>>> (XEN) [2016-10-02 11:31:53.217] .done.
>>> (XEN) [2016-10-02 11:31:56.242] Initial low memory virq threshold set
>>> at 0x4000 pages.
>>> (XEN) [2016-10-02 11:31:56.260] Std. Loglevel: All
>>> (XEN) [2016-10-02 11:31:56.277] Guest Loglevel: All
>>> (XEN) [2016-10-02 11:31:56.295] Xen is relinquishing VGA console.
>>> (XEN) [2016-10-02 11:31:56.396] *** Serial input -> DOM0 (type
>>> 'CTRL-a' three times to switch input to Xen)
>>> (XEN) [2016-10-02 11:31:56.396] Freed 308kB init memory
>>> (XEN) [2016-10-02 11:31:56.397] d0v0: unhandled page fault (ec=)
>>> (XEN) [2016-10-02 11:31:56.397] Pagetable walk from 0001:
>>> (XEN) [2016-10-02 11:31:56.397]  L4[0x000] = 
>>> 
>>> (XEN) [2016-10-02 11:31:56.397] domain_crash_sync called from entry.S:
>>> fault at 82d080244960 entry.o#create_bounce_frame+0x145/0x154
>>> (XEN) [2016-10-02 11:31:56.397] Domain 0 (vcpu#0) crashed on cpu#0:
>>> (XEN) [2016-10-02 11:31:56.397] [ Xen-4.8-unstable  x86_64
>>> debug=y   Not tainted ]
>>> (XEN) [2016-10-02 11:31:56.397] CPU:0
>>> (XEN) [2016-10-02 11:31:56.397] RIP:e033:[]
>>> (XEN) [2016-10-02 11:31:56.397] RFLAGS: 0286   EM: 1
>>> CONTEXT: pv guest (d0v0)
>>> (XEN) [2016-10-02 11:31:56.397] rax:    rbx:
>>> 82248bb0   rcx: 8101bc10
>>> (XEN) [2016-10-02 11:31:56.397] rdx: 0001   rsi:
>>> 81f0aa50   rdi: 82248bb0
>>> (XEN) [2016-10-02 11:31:56.397] rbp: 82203e50   rsp:
>>> 82203dc0   r8:  8101b550
>>> (XEN) [2016-10-02 11:31:56.397] r9:     r10:
>>>    r11: 80802001
>>> (XEN) [2016-10-02 11:31:56.397] r12:    r13:
>>>    r14: 82215580
>>> (XEN) [2016-10-02 11:31:56.397] r15:    cr0:
>>> 8005003b   cr4: 06e0
>>> (XEN) [2016-10-02 11:31:56.397] cr3: 00054a601000   cr2:
>>> 0001
>>> (XEN) [2016-10-02 11:31:56.397] ds:    es:    fs:    gs:
>>>    ss: e02b   cs: e033
>>> (XEN) [2016-10-02 11:31:56.397] Guest stack trace from
>>> rsp=82203dc0:
>>> (XEN) [2016-10-02 11:31:56.397]8101bc10 80802001
>>>  8101fdb9
>>> (XEN) [2016-10-02 11:31:56.397]0001e030 00010086
>>> 82203e00 e02b
>>> (XEN) [2016-10-02 11:31:56.397]82203e50 8101fcb5
>>> 80802001 
>>> (XEN) [2016-10-02 11:31:56.397] 8101b550
>>> 82248bb0 81f0aa50
>>> (XEN) [2016-10-02 11:31:56.397]0001 8101bc10
>>> 82203eb8 81b7e9f4
>>> (XEN) [2016-10-02 11:31:56.397] 82203ea8
>>> 80802001 0004
>>> (XEN) [2016-10-02 11:31:56.397]8101baa2 82203f40
>>> 82248bb0 
>>> (XEN) [2016-10-02 11:31:56.397] 8101bc10
>>>  82203ed0
>>> (XEN) [2016-10-02 11:31:56.397]81b7ed45 0013
>>> 82203ee0 810cc127
>>> (XEN) [2016-10-02 11:31:56.397]82203f28 810ccdab
>>> 81f0aa50 8101b550
>>> (XEN) [2016-10-02 11:31:56.397]82203f60 82203f5c
>>>  
>>> (XEN) [2016-10-02 11:31:56.397] 82203f40
>>> 810c83be 8260
>>> (XEN) [2016-10-02 11:31:56.397]82203ff8 8232946a
>>> 00100fa0 8080200100060800
>>> (XEN) [2016-10-02 11:31:56.397]1789c3f5 
>>>  
>>> (XEN) [2016-10-02 11:31:56.397] 
>>>  
>>> (XEN) [2016-10-02 11:31:56.397] 
>>>  
>>> (XEN) [2016-10-02 11:31:56.397] 
>>>  
>>> (XEN) [2016-10-02 11:31:56.397] 
>>>  
>>> (XEN) [2016-10-02 11:31:56.39

Re: [Xen-devel] Linux 4.8-rc8 with Xen for-linus-4.9 branch: dom0 crashes on boot

2016-10-02 Thread Sander Eikelenboom 

On 2016-10-02 14:08, Andrew Cooper wrote:

On 02/10/2016 12:46, Sander Eikelenboom wrote:

Hi All,

Since the new merge window is emerging I took the liberty of testing a
linux 4.8-rc8 tree with
the Xen for-linus-4.9 branch pulled on top.
Unfortunately this crashes dom0 early in boot under Xen.
On bare-metal the same kernel boots fine.
Under Xen a linux 4.8-rc8 kernel without the Xen branch pulled on top,
also boots fine.


So this looks to be a regression in the Xen for-linux-4.9 branch.



Hypervisor is a recentish xen-unstable build.

The serial log is below.

(XEN) [2016-10-02 11:31:53.106] Scrubbing Free RAM on 1 nodes using 6
CPUs
(XEN) [2016-10-02 11:31:53.217] .done.
(XEN) [2016-10-02 11:31:56.242] Initial low memory virq threshold set
at 0x4000 pages.
(XEN) [2016-10-02 11:31:56.260] Std. Loglevel: All
(XEN) [2016-10-02 11:31:56.277] Guest Loglevel: All
(XEN) [2016-10-02 11:31:56.295] Xen is relinquishing VGA console.
(XEN) [2016-10-02 11:31:56.396] *** Serial input -> DOM0 (type
'CTRL-a' three times to switch input to Xen)
(XEN) [2016-10-02 11:31:56.396] Freed 308kB init memory
(XEN) [2016-10-02 11:31:56.397] d0v0: unhandled page fault (ec=)
(XEN) [2016-10-02 11:31:56.397] Pagetable walk from 0001:
(XEN) [2016-10-02 11:31:56.397]  L4[0x000] = 

(XEN) [2016-10-02 11:31:56.397] domain_crash_sync called from entry.S:
fault at 82d080244960 entry.o#create_bounce_frame+0x145/0x154
(XEN) [2016-10-02 11:31:56.397] Domain 0 (vcpu#0) crashed on cpu#0:
(XEN) [2016-10-02 11:31:56.397] [ Xen-4.8-unstable  x86_64
debug=y   Not tainted ]
(XEN) [2016-10-02 11:31:56.397] CPU:0
(XEN) [2016-10-02 11:31:56.397] RIP:e033:[]
(XEN) [2016-10-02 11:31:56.397] RFLAGS: 0286   EM: 1
CONTEXT: pv guest (d0v0)
(XEN) [2016-10-02 11:31:56.397] rax:    rbx:
82248bb0   rcx: 8101bc10
(XEN) [2016-10-02 11:31:56.397] rdx: 0001   rsi:
81f0aa50   rdi: 82248bb0
(XEN) [2016-10-02 11:31:56.397] rbp: 82203e50   rsp:
82203dc0   r8:  8101b550
(XEN) [2016-10-02 11:31:56.397] r9:     r10:
   r11: 80802001
(XEN) [2016-10-02 11:31:56.397] r12:    r13:
   r14: 82215580
(XEN) [2016-10-02 11:31:56.397] r15:    cr0:
8005003b   cr4: 06e0
(XEN) [2016-10-02 11:31:56.397] cr3: 00054a601000   cr2:
0001
(XEN) [2016-10-02 11:31:56.397] ds:    es:    fs:    gs:
   ss: e02b   cs: e033
(XEN) [2016-10-02 11:31:56.397] Guest stack trace from
rsp=82203dc0:
(XEN) [2016-10-02 11:31:56.397]8101bc10 80802001
 8101fdb9
(XEN) [2016-10-02 11:31:56.397]0001e030 00010086
82203e00 e02b
(XEN) [2016-10-02 11:31:56.397]82203e50 8101fcb5
80802001 
(XEN) [2016-10-02 11:31:56.397] 8101b550
82248bb0 81f0aa50
(XEN) [2016-10-02 11:31:56.397]0001 8101bc10
82203eb8 81b7e9f4
(XEN) [2016-10-02 11:31:56.397] 82203ea8
80802001 0004
(XEN) [2016-10-02 11:31:56.397]8101baa2 82203f40
82248bb0 
(XEN) [2016-10-02 11:31:56.397] 8101bc10
 82203ed0
(XEN) [2016-10-02 11:31:56.397]81b7ed45 0013
82203ee0 810cc127
(XEN) [2016-10-02 11:31:56.397]82203f28 810ccdab
81f0aa50 8101b550
(XEN) [2016-10-02 11:31:56.397]82203f60 82203f5c
 
(XEN) [2016-10-02 11:31:56.397] 82203f40
810c83be 8260
(XEN) [2016-10-02 11:31:56.397]82203ff8 8232946a
00100fa0 8080200100060800
(XEN) [2016-10-02 11:31:56.397]1789c3f5 
 
(XEN) [2016-10-02 11:31:56.397] 
 
(XEN) [2016-10-02 11:31:56.397] 
 
(XEN) [2016-10-02 11:31:56.397] 
 
(XEN) [2016-10-02 11:31:56.397] 
 
(XEN) [2016-10-02 11:31:56.397]0f0060c0c748 c305
 
(XEN) [2016-10-02 11:31:56.397] 
 
(XEN) [2016-10-02 11:31:56.397] Hardware Dom0 crashed: rebooting
machine in 5 seconds.


Something in Linux at 8101fdb9 followed a NULL pointer.  Can 
you

see what it was with the linux debug symbols?

~Andrew


Sure thing:
addr2line -e vml

Re: [Xen-devel] Linux 4.8-rc8 with Xen for-linus-4.9 branch: dom0 crashes on boot

2016-10-02 Thread Andrew Cooper 
On 02/10/2016 12:46, Sander Eikelenboom wrote:
> Hi All,
>
> Since the new merge window is emerging I took the liberty of testing a
> linux 4.8-rc8 tree with
> the Xen for-linus-4.9 branch pulled on top.
> Unfortunately this crashes dom0 early in boot under Xen.
> On bare-metal the same kernel boots fine.
> Under Xen a linux 4.8-rc8 kernel without the Xen branch pulled on top,
> also boots fine.

So this looks to be a regression in the Xen for-linux-4.9 branch.

>
> Hypervisor is a recentish xen-unstable build.
>
> The serial log is below.
> 
> (XEN) [2016-10-02 11:31:53.106] Scrubbing Free RAM on 1 nodes using 6
> CPUs
> (XEN) [2016-10-02 11:31:53.217] .done.
> (XEN) [2016-10-02 11:31:56.242] Initial low memory virq threshold set
> at 0x4000 pages.
> (XEN) [2016-10-02 11:31:56.260] Std. Loglevel: All
> (XEN) [2016-10-02 11:31:56.277] Guest Loglevel: All
> (XEN) [2016-10-02 11:31:56.295] Xen is relinquishing VGA console.
> (XEN) [2016-10-02 11:31:56.396] *** Serial input -> DOM0 (type
> 'CTRL-a' three times to switch input to Xen)
> (XEN) [2016-10-02 11:31:56.396] Freed 308kB init memory
> (XEN) [2016-10-02 11:31:56.397] d0v0: unhandled page fault (ec=)
> (XEN) [2016-10-02 11:31:56.397] Pagetable walk from 0001:
> (XEN) [2016-10-02 11:31:56.397]  L4[0x000] = 
> 
> (XEN) [2016-10-02 11:31:56.397] domain_crash_sync called from entry.S:
> fault at 82d080244960 entry.o#create_bounce_frame+0x145/0x154
> (XEN) [2016-10-02 11:31:56.397] Domain 0 (vcpu#0) crashed on cpu#0:
> (XEN) [2016-10-02 11:31:56.397] [ Xen-4.8-unstable  x86_64 
> debug=y   Not tainted ]
> (XEN) [2016-10-02 11:31:56.397] CPU:0
> (XEN) [2016-10-02 11:31:56.397] RIP:e033:[]
> (XEN) [2016-10-02 11:31:56.397] RFLAGS: 0286   EM: 1  
> CONTEXT: pv guest (d0v0)
> (XEN) [2016-10-02 11:31:56.397] rax:    rbx:
> 82248bb0   rcx: 8101bc10
> (XEN) [2016-10-02 11:31:56.397] rdx: 0001   rsi:
> 81f0aa50   rdi: 82248bb0
> (XEN) [2016-10-02 11:31:56.397] rbp: 82203e50   rsp:
> 82203dc0   r8:  8101b550
> (XEN) [2016-10-02 11:31:56.397] r9:     r10:
>    r11: 80802001
> (XEN) [2016-10-02 11:31:56.397] r12:    r13:
>    r14: 82215580
> (XEN) [2016-10-02 11:31:56.397] r15:    cr0:
> 8005003b   cr4: 06e0
> (XEN) [2016-10-02 11:31:56.397] cr3: 00054a601000   cr2:
> 0001
> (XEN) [2016-10-02 11:31:56.397] ds:    es:    fs:    gs:
>    ss: e02b   cs: e033
> (XEN) [2016-10-02 11:31:56.397] Guest stack trace from
> rsp=82203dc0:
> (XEN) [2016-10-02 11:31:56.397]8101bc10 80802001
>  8101fdb9
> (XEN) [2016-10-02 11:31:56.397]0001e030 00010086
> 82203e00 e02b
> (XEN) [2016-10-02 11:31:56.397]82203e50 8101fcb5
> 80802001 
> (XEN) [2016-10-02 11:31:56.397] 8101b550
> 82248bb0 81f0aa50
> (XEN) [2016-10-02 11:31:56.397]0001 8101bc10
> 82203eb8 81b7e9f4
> (XEN) [2016-10-02 11:31:56.397] 82203ea8
> 80802001 0004
> (XEN) [2016-10-02 11:31:56.397]8101baa2 82203f40
> 82248bb0 
> (XEN) [2016-10-02 11:31:56.397] 8101bc10
>  82203ed0
> (XEN) [2016-10-02 11:31:56.397]81b7ed45 0013
> 82203ee0 810cc127
> (XEN) [2016-10-02 11:31:56.397]82203f28 810ccdab
> 81f0aa50 8101b550
> (XEN) [2016-10-02 11:31:56.397]82203f60 82203f5c
>  
> (XEN) [2016-10-02 11:31:56.397] 82203f40
> 810c83be 8260
> (XEN) [2016-10-02 11:31:56.397]82203ff8 8232946a
> 00100fa0 8080200100060800
> (XEN) [2016-10-02 11:31:56.397]1789c3f5 
>  
> (XEN) [2016-10-02 11:31:56.397] 
>  
> (XEN) [2016-10-02 11:31:56.397] 
>  
> (XEN) [2016-10-02 11:31:56.397] 
>  
> (XEN) [2016-10-02 11:31:56.397] 
>  
> (XEN) [2016-10-02 11:31:56.397]0f0060c0c748 c305
>  
> (XEN) [2016-10-02 11:31:56.397] 
>  
> (XEN) [2016-10-02 11:31:56.397] Hardware Dom0 crashed: rebooting
> machine in 5 seconds.

Something in

[Xen-devel] Linux 4.8-rc8 with Xen for-linus-4.9 branch: dom0 crashes on boot

2016-10-02 Thread Sander Eikelenboom 

Hi All,

Since the new merge window is emerging I took the liberty of testing a 
linux 4.8-rc8 tree with

the Xen for-linus-4.9 branch pulled on top.
Unfortunately this crashes dom0 early in boot under Xen.
On bare-metal the same kernel boots fine.
Under Xen a linux 4.8-rc8 kernel without the Xen branch pulled on top, 
also boots fine.


Hypervisor is a recentish xen-unstable build.

The serial log is below.

--
Sander

 __  ___  ____ __ _
 \ \/ /___ _ __   | || |  ( _ )_   _ _ __  ___| |_ __ _| |__ | | ___
  \  // _ \ '_ \  | || |_ / _ \ __| | | | '_ \/ __| __/ _` | '_ \| |/ _ 
\
  /  \  __/ | | | |__   _| (_) |__| |_| | | | \__ \ || (_| | |_) | |  
__/
 /_/\_\___|_| |_||_|(_)___/\__,_|_| 
|_|___/\__\__,_|_.__/|_|\___|


(XEN) Xen version 4.8-unstable (r...@dyndns.org) (gcc-4.9.real (Debian 
4.9.2-10) 4.9.2) debug=y  Sat Oct  1 21:59:54 CEST 2016

(XEN) Latest ChangeSet: Wed Sep 28 12:12:13 2016 +0100 git:da9207c-dirty
(XEN) Bootloader: GRUB 2.02~beta2-22+deb8u1
(XEN) Command line: dom0_mem=2048M,max:2048M loglvl=all loglvl_guest=all 
console_timestamps=datems vga=gfx-1280x1024x32 no-cpuidle cpufreq=xen 
com1=38400,8n1 console=vga,com1 ivrs_ioapic[6]=00:14.0 
iommu=on,verbose,debug,amd-iommu-debug conring_size=128k ucode=-1

(XEN) Video information:
(XEN)  VGA is graphics mode 1280x1024, 32 bpp
(XEN)  VBE/DDC methods: V2; EDID transfer time: 1 seconds
(XEN) Disc information:
(XEN)  Found 2 MBR signatures
(XEN)  Found 2 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)   - 00099400 (usable)
(XEN)  00099400 - 000a (reserved)
(XEN)  000e4000 - 0010 (reserved)
(XEN)  0010 - 9ff9 (usable)
(XEN)  9ff9 - 9ff9e000 (ACPI data)
(XEN)  9ff9e000 - 9ffe (ACPI NVS)
(XEN)  9ffe - a000 (reserved)
(XEN)  ffe0 - 0001 (reserved)
(XEN)  0001 - 00056000 (usable)
(XEN) ACPI: RSDP 000FB100, 0014 (r0 ACPIAM)
(XEN) ACPI: RSDT 9FF9, 0048 (r1 MSIOEMSLIC  20100913 MSFT   
97)
(XEN) ACPI: FACP 9FF90200, 0084 (r1 7640MS A7640100 20100913 MSFT   
97)
(XEN) ACPI: DSDT 9FF905E0, 9427 (r1  A7640 A7640100  100 INTL 
20051117)

(XEN) ACPI: FACS 9FF9E000, 0040
(XEN) ACPI: APIC 9FF90390, 0088 (r1 7640MS A7640100 20100913 MSFT   
97)
(XEN) ACPI: MCFG 9FF90420, 003C (r1 7640MS OEMMCFG  20100913 MSFT   
97)
(XEN) ACPI: SLIC 9FF90460, 0176 (r1 MSIOEMSLIC  20100913 MSFT   
97)
(XEN) ACPI: OEMB 9FF9E040, 0072 (r1 7640MS A7640100 20100913 MSFT   
97)
(XEN) ACPI: SRAT 9FF9A5E0, 0108 (r3 AMDFAM_F_102 AMD 
1)
(XEN) ACPI: HPET 9FF9A6F0, 0038 (r1 7640MS OEMHPET  20100913 MSFT   
97)
(XEN) ACPI: IVRS 9FF9A730, 0110 (r1  AMD RD890S   202031 AMD 
0)
(XEN) ACPI: SSDT 9FF9A840, 0DA4 (r1 A M I  POWERNOW1 AMD 
1)

(XEN) System RAM: 20479MB (20970660kB)
(XEN) SRAT: PXM 0 -> APIC 00 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 01 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 02 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 03 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 04 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 05 -> Node 0
(XEN) SRAT: Node 0 PXM 0 0-a
(XEN) SRAT: Node 0 PXM 0 10-a000
(XEN) SRAT: Node 0 PXM 0 1-56000
(XEN) NUMA: Allocated memnodemap from 55c75c000 - 55c762000
(XEN) NUMA: Using 8 for the hash shift.
(XEN) Domain heap initialised
(XEN) Allocated console ring of 128 KiB.
(XEN) vesafb: framebuffer at 0xd000, mapped to 0x82c000201000, 
using 6144k, total 16384k

(XEN) vesafb: mode is 1280x1024x32, linelength=5120, font 8x16
(XEN) vesafb: Truecolor: size=0:8:8:8, shift=0:16:8:0
(XEN) CPU Vendor: AMD, Family 16 (0x10), Model 10 (0xa), Stepping 0 (raw 
00100fa0)

(XEN) found SMP MP-table at 000ff780
(XEN) DMI present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x808 (24 bits)
(XEN) ACPI: SLEEP INFO: pm1x_cnt[1:804,1:0], pm1x_evt[1:800,1:0]
(XEN) ACPI: wakeup_vec[9ff9e00c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee0
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x04] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x05] enabled)
(XEN) ACPI: IOAPIC (id[0x06] address[0xfec0] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 6, version 33, address 0xfec0, GSI 0-23
(XEN) ACPI: IOAPIC (id[0x07] address[0xfec2] gsi_base[24])
(XEN) IOAPIC[1]: apic_id 7, version 33, address 0xfec2, GSI 24-55
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode:  Flat.