subject:"\[Xen\-devel\] Xen\-unstable 4.8\: Host crash when shutting down guest with pci device passed through using MSI\-X interrupts."

Re: [Xen-devel] Xen-unstable 4.8: Host crash when shutting down guest with pci device passed through using MSI-X interrupts.

2016-07-18 Thread Andrew Cooper

On 18/07/2016 23:03, li...@eikelenboom.it wrote:
> On 2016-07-18 22:57, Andrew Cooper wrote:
>> On 18/07/2016 20:26, Sander Eikelenboom wrote:
>>> Monday, July 18, 2016, 7:48:20 PM, you wrote:
>>>
 On 18/07/16 11:21, li...@eikelenboom.it wrote:
> Hi Jan,
>
> It seems that since your patch series starting with commit:
> 2016-06-22 x86/vMSI-X: defer intercept handler registration
> 74c6dc2d0ac4dcab0c6243cdf6ed550c1532b798
>
> The shutdown of a guest which has a PCI device passed through which
> uses MSI-X interrupts causes
> a host crash, see the splat below. Somehow it also doesn't reboot
> in 5
> seconds as it is supposed to (i don't have no-reboot on the command
> line).
>
> -- 
> Sander
>
>
> (XEN) [2016-07-16 16:03:17.069] [ Xen-4.8-unstable  x86_64
> debug=y  Not tainted ]
> (XEN) [2016-07-16 16:03:17.069] CPU:0
> (XEN) [2016-07-16 16:03:17.069] RIP:e008:[]
> msixtbl_pt_unregister+0x7b/0xd9
> (XEN) [2016-07-16 16:03:17.069] RFLAGS: 00010082   CONTEXT:
> hypervisor (d0v0)
> (XEN) [2016-07-16 16:03:17.069] rax: 83055c678e40   rbx:
> 83055c685500   rcx: 0001
> (XEN) [2016-07-16 16:03:17.069] rdx:    rsi:
> 1ab0   rdi: 8305313b85a0
> (XEN) [2016-07-16 16:03:17.069] rbp: 83009fd07c78   rsp:
> 83009fd07c68   r8:  8305356dfff0
> (XEN) [2016-07-16 16:03:17.069] r9:  8305356df480   r10:
> 830503420c50   r11: 0282
> (XEN) [2016-07-16 16:03:17.069] r12: 8305313b8000   r13:
> 83009fd07e48   r14: 8305313b8000
> (XEN) [2016-07-16 16:03:17.069] r15: 8305356df4a8   cr0:
> 80050033   cr4: 06e0
> (XEN) [2016-07-16 16:03:17.069] cr3: 00053639f000   cr2:
> 
> (XEN) [2016-07-16 16:03:17.069] ds:    es:    fs:    gs:
>    ss: e010   cs: e008
> (XEN) [2016-07-16 16:03:17.069] Xen code around 
> (msixtbl_pt_unregister+0x7b/0xd9):
> (XEN) [2016-07-16 16:03:17.069]  39 42 18 74 19 48 89 ca <48> 8b
> 0a 0f
> 18 09 48 39 fa 75 ec 48 8d 7b 24 e8
> (XEN) [2016-07-16 16:03:17.069] Xen stack trace from
> rsp=83009fd07c68:
> (XEN) [2016-07-16 16:03:17.069] 8305356df480
> 83009fd07ce8 82d08014c394
> (XEN) [2016-07-16 16:03:17.069]0001 8305356df480
> 0293 8305313b80cc
> (XEN) [2016-07-16 16:03:17.069]00568012ffe5 8305313b8000
> 83009fd07cd8 83009fd07e38
> (XEN) [2016-07-16 16:03:17.070] 83054e5fc000
> 7fc25a33e004 8305313b8000
> (XEN) [2016-07-16 16:03:17.070]83009fd07da8 82d0801629c8
>  83053b1191f0
> (XEN) [2016-07-16 16:03:17.070]0246 83009fd07d28
> 82d0801300ae 000e
> (XEN) [2016-07-16 16:03:17.070]83009fd07d78 82d080171497
> 83009fd07d78 00020001d17b
> (XEN) [2016-07-16 16:03:17.070]83009fd07d68 
> 83009fd07d68 82d080130280
> (XEN) [2016-07-16 16:03:17.070]83009fd07d78 82d08014d0aa
> 0202 
> (XEN) [2016-07-16 16:03:17.070]8305313b8000 88005716d320
> 00305000 7fc25a33e004
> (XEN) [2016-07-16 16:03:17.070]83009fd07ef8 82d080104b2c
> 0206 0002
> (XEN) [2016-07-16 16:03:17.070]83009fd07df8 82d08018c9db
> 0cfe 0002
> (XEN) [2016-07-16 16:03:17.070]0002 83054e5fc000
> 83009fd07e48 82d08019c119
> (XEN) [2016-07-16 16:03:17.070]83009fd07e38 80121177
> 83009fd07e38 0cfe
> (XEN) [2016-07-16 16:03:17.070]83009fd07f18 0206
> 000c0030 56082bb90013
> (XEN) [2016-07-16 16:03:17.070]00020056 7fc20013
> 3056 56082b87465d
> (XEN) [2016-07-16 16:03:17.070]7ffe268206e0 7fc25606b31f
>  56082b8746cf
> (XEN) [2016-07-16 16:03:17.070]1000 fee5600026820730
> 7ffe26820740 56082b8797be
> (XEN) [2016-07-16 16:03:17.070]fee56000 430026820772
> 7ffe26820740 3056
> (XEN) [2016-07-16 16:03:17.070]7ffe268206e0 83009ff8a000
> 7ffe26820580 88005716d320
> (XEN) [2016-07-16 16:03:17.070] Xen call trace:
> (XEN) [2016-07-16 16:03:17.070][]
> msixtbl_pt_unregister+0x7b/0xd9
> (XEN) [2016-07-16 16:03:17.070][]
> pt_irq_destroy_bind+0x2be/0x3f0
> (XEN) [2016-07-16 16:03:17.070][]
> arch_do_domctl+0xc77/0x2414
> (XEN) [2016-07-16 16:03:17.070][]
> do_domctl+0x19db/0x1d26
> (XEN) [2016-07-16

Re: [Xen-devel] Xen-unstable 4.8: Host crash when shutting down guest with pci device passed through using MSI-X interrupts.

2016-07-18 Thread linux


On 2016-07-18 22:57, Andrew Cooper wrote:

On 18/07/2016 20:26, Sander Eikelenboom wrote:

Monday, July 18, 2016, 7:48:20 PM, you wrote:


On 18/07/16 11:21, li...@eikelenboom.it wrote:

Hi Jan,

It seems that since your patch series starting with commit:
2016-06-22 x86/vMSI-X: defer intercept handler registration
74c6dc2d0ac4dcab0c6243cdf6ed550c1532b798

The shutdown of a guest which has a PCI device passed through which
uses MSI-X interrupts causes
a host crash, see the splat below. Somehow it also doesn't reboot in 
5

seconds as it is supposed to (i don't have no-reboot on the command
line).

--
Sander


(XEN) [2016-07-16 16:03:17.069] [ Xen-4.8-unstable  x86_64
debug=y  Not tainted ]
(XEN) [2016-07-16 16:03:17.069] CPU:0
(XEN) [2016-07-16 16:03:17.069] RIP:e008:[]
msixtbl_pt_unregister+0x7b/0xd9
(XEN) [2016-07-16 16:03:17.069] RFLAGS: 00010082   CONTEXT:
hypervisor (d0v0)
(XEN) [2016-07-16 16:03:17.069] rax: 83055c678e40   rbx:
83055c685500   rcx: 0001
(XEN) [2016-07-16 16:03:17.069] rdx:    rsi:
1ab0   rdi: 8305313b85a0
(XEN) [2016-07-16 16:03:17.069] rbp: 83009fd07c78   rsp:
83009fd07c68   r8:  8305356dfff0
(XEN) [2016-07-16 16:03:17.069] r9:  8305356df480   r10:
830503420c50   r11: 0282
(XEN) [2016-07-16 16:03:17.069] r12: 8305313b8000   r13:
83009fd07e48   r14: 8305313b8000
(XEN) [2016-07-16 16:03:17.069] r15: 8305356df4a8   cr0:
80050033   cr4: 06e0
(XEN) [2016-07-16 16:03:17.069] cr3: 00053639f000   cr2:

(XEN) [2016-07-16 16:03:17.069] ds:    es:    fs:    gs:
   ss: e010   cs: e008
(XEN) [2016-07-16 16:03:17.069] Xen code around 
(msixtbl_pt_unregister+0x7b/0xd9):
(XEN) [2016-07-16 16:03:17.069]  39 42 18 74 19 48 89 ca <48> 8b 0a 
0f

18 09 48 39 fa 75 ec 48 8d 7b 24 e8
(XEN) [2016-07-16 16:03:17.069] Xen stack trace from
rsp=83009fd07c68:
(XEN) [2016-07-16 16:03:17.069] 8305356df480
83009fd07ce8 82d08014c394
(XEN) [2016-07-16 16:03:17.069]0001 8305356df480
0293 8305313b80cc
(XEN) [2016-07-16 16:03:17.069]00568012ffe5 8305313b8000
83009fd07cd8 83009fd07e38
(XEN) [2016-07-16 16:03:17.070] 83054e5fc000
7fc25a33e004 8305313b8000
(XEN) [2016-07-16 16:03:17.070]83009fd07da8 82d0801629c8
 83053b1191f0
(XEN) [2016-07-16 16:03:17.070]0246 83009fd07d28
82d0801300ae 000e
(XEN) [2016-07-16 16:03:17.070]83009fd07d78 82d080171497
83009fd07d78 00020001d17b
(XEN) [2016-07-16 16:03:17.070]83009fd07d68 
83009fd07d68 82d080130280
(XEN) [2016-07-16 16:03:17.070]83009fd07d78 82d08014d0aa
0202 
(XEN) [2016-07-16 16:03:17.070]8305313b8000 88005716d320
00305000 7fc25a33e004
(XEN) [2016-07-16 16:03:17.070]83009fd07ef8 82d080104b2c
0206 0002
(XEN) [2016-07-16 16:03:17.070]83009fd07df8 82d08018c9db
0cfe 0002
(XEN) [2016-07-16 16:03:17.070]0002 83054e5fc000
83009fd07e48 82d08019c119
(XEN) [2016-07-16 16:03:17.070]83009fd07e38 80121177
83009fd07e38 0cfe
(XEN) [2016-07-16 16:03:17.070]83009fd07f18 0206
000c0030 56082bb90013
(XEN) [2016-07-16 16:03:17.070]00020056 7fc20013
3056 56082b87465d
(XEN) [2016-07-16 16:03:17.070]7ffe268206e0 7fc25606b31f
 56082b8746cf
(XEN) [2016-07-16 16:03:17.070]1000 fee5600026820730
7ffe26820740 56082b8797be
(XEN) [2016-07-16 16:03:17.070]fee56000 430026820772
7ffe26820740 3056
(XEN) [2016-07-16 16:03:17.070]7ffe268206e0 83009ff8a000
7ffe26820580 88005716d320
(XEN) [2016-07-16 16:03:17.070] Xen call trace:
(XEN) [2016-07-16 16:03:17.070][]
msixtbl_pt_unregister+0x7b/0xd9
(XEN) [2016-07-16 16:03:17.070][]
pt_irq_destroy_bind+0x2be/0x3f0
(XEN) [2016-07-16 16:03:17.070][]
arch_do_domctl+0xc77/0x2414
(XEN) [2016-07-16 16:03:17.070][]
do_domctl+0x19db/0x1d26
(XEN) [2016-07-16 16:03:17.070][]
lstar_enter+0xdd/0x137
(XEN) [2016-07-16 16:03:17.070]
(XEN) [2016-07-16 16:03:17.070] Pagetable walk from 
:

(XEN) [2016-07-16 16:03:17.070]  L4[0x000] = 

(XEN) [2016-07-16 16:03:18.147]
(XEN) [2016-07-16 16:03:18.155] 


(XEN) [2016-07-16 16:03:18.175] Panic on CPU 0:
(XEN) [2016-07-16 16:03:18.187] FATAL PAGE FAULT
(XEN) [2016-07-16 16:03:18.200] [error_code=]
(XEN) [2016-07-16 16:03:18.214] Faulting linear address: 

(XEN) [2016-07-16 16:03:18.233] 


(XEN)

Re: [Xen-devel] Xen-unstable 4.8: Host crash when shutting down guest with pci device passed through using MSI-X interrupts.

2016-07-18 Thread Andrew Cooper

On 18/07/2016 20:26, Sander Eikelenboom wrote:
> Monday, July 18, 2016, 7:48:20 PM, you wrote:
>
>> On 18/07/16 11:21, li...@eikelenboom.it wrote:
>>> Hi Jan,
>>>
>>> It seems that since your patch series starting with commit:
>>> 2016-06-22 x86/vMSI-X: defer intercept handler registration
>>> 74c6dc2d0ac4dcab0c6243cdf6ed550c1532b798
>>>
>>> The shutdown of a guest which has a PCI device passed through which
>>> uses MSI-X interrupts causes
>>> a host crash, see the splat below. Somehow it also doesn't reboot in 5
>>> seconds as it is supposed to (i don't have no-reboot on the command
>>> line).
>>>
>>> -- 
>>> Sander
>>>
>>>
>>> (XEN) [2016-07-16 16:03:17.069] [ Xen-4.8-unstable  x86_64 
>>> debug=y  Not tainted ]
>>> (XEN) [2016-07-16 16:03:17.069] CPU:0
>>> (XEN) [2016-07-16 16:03:17.069] RIP:e008:[]
>>> msixtbl_pt_unregister+0x7b/0xd9
>>> (XEN) [2016-07-16 16:03:17.069] RFLAGS: 00010082   CONTEXT:
>>> hypervisor (d0v0)
>>> (XEN) [2016-07-16 16:03:17.069] rax: 83055c678e40   rbx:
>>> 83055c685500   rcx: 0001
>>> (XEN) [2016-07-16 16:03:17.069] rdx:    rsi:
>>> 1ab0   rdi: 8305313b85a0
>>> (XEN) [2016-07-16 16:03:17.069] rbp: 83009fd07c78   rsp:
>>> 83009fd07c68   r8:  8305356dfff0
>>> (XEN) [2016-07-16 16:03:17.069] r9:  8305356df480   r10:
>>> 830503420c50   r11: 0282
>>> (XEN) [2016-07-16 16:03:17.069] r12: 8305313b8000   r13:
>>> 83009fd07e48   r14: 8305313b8000
>>> (XEN) [2016-07-16 16:03:17.069] r15: 8305356df4a8   cr0:
>>> 80050033   cr4: 06e0
>>> (XEN) [2016-07-16 16:03:17.069] cr3: 00053639f000   cr2:
>>> 
>>> (XEN) [2016-07-16 16:03:17.069] ds:    es:    fs:    gs:
>>>    ss: e010   cs: e008
>>> (XEN) [2016-07-16 16:03:17.069] Xen code around 
>>> (msixtbl_pt_unregister+0x7b/0xd9):
>>> (XEN) [2016-07-16 16:03:17.069]  39 42 18 74 19 48 89 ca <48> 8b 0a 0f
>>> 18 09 48 39 fa 75 ec 48 8d 7b 24 e8
>>> (XEN) [2016-07-16 16:03:17.069] Xen stack trace from
>>> rsp=83009fd07c68:
>>> (XEN) [2016-07-16 16:03:17.069] 8305356df480
>>> 83009fd07ce8 82d08014c394
>>> (XEN) [2016-07-16 16:03:17.069]0001 8305356df480
>>> 0293 8305313b80cc
>>> (XEN) [2016-07-16 16:03:17.069]00568012ffe5 8305313b8000
>>> 83009fd07cd8 83009fd07e38
>>> (XEN) [2016-07-16 16:03:17.070] 83054e5fc000
>>> 7fc25a33e004 8305313b8000
>>> (XEN) [2016-07-16 16:03:17.070]83009fd07da8 82d0801629c8
>>>  83053b1191f0
>>> (XEN) [2016-07-16 16:03:17.070]0246 83009fd07d28
>>> 82d0801300ae 000e
>>> (XEN) [2016-07-16 16:03:17.070]83009fd07d78 82d080171497
>>> 83009fd07d78 00020001d17b
>>> (XEN) [2016-07-16 16:03:17.070]83009fd07d68 
>>> 83009fd07d68 82d080130280
>>> (XEN) [2016-07-16 16:03:17.070]83009fd07d78 82d08014d0aa
>>> 0202 
>>> (XEN) [2016-07-16 16:03:17.070]8305313b8000 88005716d320
>>> 00305000 7fc25a33e004
>>> (XEN) [2016-07-16 16:03:17.070]83009fd07ef8 82d080104b2c
>>> 0206 0002
>>> (XEN) [2016-07-16 16:03:17.070]83009fd07df8 82d08018c9db
>>> 0cfe 0002
>>> (XEN) [2016-07-16 16:03:17.070]0002 83054e5fc000
>>> 83009fd07e48 82d08019c119
>>> (XEN) [2016-07-16 16:03:17.070]83009fd07e38 80121177
>>> 83009fd07e38 0cfe
>>> (XEN) [2016-07-16 16:03:17.070]83009fd07f18 0206
>>> 000c0030 56082bb90013
>>> (XEN) [2016-07-16 16:03:17.070]00020056 7fc20013
>>> 3056 56082b87465d
>>> (XEN) [2016-07-16 16:03:17.070]7ffe268206e0 7fc25606b31f
>>>  56082b8746cf
>>> (XEN) [2016-07-16 16:03:17.070]1000 fee5600026820730
>>> 7ffe26820740 56082b8797be
>>> (XEN) [2016-07-16 16:03:17.070]fee56000 430026820772
>>> 7ffe26820740 3056
>>> (XEN) [2016-07-16 16:03:17.070]7ffe268206e0 83009ff8a000
>>> 7ffe26820580 88005716d320
>>> (XEN) [2016-07-16 16:03:17.070] Xen call trace:
>>> (XEN) [2016-07-16 16:03:17.070][]
>>> msixtbl_pt_unregister+0x7b/0xd9
>>> (XEN) [2016-07-16 16:03:17.070][]
>>> pt_irq_destroy_bind+0x2be/0x3f0
>>> (XEN) [2016-07-16 16:03:17.070][]
>>> arch_do_domctl+0xc77/0x2414
>>> (XEN) [2016-07-16 16:03:17.070][]
>>> do_domctl+0x19db/0x1d26
>>> (XEN) [2016-07-16 16:03:17.070][]
>>> lstar_enter+0xdd/0x137
>>> (XEN) [2016-07-16 16:03:17.070]
>>> (XEN) [2016-07-16 16:03:17.070] Pagetable walk from :
>>> (XEN) [2016-07-16 16:03:17.070]  L4[0x000] = 
>>> 
>>> (XEN) [2016-07-16 16:03:18.147]
>>> (XEN) [2016-07-16

Re: [Xen-devel] Xen-unstable 4.8: Host crash when shutting down guest with pci device passed through using MSI-X interrupts.

2016-07-18 Thread Sander Eikelenboom


Monday, July 18, 2016, 7:48:20 PM, you wrote:

> On 18/07/16 11:21, li...@eikelenboom.it wrote:
>> Hi Jan,
>>
>> It seems that since your patch series starting with commit:
>> 2016-06-22 x86/vMSI-X: defer intercept handler registration
>> 74c6dc2d0ac4dcab0c6243cdf6ed550c1532b798
>>
>> The shutdown of a guest which has a PCI device passed through which
>> uses MSI-X interrupts causes
>> a host crash, see the splat below. Somehow it also doesn't reboot in 5
>> seconds as it is supposed to (i don't have no-reboot on the command
>> line).
>>
>> -- 
>> Sander
>>
>>
>> (XEN) [2016-07-16 16:03:17.069] [ Xen-4.8-unstable  x86_64 
>> debug=y  Not tainted ]
>> (XEN) [2016-07-16 16:03:17.069] CPU:0
>> (XEN) [2016-07-16 16:03:17.069] RIP:e008:[]
>> msixtbl_pt_unregister+0x7b/0xd9
>> (XEN) [2016-07-16 16:03:17.069] RFLAGS: 00010082   CONTEXT:
>> hypervisor (d0v0)
>> (XEN) [2016-07-16 16:03:17.069] rax: 83055c678e40   rbx:
>> 83055c685500   rcx: 0001
>> (XEN) [2016-07-16 16:03:17.069] rdx:    rsi:
>> 1ab0   rdi: 8305313b85a0
>> (XEN) [2016-07-16 16:03:17.069] rbp: 83009fd07c78   rsp:
>> 83009fd07c68   r8:  8305356dfff0
>> (XEN) [2016-07-16 16:03:17.069] r9:  8305356df480   r10:
>> 830503420c50   r11: 0282
>> (XEN) [2016-07-16 16:03:17.069] r12: 8305313b8000   r13:
>> 83009fd07e48   r14: 8305313b8000
>> (XEN) [2016-07-16 16:03:17.069] r15: 8305356df4a8   cr0:
>> 80050033   cr4: 06e0
>> (XEN) [2016-07-16 16:03:17.069] cr3: 00053639f000   cr2:
>> 
>> (XEN) [2016-07-16 16:03:17.069] ds:    es:    fs:    gs:
>>    ss: e010   cs: e008
>> (XEN) [2016-07-16 16:03:17.069] Xen code around 
>> (msixtbl_pt_unregister+0x7b/0xd9):
>> (XEN) [2016-07-16 16:03:17.069]  39 42 18 74 19 48 89 ca <48> 8b 0a 0f
>> 18 09 48 39 fa 75 ec 48 8d 7b 24 e8
>> (XEN) [2016-07-16 16:03:17.069] Xen stack trace from
>> rsp=83009fd07c68:
>> (XEN) [2016-07-16 16:03:17.069] 8305356df480
>> 83009fd07ce8 82d08014c394
>> (XEN) [2016-07-16 16:03:17.069]0001 8305356df480
>> 0293 8305313b80cc
>> (XEN) [2016-07-16 16:03:17.069]00568012ffe5 8305313b8000
>> 83009fd07cd8 83009fd07e38
>> (XEN) [2016-07-16 16:03:17.070] 83054e5fc000
>> 7fc25a33e004 8305313b8000
>> (XEN) [2016-07-16 16:03:17.070]83009fd07da8 82d0801629c8
>>  83053b1191f0
>> (XEN) [2016-07-16 16:03:17.070]0246 83009fd07d28
>> 82d0801300ae 000e
>> (XEN) [2016-07-16 16:03:17.070]83009fd07d78 82d080171497
>> 83009fd07d78 00020001d17b
>> (XEN) [2016-07-16 16:03:17.070]83009fd07d68 
>> 83009fd07d68 82d080130280
>> (XEN) [2016-07-16 16:03:17.070]83009fd07d78 82d08014d0aa
>> 0202 
>> (XEN) [2016-07-16 16:03:17.070]8305313b8000 88005716d320
>> 00305000 7fc25a33e004
>> (XEN) [2016-07-16 16:03:17.070]83009fd07ef8 82d080104b2c
>> 0206 0002
>> (XEN) [2016-07-16 16:03:17.070]83009fd07df8 82d08018c9db
>> 0cfe 0002
>> (XEN) [2016-07-16 16:03:17.070]0002 83054e5fc000
>> 83009fd07e48 82d08019c119
>> (XEN) [2016-07-16 16:03:17.070]83009fd07e38 80121177
>> 83009fd07e38 0cfe
>> (XEN) [2016-07-16 16:03:17.070]83009fd07f18 0206
>> 000c0030 56082bb90013
>> (XEN) [2016-07-16 16:03:17.070]00020056 7fc20013
>> 3056 56082b87465d
>> (XEN) [2016-07-16 16:03:17.070]7ffe268206e0 7fc25606b31f
>>  56082b8746cf
>> (XEN) [2016-07-16 16:03:17.070]1000 fee5600026820730
>> 7ffe26820740 56082b8797be
>> (XEN) [2016-07-16 16:03:17.070]fee56000 430026820772
>> 7ffe26820740 3056
>> (XEN) [2016-07-16 16:03:17.070]7ffe268206e0 83009ff8a000
>> 7ffe26820580 88005716d320
>> (XEN) [2016-07-16 16:03:17.070] Xen call trace:
>> (XEN) [2016-07-16 16:03:17.070][]
>> msixtbl_pt_unregister+0x7b/0xd9
>> (XEN) [2016-07-16 16:03:17.070][]
>> pt_irq_destroy_bind+0x2be/0x3f0
>> (XEN) [2016-07-16 16:03:17.070][]
>> arch_do_domctl+0xc77/0x2414
>> (XEN) [2016-07-16 16:03:17.070][]
>> do_domctl+0x19db/0x1d26
>> (XEN) [2016-07-16 16:03:17.070][]
>> lstar_enter+0xdd/0x137
>> (XEN) [2016-07-16 16:03:17.070]
>> (XEN) [2016-07-16 16:03:17.070] Pagetable walk from :
>> (XEN) [2016-07-16 16:03:17.070]  L4[0x000] = 
>> 
>> (XEN) [2016-07-16 16:03:18.147]
>> (XEN) [2016-07-16 16:03:18.155] 
>> (XEN) [2016-07-16 16:03:18.175] Panic on CPU 0:
>> (XEN) [2016-07-16 16:03:18.187] FATAL PAGE

Re: [Xen-devel] Xen-unstable 4.8: Host crash when shutting down guest with pci device passed through using MSI-X interrupts.

2016-07-18 Thread Andrew Cooper

On 18/07/16 11:21, li...@eikelenboom.it wrote:
> Hi Jan,
>
> It seems that since your patch series starting with commit:
> 2016-06-22 x86/vMSI-X: defer intercept handler registration
> 74c6dc2d0ac4dcab0c6243cdf6ed550c1532b798
>
> The shutdown of a guest which has a PCI device passed through which
> uses MSI-X interrupts causes
> a host crash, see the splat below. Somehow it also doesn't reboot in 5
> seconds as it is supposed to (i don't have no-reboot on the command
> line).
>
> -- 
> Sander
>
>
> (XEN) [2016-07-16 16:03:17.069] [ Xen-4.8-unstable  x86_64 
> debug=y  Not tainted ]
> (XEN) [2016-07-16 16:03:17.069] CPU:0
> (XEN) [2016-07-16 16:03:17.069] RIP:e008:[]
> msixtbl_pt_unregister+0x7b/0xd9
> (XEN) [2016-07-16 16:03:17.069] RFLAGS: 00010082   CONTEXT:
> hypervisor (d0v0)
> (XEN) [2016-07-16 16:03:17.069] rax: 83055c678e40   rbx:
> 83055c685500   rcx: 0001
> (XEN) [2016-07-16 16:03:17.069] rdx:    rsi:
> 1ab0   rdi: 8305313b85a0
> (XEN) [2016-07-16 16:03:17.069] rbp: 83009fd07c78   rsp:
> 83009fd07c68   r8:  8305356dfff0
> (XEN) [2016-07-16 16:03:17.069] r9:  8305356df480   r10:
> 830503420c50   r11: 0282
> (XEN) [2016-07-16 16:03:17.069] r12: 8305313b8000   r13:
> 83009fd07e48   r14: 8305313b8000
> (XEN) [2016-07-16 16:03:17.069] r15: 8305356df4a8   cr0:
> 80050033   cr4: 06e0
> (XEN) [2016-07-16 16:03:17.069] cr3: 00053639f000   cr2:
> 
> (XEN) [2016-07-16 16:03:17.069] ds:    es:    fs:    gs:
>    ss: e010   cs: e008
> (XEN) [2016-07-16 16:03:17.069] Xen code around 
> (msixtbl_pt_unregister+0x7b/0xd9):
> (XEN) [2016-07-16 16:03:17.069]  39 42 18 74 19 48 89 ca <48> 8b 0a 0f
> 18 09 48 39 fa 75 ec 48 8d 7b 24 e8
> (XEN) [2016-07-16 16:03:17.069] Xen stack trace from
> rsp=83009fd07c68:
> (XEN) [2016-07-16 16:03:17.069] 8305356df480
> 83009fd07ce8 82d08014c394
> (XEN) [2016-07-16 16:03:17.069]0001 8305356df480
> 0293 8305313b80cc
> (XEN) [2016-07-16 16:03:17.069]00568012ffe5 8305313b8000
> 83009fd07cd8 83009fd07e38
> (XEN) [2016-07-16 16:03:17.070] 83054e5fc000
> 7fc25a33e004 8305313b8000
> (XEN) [2016-07-16 16:03:17.070]83009fd07da8 82d0801629c8
>  83053b1191f0
> (XEN) [2016-07-16 16:03:17.070]0246 83009fd07d28
> 82d0801300ae 000e
> (XEN) [2016-07-16 16:03:17.070]83009fd07d78 82d080171497
> 83009fd07d78 00020001d17b
> (XEN) [2016-07-16 16:03:17.070]83009fd07d68 
> 83009fd07d68 82d080130280
> (XEN) [2016-07-16 16:03:17.070]83009fd07d78 82d08014d0aa
> 0202 
> (XEN) [2016-07-16 16:03:17.070]8305313b8000 88005716d320
> 00305000 7fc25a33e004
> (XEN) [2016-07-16 16:03:17.070]83009fd07ef8 82d080104b2c
> 0206 0002
> (XEN) [2016-07-16 16:03:17.070]83009fd07df8 82d08018c9db
> 0cfe 0002
> (XEN) [2016-07-16 16:03:17.070]0002 83054e5fc000
> 83009fd07e48 82d08019c119
> (XEN) [2016-07-16 16:03:17.070]83009fd07e38 80121177
> 83009fd07e38 0cfe
> (XEN) [2016-07-16 16:03:17.070]83009fd07f18 0206
> 000c0030 56082bb90013
> (XEN) [2016-07-16 16:03:17.070]00020056 7fc20013
> 3056 56082b87465d
> (XEN) [2016-07-16 16:03:17.070]7ffe268206e0 7fc25606b31f
>  56082b8746cf
> (XEN) [2016-07-16 16:03:17.070]1000 fee5600026820730
> 7ffe26820740 56082b8797be
> (XEN) [2016-07-16 16:03:17.070]fee56000 430026820772
> 7ffe26820740 3056
> (XEN) [2016-07-16 16:03:17.070]7ffe268206e0 83009ff8a000
> 7ffe26820580 88005716d320
> (XEN) [2016-07-16 16:03:17.070] Xen call trace:
> (XEN) [2016-07-16 16:03:17.070][]
> msixtbl_pt_unregister+0x7b/0xd9
> (XEN) [2016-07-16 16:03:17.070][]
> pt_irq_destroy_bind+0x2be/0x3f0
> (XEN) [2016-07-16 16:03:17.070][]
> arch_do_domctl+0xc77/0x2414
> (XEN) [2016-07-16 16:03:17.070][]
> do_domctl+0x19db/0x1d26
> (XEN) [2016-07-16 16:03:17.070][]
> lstar_enter+0xdd/0x137
> (XEN) [2016-07-16 16:03:17.070]
> (XEN) [2016-07-16 16:03:17.070] Pagetable walk from :
> (XEN) [2016-07-16 16:03:17.070]  L4[0x000] = 
> 
> (XEN) [2016-07-16 16:03:18.147]
> (XEN) [2016-07-16 16:03:18.155] 
> (XEN) [2016-07-16 16:03:18.175] Panic on CPU 0:
> (XEN) [2016-07-16 16:03:18.187] FATAL PAGE FAULT
> (XEN) [2016-07-16 16:03:18.200] [error_code=]
> (XEN) [2016-07-16 16:03:18.214] Faulting linear address: 
> (XEN) [2016-07-16

[Xen-devel] Xen-unstable 4.8: Host crash when shutting down guest with pci device passed through using MSI-X interrupts.

2016-07-18 Thread linux


Hi Jan,

It seems that since your patch series starting with commit:
2016-06-22 x86/vMSI-X: defer intercept handler registration
74c6dc2d0ac4dcab0c6243cdf6ed550c1532b798

The shutdown of a guest which has a PCI device passed through which uses 
MSI-X interrupts causes
a host crash, see the splat below. Somehow it also doesn't reboot in 5 
seconds as it is supposed to (i don't have no-reboot on the command 
line).


--
Sander


(XEN) [2016-07-16 16:03:17.069] [ Xen-4.8-unstable  x86_64  debug=y  
Not tainted ]

(XEN) [2016-07-16 16:03:17.069] CPU:0
(XEN) [2016-07-16 16:03:17.069] RIP:e008:[] 
msixtbl_pt_unregister+0x7b/0xd9
(XEN) [2016-07-16 16:03:17.069] RFLAGS: 00010082   CONTEXT: 
hypervisor (d0v0)
(XEN) [2016-07-16 16:03:17.069] rax: 83055c678e40   rbx: 
83055c685500   rcx: 0001
(XEN) [2016-07-16 16:03:17.069] rdx:    rsi: 
1ab0   rdi: 8305313b85a0
(XEN) [2016-07-16 16:03:17.069] rbp: 83009fd07c78   rsp: 
83009fd07c68   r8:  8305356dfff0
(XEN) [2016-07-16 16:03:17.069] r9:  8305356df480   r10: 
830503420c50   r11: 0282
(XEN) [2016-07-16 16:03:17.069] r12: 8305313b8000   r13: 
83009fd07e48   r14: 8305313b8000
(XEN) [2016-07-16 16:03:17.069] r15: 8305356df4a8   cr0: 
80050033   cr4: 06e0
(XEN) [2016-07-16 16:03:17.069] cr3: 00053639f000   cr2: 

(XEN) [2016-07-16 16:03:17.069] ds:    es:    fs:    gs: 
   ss: e010   cs: e008
(XEN) [2016-07-16 16:03:17.069] Xen code around  
(msixtbl_pt_unregister+0x7b/0xd9):
(XEN) [2016-07-16 16:03:17.069]  39 42 18 74 19 48 89 ca <48> 8b 0a 0f 
18 09 48 39 fa 75 ec 48 8d 7b 24 e8
(XEN) [2016-07-16 16:03:17.069] Xen stack trace from 
rsp=83009fd07c68:
(XEN) [2016-07-16 16:03:17.069] 8305356df480 
83009fd07ce8 82d08014c394
(XEN) [2016-07-16 16:03:17.069]0001 8305356df480 
0293 8305313b80cc
(XEN) [2016-07-16 16:03:17.069]00568012ffe5 8305313b8000 
83009fd07cd8 83009fd07e38
(XEN) [2016-07-16 16:03:17.070] 83054e5fc000 
7fc25a33e004 8305313b8000
(XEN) [2016-07-16 16:03:17.070]83009fd07da8 82d0801629c8 
 83053b1191f0
(XEN) [2016-07-16 16:03:17.070]0246 83009fd07d28 
82d0801300ae 000e
(XEN) [2016-07-16 16:03:17.070]83009fd07d78 82d080171497 
83009fd07d78 00020001d17b
(XEN) [2016-07-16 16:03:17.070]83009fd07d68  
83009fd07d68 82d080130280
(XEN) [2016-07-16 16:03:17.070]83009fd07d78 82d08014d0aa 
0202 
(XEN) [2016-07-16 16:03:17.070]8305313b8000 88005716d320 
00305000 7fc25a33e004
(XEN) [2016-07-16 16:03:17.070]83009fd07ef8 82d080104b2c 
0206 0002
(XEN) [2016-07-16 16:03:17.070]83009fd07df8 82d08018c9db 
0cfe 0002
(XEN) [2016-07-16 16:03:17.070]0002 83054e5fc000 
83009fd07e48 82d08019c119
(XEN) [2016-07-16 16:03:17.070]83009fd07e38 80121177 
83009fd07e38 0cfe
(XEN) [2016-07-16 16:03:17.070]83009fd07f18 0206 
000c0030 56082bb90013
(XEN) [2016-07-16 16:03:17.070]00020056 7fc20013 
3056 56082b87465d
(XEN) [2016-07-16 16:03:17.070]7ffe268206e0 7fc25606b31f 
 56082b8746cf
(XEN) [2016-07-16 16:03:17.070]1000 fee5600026820730 
7ffe26820740 56082b8797be
(XEN) [2016-07-16 16:03:17.070]fee56000 430026820772 
7ffe26820740 3056
(XEN) [2016-07-16 16:03:17.070]7ffe268206e0 83009ff8a000 
7ffe26820580 88005716d320

(XEN) [2016-07-16 16:03:17.070] Xen call trace:
(XEN) [2016-07-16 16:03:17.070][] 
msixtbl_pt_unregister+0x7b/0xd9
(XEN) [2016-07-16 16:03:17.070][] 
pt_irq_destroy_bind+0x2be/0x3f0
(XEN) [2016-07-16 16:03:17.070][] 
arch_do_domctl+0xc77/0x2414
(XEN) [2016-07-16 16:03:17.070][] 
do_domctl+0x19db/0x1d26
(XEN) [2016-07-16 16:03:17.070][] 
lstar_enter+0xdd/0x137

(XEN) [2016-07-16 16:03:17.070]
(XEN) [2016-07-16 16:03:17.070] Pagetable walk from :
(XEN) [2016-07-16 16:03:17.070]  L4[0x000] =  


(XEN) [2016-07-16 16:03:18.147]
(XEN) [2016-07-16 16:03:18.155] 
(XEN) [2016-07-16 16:03:18.175] Panic on CPU 0:
(XEN) [2016-07-16 16:03:18.187] FATAL PAGE FAULT
(XEN) [2016-07-16 16:03:18.200] [error_code=]
(XEN) [2016-07-16 16:03:18.214] Faulting linear address: 


(XEN) [2016-07-16 16:03:18.233] 
(XEN) [2016-07-16 16:03:18.252]
(XEN) [2016-07-16 16:03:18.261] Reboot in five seconds...


___
Xen-devel

Re: [Xen-devel] Xen-unstable 4.8: Host crash when shutting down guest with pci device passed through using MSI-X interrupts.

Re: [Xen-devel] Xen-unstable 4.8: Host crash when shutting down guest with pci device passed through using MSI-X interrupts.

Re: [Xen-devel] Xen-unstable 4.8: Host crash when shutting down guest with pci device passed through using MSI-X interrupts.

Re: [Xen-devel] Xen-unstable 4.8: Host crash when shutting down guest with pci device passed through using MSI-X interrupts.

Re: [Xen-devel] Xen-unstable 4.8: Host crash when shutting down guest with pci device passed through using MSI-X interrupts.

[Xen-devel] Xen-unstable 4.8: Host crash when shutting down guest with pci device passed through using MSI-X interrupts.

6 matches

Site Navigation

Mail list logo

Footer information