thr3ads.net - Xen devel - [bug 1868] dom0 will panic when pcibacking a vt-d device on IVT-EP [Jul 2013]

If this information is useful, please help other people find it:
Share via:

Liu, SongtaoX

2013-Jul-17 08:51 UTC

[bug 1868] dom0 will panic when pcibacking a vt-d device on IVT-EP

Hi, all,
c/s 27239:807bde93934d introduced a new bug, dom0 will panic when pcibacking a
vt-d device on IVT-EP.
as: http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1868

author    Jan Beulich <jbeulich@suse.com>
date    Mon Jul 15 14:17:56 2013 +0200 (39 hours ago)
parents    6542a6b34d7b
children    e539f83fc9b1
files    xen/arch/x86/mm.c xen/arch/x86/msi.c xen/arch/x86/x86_64/mm.c
xen/include/asm-x86/page.h

Reproduce steps:
----------------
1. boot up dom0, 
2. run "xl pci-assignable-add $vt-d_BDF"
3. dom0 will panic

panic log:
(XEN) ----[ Xen-4.4-unstable  x86_64  debug=y  Not tainted ]----
(XEN) CPU:    25
(XEN) RIP:    e008:[<ffff82d080160634>] flush_area_local+0x116/0x140
(XEN) RFLAGS: 0000000000010002   CONTEXT: hypervisor
(XEN) rax: 0000000000001000   rbx: 0000000000000701   rcx: 0000000000000040
(XEN) rdx: 0000000000000000   rsi: 0000000000000004   rdi: ffff82cfffd4d000
(XEN) rbp: ffff830839abfc78   rsp: ffff830839abfc38   r8:  ffff8300ba470ff0
(XEN) r9:  0000000000000038   r10: ffff82d08022dba0   r11: 0000000000000202
(XEN) r12: 0000000000000000   r13: 0000000000000246   r14: ffff82cfffd4d000
(XEN) r15: ffff82d0802f5e00   cr0: 0000000080050033   cr4: 00000000001426f0
(XEN) cr3: 000000084c557000   cr2: ffff82cfffd4d000
(XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e010   cs: e008
(XEN) Xen stack trace from rsp=ffff830839abfc38:
(XEN)    000000ff00dd00b3 0000000000000000 0000000000000000 ffff82d080264d80
(XEN)    ffff82cfffd4d000 0000000000000701 0000000000000001 ffff8300ba4729f8
(XEN)    ffff830839abfca8 ffff82d08017fba4 0000000000000000 0000000000000000
(XEN)    00000000ba470063 ffff82cfffd4d000 ffff830839abfd38 ffff82d08016ff7a
(XEN)    ffff830839abfcc8 0000000000000000 0000000000000080 0000000000000000
(XEN)    0000000000000000 0100000000000000 ffff83083980b324 000ffff82cfffd4d
(XEN)    0000000000000000 ffff8300ba470ff0 0000000000000000 ffff8304bb825f70
(XEN)    0000000000000000 00000000000002b2 ffff83083998a790 ffff83083998a830
(XEN)    ffff830839abfd48 ffff82d0801707f8 ffff830839abfd88 ffff82d080167841
(XEN)    00000000000000df ffff8304bb824080 00000000000000de ffff830839a77000
(XEN)    00000000000000b3 ffff83083980b300 ffff830839abfe08 ffff82d08016b880
(XEN)    0000000000000cfc 0000000000000296 00000000000000b3 ffff8304bb825f70
(XEN)    00000000000000de ffff82d080186100 ffff830839a771b0 ffff83083980b324
(XEN)    ffff830839abff18 ffff830839a77000 00000000fffffffd ffff830839a77198
(XEN)    00000000000000de 0000000000000001 ffff830839abfe48 ffff82d08017dbd9
(XEN)    ffff830839abfe68 000000000000000e ffff8800b20cdc58 ffff8300ba2e3000
(XEN)    0000000000000001 0000000000000001 ffff830839abfef8 ffff82d08017e81b
(XEN)    ffff8801004038c0 ffff8800b29a1a00 000000de00007ff0 ffff82d08017fe99
(XEN)    ffff830839abff08 ffff82d080169611 aaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaa
(XEN)    aaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaa aaaaaaaaaaaaaaef aaaaaaaaaaaaaaaa
(XEN) Xen call trace:
(XEN)    [<ffff82d080160634>] flush_area_local+0x116/0x140
(XEN)    [<ffff82d08017fba4>] flush_area_mask+0x67/0x15b
(XEN)    [<ffff82d08016ff7a>] map_pages_to_xen+0xb2b/0xffd
(XEN)    [<ffff82d0801707f8>] __set_fixmap+0x34/0x36
(XEN)    [<ffff82d080167841>] msi_free_irq+0xe1/0x1ae
(XEN)    [<ffff82d08016b880>] unmap_domain_pirq+0x304/0x38e
(XEN)    [<ffff82d08017dbd9>] physdev_unmap_pirq+0xf9/0x16d
(XEN)    [<ffff82d08017e81b>] do_physdev_op+0x6df/0x1128
(XEN)    [<ffff82d08022304b>] syscall_enter+0xeb/0x145
(XEN)    
(XEN) Pagetable walk from ffff82cfffd4d000:
(XEN)  L4[0x105] = 00000000ba472063 ffffffffffffffff
(XEN)  L3[0x13f] = 00000000ba470063 ffffffffffffffff
(XEN)  L2[0x1fe] = 00000000ba7e6063 ffffffffffffffff 
(XEN)  L1[0x14d] = 0000000000000000 ffffffffffffffff
(XEN) 
(XEN) ****************************************
(XEN) Panic on CPU 25:
(XEN) FATAL PAGE FAULT
(XEN) [error_code=0000]
(XEN) Faulting linear address: ffff82cfffd4d000
(XEN) ****************************************
(XEN) 
(XEN) Reboot in five seconds...
(XEN) Resetting with ACPI MEMORY or I/O RESET_REG.

Regards
Carl(Songtao)

Jan Beulich

2013-Jul-17 14:15 UTC

head link

Re: [bug 1868] dom0 will panic when pcibacking a vt-d device on IVT-EP

>>> On 17.07.13 at 10:51, "Liu, SongtaoX"
<songtaox.liu@intel.com> wrote:
> Hi, all,
> c/s 27239:807bde93934d introduced a new bug, dom0 will panic when
pcibacking
> a vt-d device on IVT-EP.
> as: http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1868 
> 
> author    Jan Beulich <jbeulich@suse.com>
> date    Mon Jul 15 14:17:56 2013 +0200 (39 hours ago)
> parents    6542a6b34d7b
> children    e539f83fc9b1
> files    xen/arch/x86/mm.c xen/arch/x86/msi.c xen/arch/x86/x86_64/mm.c
> xen/include/asm-x86/page.h
> 
> Reproduce steps:
> ----------------
> 1. boot up dom0, 
> 2. run "xl pci-assignable-add $vt-d_BDF"
> 3. dom0 will panic
Just found a box where a similar crash happens during shutdown or
reboot. Debugging...

Jan
> panic log:
> (XEN) ----[ Xen-4.4-unstable  x86_64  debug=y  Not tainted ]----
> (XEN) CPU:    25
> (XEN) RIP:    e008:[<ffff82d080160634>] flush_area_local+0x116/0x140
> (XEN) RFLAGS: 0000000000010002   CONTEXT: hypervisor
> (XEN) rax: 0000000000001000   rbx: 0000000000000701   rcx: 0000000000000040
> (XEN) rdx: 0000000000000000   rsi: 0000000000000004   rdi: ffff82cfffd4d000
> (XEN) rbp: ffff830839abfc78   rsp: ffff830839abfc38   r8:  ffff8300ba470ff0
> (XEN) r9:  0000000000000038   r10: ffff82d08022dba0   r11: 0000000000000202
> (XEN) r12: 0000000000000000   r13: 0000000000000246   r14: ffff82cfffd4d000
> (XEN) r15: ffff82d0802f5e00   cr0: 0000000080050033   cr4: 00000000001426f0
> (XEN) cr3: 000000084c557000   cr2: ffff82cfffd4d000
> (XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e010   cs: e008
> (XEN) Xen stack trace from rsp=ffff830839abfc38:
> (XEN)    000000ff00dd00b3 0000000000000000 0000000000000000
ffff82d080264d80
> (XEN)    ffff82cfffd4d000 0000000000000701 0000000000000001
ffff8300ba4729f8
> (XEN)    ffff830839abfca8 ffff82d08017fba4 0000000000000000
0000000000000000
> (XEN)    00000000ba470063 ffff82cfffd4d000 ffff830839abfd38
ffff82d08016ff7a
> (XEN)    ffff830839abfcc8 0000000000000000 0000000000000080
0000000000000000
> (XEN)    0000000000000000 0100000000000000 ffff83083980b324
000ffff82cfffd4d
> (XEN)    0000000000000000 ffff8300ba470ff0 0000000000000000
ffff8304bb825f70
> (XEN)    0000000000000000 00000000000002b2 ffff83083998a790
ffff83083998a830
> (XEN)    ffff830839abfd48 ffff82d0801707f8 ffff830839abfd88
ffff82d080167841
> (XEN)    00000000000000df ffff8304bb824080 00000000000000de
ffff830839a77000
> (XEN)    00000000000000b3 ffff83083980b300 ffff830839abfe08
ffff82d08016b880
> (XEN)    0000000000000cfc 0000000000000296 00000000000000b3
ffff8304bb825f70
> (XEN)    00000000000000de ffff82d080186100 ffff830839a771b0
ffff83083980b324
> (XEN)    ffff830839abff18 ffff830839a77000 00000000fffffffd
ffff830839a77198
> (XEN)    00000000000000de 0000000000000001 ffff830839abfe48
ffff82d08017dbd9
> (XEN)    ffff830839abfe68 000000000000000e ffff8800b20cdc58
ffff8300ba2e3000
> (XEN)    0000000000000001 0000000000000001 ffff830839abfef8
ffff82d08017e81b
> (XEN)    ffff8801004038c0 ffff8800b29a1a00 000000de00007ff0
ffff82d08017fe99
> (XEN)    ffff830839abff08 ffff82d080169611 aaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaa
> (XEN)    aaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaa aaaaaaaaaaaaaaef
aaaaaaaaaaaaaaaa
> (XEN) Xen call trace:
> (XEN)    [<ffff82d080160634>] flush_area_local+0x116/0x140
> (XEN)    [<ffff82d08017fba4>] flush_area_mask+0x67/0x15b
> (XEN)    [<ffff82d08016ff7a>] map_pages_to_xen+0xb2b/0xffd
> (XEN)    [<ffff82d0801707f8>] __set_fixmap+0x34/0x36
> (XEN)    [<ffff82d080167841>] msi_free_irq+0xe1/0x1ae
> (XEN)    [<ffff82d08016b880>] unmap_domain_pirq+0x304/0x38e
> (XEN)    [<ffff82d08017dbd9>] physdev_unmap_pirq+0xf9/0x16d
> (XEN)    [<ffff82d08017e81b>] do_physdev_op+0x6df/0x1128
> (XEN)    [<ffff82d08022304b>] syscall_enter+0xeb/0x145
> (XEN)    
> (XEN) Pagetable walk from ffff82cfffd4d000:
> (XEN)  L4[0x105] = 00000000ba472063 ffffffffffffffff
> (XEN)  L3[0x13f] = 00000000ba470063 ffffffffffffffff
> (XEN)  L2[0x1fe] = 00000000ba7e6063 ffffffffffffffff 
> (XEN)  L1[0x14d] = 0000000000000000 ffffffffffffffff
> (XEN) 
> (XEN) ****************************************
> (XEN) Panic on CPU 25:
> (XEN) FATAL PAGE FAULT
> (XEN) [error_code=0000]
> (XEN) Faulting linear address: ffff82cfffd4d000
> (XEN) ****************************************
> (XEN) 
> (XEN) Reboot in five seconds...
> (XEN) Resetting with ACPI MEMORY or I/O RESET_REG.
> 
> Regards
> Carl(Songtao)

Jan Beulich

2013-Jul-17 15:10 UTC

head link

Re: [bug 1868] dom0 will panic when pcibacking a vt-d device on IVT-EP

>>> On 17.07.13 at 10:51, "Liu, SongtaoX"
<songtaox.liu@intel.com> wrote:
> Hi, all,
> c/s 27239:807bde93934d introduced a new bug, dom0 will panic when
pcibacking
> a vt-d device on IVT-EP.
> as: http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1868 
> 
> author    Jan Beulich <jbeulich@suse.com>
> date    Mon Jul 15 14:17:56 2013 +0200 (39 hours ago)
> parents    6542a6b34d7b
> children    e539f83fc9b1
> files    xen/arch/x86/mm.c xen/arch/x86/msi.c xen/arch/x86/x86_64/mm.c
> xen/include/asm-x86/page.h
> 
> Reproduce steps:
> ----------------
> 1. boot up dom0, 
> 2. run "xl pci-assignable-add $vt-d_BDF"
> 3. dom0 will panic
Should be fixed by
http://lists.xenproject.org/archives/html/xen-devel/2013-07/msg01573.html

Jan
> panic log:
> (XEN) ----[ Xen-4.4-unstable  x86_64  debug=y  Not tainted ]----
> (XEN) CPU:    25
> (XEN) RIP:    e008:[<ffff82d080160634>] flush_area_local+0x116/0x140
> (XEN) RFLAGS: 0000000000010002   CONTEXT: hypervisor
> (XEN) rax: 0000000000001000   rbx: 0000000000000701   rcx: 0000000000000040
> (XEN) rdx: 0000000000000000   rsi: 0000000000000004   rdi: ffff82cfffd4d000
> (XEN) rbp: ffff830839abfc78   rsp: ffff830839abfc38   r8:  ffff8300ba470ff0
> (XEN) r9:  0000000000000038   r10: ffff82d08022dba0   r11: 0000000000000202
> (XEN) r12: 0000000000000000   r13: 0000000000000246   r14: ffff82cfffd4d000
> (XEN) r15: ffff82d0802f5e00   cr0: 0000000080050033   cr4: 00000000001426f0
> (XEN) cr3: 000000084c557000   cr2: ffff82cfffd4d000
> (XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e010   cs: e008
> (XEN) Xen stack trace from rsp=ffff830839abfc38:
> (XEN)    000000ff00dd00b3 0000000000000000 0000000000000000
ffff82d080264d80
> (XEN)    ffff82cfffd4d000 0000000000000701 0000000000000001
ffff8300ba4729f8
> (XEN)    ffff830839abfca8 ffff82d08017fba4 0000000000000000
0000000000000000
> (XEN)    00000000ba470063 ffff82cfffd4d000 ffff830839abfd38
ffff82d08016ff7a
> (XEN)    ffff830839abfcc8 0000000000000000 0000000000000080
0000000000000000
> (XEN)    0000000000000000 0100000000000000 ffff83083980b324
000ffff82cfffd4d
> (XEN)    0000000000000000 ffff8300ba470ff0 0000000000000000
ffff8304bb825f70
> (XEN)    0000000000000000 00000000000002b2 ffff83083998a790
ffff83083998a830
> (XEN)    ffff830839abfd48 ffff82d0801707f8 ffff830839abfd88
ffff82d080167841
> (XEN)    00000000000000df ffff8304bb824080 00000000000000de
ffff830839a77000
> (XEN)    00000000000000b3 ffff83083980b300 ffff830839abfe08
ffff82d08016b880
> (XEN)    0000000000000cfc 0000000000000296 00000000000000b3
ffff8304bb825f70
> (XEN)    00000000000000de ffff82d080186100 ffff830839a771b0
ffff83083980b324
> (XEN)    ffff830839abff18 ffff830839a77000 00000000fffffffd
ffff830839a77198
> (XEN)    00000000000000de 0000000000000001 ffff830839abfe48
ffff82d08017dbd9
> (XEN)    ffff830839abfe68 000000000000000e ffff8800b20cdc58
ffff8300ba2e3000
> (XEN)    0000000000000001 0000000000000001 ffff830839abfef8
ffff82d08017e81b
> (XEN)    ffff8801004038c0 ffff8800b29a1a00 000000de00007ff0
ffff82d08017fe99
> (XEN)    ffff830839abff08 ffff82d080169611 aaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaa
> (XEN)    aaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaa aaaaaaaaaaaaaaef
aaaaaaaaaaaaaaaa
> (XEN) Xen call trace:
> (XEN)    [<ffff82d080160634>] flush_area_local+0x116/0x140
> (XEN)    [<ffff82d08017fba4>] flush_area_mask+0x67/0x15b
> (XEN)    [<ffff82d08016ff7a>] map_pages_to_xen+0xb2b/0xffd
> (XEN)    [<ffff82d0801707f8>] __set_fixmap+0x34/0x36
> (XEN)    [<ffff82d080167841>] msi_free_irq+0xe1/0x1ae
> (XEN)    [<ffff82d08016b880>] unmap_domain_pirq+0x304/0x38e
> (XEN)    [<ffff82d08017dbd9>] physdev_unmap_pirq+0xf9/0x16d
> (XEN)    [<ffff82d08017e81b>] do_physdev_op+0x6df/0x1128
> (XEN)    [<ffff82d08022304b>] syscall_enter+0xeb/0x145
> (XEN)    
> (XEN) Pagetable walk from ffff82cfffd4d000:
> (XEN)  L4[0x105] = 00000000ba472063 ffffffffffffffff
> (XEN)  L3[0x13f] = 00000000ba470063 ffffffffffffffff
> (XEN)  L2[0x1fe] = 00000000ba7e6063 ffffffffffffffff 
> (XEN)  L1[0x14d] = 0000000000000000 ffffffffffffffff
> (XEN) 
> (XEN) ****************************************
> (XEN) Panic on CPU 25:
> (XEN) FATAL PAGE FAULT
> (XEN) [error_code=0000]
> (XEN) Faulting linear address: ffff82cfffd4d000
> (XEN) ****************************************
> (XEN) 
> (XEN) Reboot in five seconds...
> (XEN) Resetting with ACPI MEMORY or I/O RESET_REG.
> 
> Regards
> Carl(Songtao)

Liu, SongtaoX

2013-Jul-18 02:03 UTC

head link

Re: [bug 1868] dom0 will panic when pcibacking a vt-d device on IVT-EP

Yes, the patch fixed it.
http://lists.xenproject.org/archives/html/xen-devel/2013-07/msg01573.html
Thanks!



Regards
Carl(Songtao)


-----Original Message-----
From: Jan Beulich [mailto:JBeulich@suse.com] 
Sent: Wednesday, July 17, 2013 11:11 PM
To: Liu, SongtaoX
Cc: Ren, Yongjie; Xu, YongweiX; Tian, Yongxue; xen-devel@lists.xen.org;
keir@xen.org
Subject: Re: [Xen-devel] [bug 1868] dom0 will panic when pcibacking a vt-d
device on IVT-EP
>>> On 17.07.13 at 10:51, "Liu, SongtaoX"
<songtaox.liu@intel.com> wrote:
> Hi, all,
> c/s 27239:807bde93934d introduced a new bug, dom0 will panic when 
> pcibacking a vt-d device on IVT-EP.
> as: 
> http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1868
> 
> author    Jan Beulich <jbeulich@suse.com>
> date    Mon Jul 15 14:17:56 2013 +0200 (39 hours ago)
> parents    6542a6b34d7b
> children    e539f83fc9b1
> files    xen/arch/x86/mm.c xen/arch/x86/msi.c xen/arch/x86/x86_64/mm.c
> xen/include/asm-x86/page.h
> 
> Reproduce steps:
> ----------------
> 1. boot up dom0,
> 2. run "xl pci-assignable-add $vt-d_BDF"
> 3. dom0 will panic
Should be fixed by
http://lists.xenproject.org/archives/html/xen-devel/2013-07/msg01573.html

Jan
> panic log:
> (XEN) ----[ Xen-4.4-unstable  x86_64  debug=y  Not tainted ]----
> (XEN) CPU:    25
> (XEN) RIP:    e008:[<ffff82d080160634>] flush_area_local+0x116/0x140
> (XEN) RFLAGS: 0000000000010002   CONTEXT: hypervisor
> (XEN) rax: 0000000000001000   rbx: 0000000000000701   rcx: 0000000000000040
> (XEN) rdx: 0000000000000000   rsi: 0000000000000004   rdi: ffff82cfffd4d000
> (XEN) rbp: ffff830839abfc78   rsp: ffff830839abfc38   r8:  ffff8300ba470ff0
> (XEN) r9:  0000000000000038   r10: ffff82d08022dba0   r11: 0000000000000202
> (XEN) r12: 0000000000000000   r13: 0000000000000246   r14: ffff82cfffd4d000
> (XEN) r15: ffff82d0802f5e00   cr0: 0000000080050033   cr4: 00000000001426f0
> (XEN) cr3: 000000084c557000   cr2: ffff82cfffd4d000
> (XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e010   cs: e008
> (XEN) Xen stack trace from rsp=ffff830839abfc38:
> (XEN)    000000ff00dd00b3 0000000000000000 0000000000000000
ffff82d080264d80
> (XEN)    ffff82cfffd4d000 0000000000000701 0000000000000001
ffff8300ba4729f8
> (XEN)    ffff830839abfca8 ffff82d08017fba4 0000000000000000
0000000000000000
> (XEN)    00000000ba470063 ffff82cfffd4d000 ffff830839abfd38
ffff82d08016ff7a
> (XEN)    ffff830839abfcc8 0000000000000000 0000000000000080
0000000000000000
> (XEN)    0000000000000000 0100000000000000 ffff83083980b324
000ffff82cfffd4d
> (XEN)    0000000000000000 ffff8300ba470ff0 0000000000000000
ffff8304bb825f70
> (XEN)    0000000000000000 00000000000002b2 ffff83083998a790
ffff83083998a830
> (XEN)    ffff830839abfd48 ffff82d0801707f8 ffff830839abfd88
ffff82d080167841
> (XEN)    00000000000000df ffff8304bb824080 00000000000000de
ffff830839a77000
> (XEN)    00000000000000b3 ffff83083980b300 ffff830839abfe08
ffff82d08016b880
> (XEN)    0000000000000cfc 0000000000000296 00000000000000b3
ffff8304bb825f70
> (XEN)    00000000000000de ffff82d080186100 ffff830839a771b0
ffff83083980b324
> (XEN)    ffff830839abff18 ffff830839a77000 00000000fffffffd
ffff830839a77198
> (XEN)    00000000000000de 0000000000000001 ffff830839abfe48
ffff82d08017dbd9
> (XEN)    ffff830839abfe68 000000000000000e ffff8800b20cdc58
ffff8300ba2e3000
> (XEN)    0000000000000001 0000000000000001 ffff830839abfef8
ffff82d08017e81b
> (XEN)    ffff8801004038c0 ffff8800b29a1a00 000000de00007ff0
ffff82d08017fe99
> (XEN)    ffff830839abff08 ffff82d080169611 aaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaa
> (XEN)    aaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaa aaaaaaaaaaaaaaef
aaaaaaaaaaaaaaaa
> (XEN) Xen call trace:
> (XEN)    [<ffff82d080160634>] flush_area_local+0x116/0x140
> (XEN)    [<ffff82d08017fba4>] flush_area_mask+0x67/0x15b
> (XEN)    [<ffff82d08016ff7a>] map_pages_to_xen+0xb2b/0xffd
> (XEN)    [<ffff82d0801707f8>] __set_fixmap+0x34/0x36
> (XEN)    [<ffff82d080167841>] msi_free_irq+0xe1/0x1ae
> (XEN)    [<ffff82d08016b880>] unmap_domain_pirq+0x304/0x38e
> (XEN)    [<ffff82d08017dbd9>] physdev_unmap_pirq+0xf9/0x16d
> (XEN)    [<ffff82d08017e81b>] do_physdev_op+0x6df/0x1128
> (XEN)    [<ffff82d08022304b>] syscall_enter+0xeb/0x145
> (XEN)    
> (XEN) Pagetable walk from ffff82cfffd4d000:
> (XEN)  L4[0x105] = 00000000ba472063 ffffffffffffffff
> (XEN)  L3[0x13f] = 00000000ba470063 ffffffffffffffff
> (XEN)  L2[0x1fe] = 00000000ba7e6063 ffffffffffffffff
> (XEN)  L1[0x14d] = 0000000000000000 ffffffffffffffff
> (XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 25:
> (XEN) FATAL PAGE FAULT
> (XEN) [error_code=0000]
> (XEN) Faulting linear address: ffff82cfffd4d000
> (XEN) ****************************************
> (XEN)
> (XEN) Reboot in five seconds...
> (XEN) Resetting with ACPI MEMORY or I/O RESET_REG.
> 
> Regards
> Carl(Songtao)

Xen devel - Jul 2013 - [bug 1868] dom0 will panic when pcibacking a vt-d device on IVT-EP

[bug 1868] dom0 will panic when pcibacking a vt-d device on IVT-EP

Re: [bug 1868] dom0 will panic when pcibacking a vt-d device on IVT-EP

Re: [bug 1868] dom0 will panic when pcibacking a vt-d device on IVT-EP

Re: [bug 1868] dom0 will panic when pcibacking a vt-d device on IVT-EP