http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1762
Summary: [VT-D]Sometimes xen panic when run guest with two
devices case
Product: Xen
Version: unstable
Platform: x86-64
OS/Version: Linux-2.6
Status: NEW
Severity: critical
Priority: P1
Component: Hardware Support
AssignedTo: xen-bugs@lists.xensource.com
ReportedBy: yang.z.zhang@intel.com
Environment:
------------
Service Arch (ia32/ia32e/IA64): ia32e
Guest Arch (ia32/ia32e/IA64):
Guest OS Type (Linux/Windows):Linux
Change Set: 23198:697ac895c11c
Hardware: Westmere-EP
Other:
pvops git:
commit bb1a15e55ec665a64c8a9c6bd699b1f16ac01ff4
Merge: df3a556... bd51e05...
Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Date: Tue Mar 29 15:17:46 2011 -0700
Bug detailed description:
--------------------------
I seen the following panic once when runing our test case that create guest
with two NICs.
vt-nhm7 login: (XEN) [VT-D]iommu.c:853: iommu_fault_status: Primary Pending
Fault
(XEN) [VT-D]iommu.c:828: DMAR:[DMA Write] Request device [0a:00.0] fault addr
2b4830942000, iommu reg = ffff82c3ffe57000
(XEN) DMAR:[fault reason 05h] PTE Write access is not set
(XEN) print_vtd_entries: iommu = ffff83013fffa5b0 bdf = a:0.0 gmfn = 2b4830942
(XEN) root_entry = ffff83013ffd4000
(XEN) root_entry[a] = 13c492001
(XEN) context = ffff83013c492000
(XEN) context[0] = 102_11cb9e005
(XEN) l4 = ffff83011cb9e000
(XEN) l4_index = 56
(XEN) l4[56] = 0
(XEN) l4[56] not present
(XEN) [VT-D]io.c:329: d6: unbind: m_gsi=127 g_gsi=36 device=5 intx=0
(XEN) [VT-D]io.c:387: d6 unmap: m_irq=127 device=5 intx=0
(XEN) [VT-D]io.c:305: d6: bind: m_gsi=17 g_gsi=36 device=5 intx=0
(XEN) msi.c:815: MSI is already in use on device 0a:00.0
(XEN) msi.c:815: MSI is already in use on device 0a:00.0
INIT: Id "co" respawning too fast: disabled for 5 minutes
[ 1069.049714] pci-stub 0000:08:02.0: restoring config space at offset 0x1 (was
0x2300400, writing 0x2300007)
(XEN) [VT-D]iommu.c:1500: d6:PCI: unmap bdf = 8:2.0
(XEN) [VT-D]iommu.c:1373: d0:PCI: map bdf = 8:2.0
[ 1069.067489] pci-stub 0000:0a:00.0: restoring config space at offset 0x1 (was
0x100400, writing 0x100407)
(XEN) [VT-D]iommu.c:1490: d6:PCIe: unmap bdf = a:0.0
(XEN) [VT-D]iommu.c:1363: d0:PCIe: map bdf = a:0.0
(XEN) irq.c:1590: dom6: forcing unbind of pirq 16
(XEN) irq.c:1590: dom6: forcing unbind of pirq 17
(XEN) irq.c:1590: dom6: forcing unbind of pirq 125
(XEN) irq.c:1590: dom6: forcing unbind of pirq 126
(XEN) ----[ Xen-4.2-unstable x86_64 debug=y Not tainted ]----
(XEN) CPU: 10
(XEN) RIP: e008:[<ffff82c4801b57b8>] vioapic_irq_positive_edge+0x9f/0xe7
(XEN) RFLAGS: 0000000000010202 CONTEXT: hypervisor
(XEN) rax: 0000000000000130 rbx: 0000000000000024 rcx: 0000000000000000
(XEN) rdx: 0000000000000297 rsi: 0000000000000024 rdi: ffff8301032826dc
(XEN) rbp: ffff83013efafe00 rsp: ffff83013efafde0 r8: 0000000000000002
(XEN) r9: ffff83013efb7280 r10: 0000ffff0000ffff r11: 00ff00ff00ff00ff
(XEN) r12: ffff830103282000 r13: 0000000000000000 r14: ffff830103282000
(XEN) r15: 0000000000000005 cr0: 000000008005003b cr4: 00000000000026f0
(XEN) cr3: 00000000bf0a4000 cr2: 0000000000000132
(XEN) ds: 002b es: 002b fs: 0000 gs: 0000 ss: e010 cs: e008
(XEN) Xen stack trace from rsp=ffff83013efafde0:
(XEN) 0000ffff0000ffff ffff8301032826e0 0000000000000005 0000000000000000
(XEN) ffff83013efafe30 ffff82c4801b05b4 0000000000000000 ffff8301032826d8
(XEN) ffff830103282000 0000000000000005 ffff83013efafe60 ffff82c4801b0879
(XEN) ffff8301033ef7a0 0000000000000000 0000000000000330 0000000000000011
(XEN) ffff83013efafec0 ffff82c48013f2d4 ffff830103282190 0000000000000330
(XEN) ffff830103282000 ffff83011cb9f010 000000113efaff18 000000000000000a
(XEN) ffff83013efb70e0 ffff83011cb9f340 ffff83013efb70d0 ffff83013efb7040
(XEN) ffff83013efafef0 ffff82c4801257d0 ffff83013efaff18 ffff8300bf7fa000
(XEN) ffffffffffffffff ffff83013efb7060 ffff83013efaff10 ffff82c480153787
(XEN) ffff82c4801234fe ffff8300bf7fa000 ffff83013efafe10 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 ffff88003fccbf10
(XEN) ffffffff81878950 0000000000000246 ffff88003c18bc18 ffffffff81067fbb
(XEN) 0000000000000000 0000000000000000 ffffffff810093aa 0000000000000000
(XEN) 00000000deadbeef 00000000deadbeef 0000010000000000 ffffffff810093aa
(XEN) 000000000000e033 0000000000000246 ffff88003fccbef8 000000000000e02b
(XEN) 000000000000beef 000000000000beef 000000000000beef 000000000000beef
(XEN) 000000000000000a ffff8300bf7fa000 0000003cbecde480 0000000000000000
(XEN) Xen call trace:
(XEN) [<ffff82c4801b57b8>] vioapic_irq_positive_edge+0x9f/0xe7
(XEN) [<ffff82c4801b05b4>] __hvm_pci_intx_assert+0x7c/0xd3
(XEN) [<ffff82c4801b0879>] hvm_pci_intx_assert+0x3f/0x5c
(XEN) [<ffff82c48013f2d4>] hvm_dirq_assist+0x12e/0x1ea
(XEN) [<ffff82c4801257d0>] do_tasklet+0xf4/0x16f
(XEN) [<ffff82c480153787>] idle_loop+0x4d/0x58
(XEN)
(XEN) Pagetable walk from 0000000000000132:
(XEN) L4[0x000] = 000000013fff5063 5555555555555555
(XEN) L3[0x000] = 000000013fff4063 5555555555555555
(XEN) L2[0x000] = 000000013fff3063 5555555555555555
(XEN) L1[0x000] = 0000000000000000 ffffffffffffffff
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 10:
(XEN) FATAL PAGE FAULT
(XEN) [error_code=0000]
(XEN) Faulting linear address: 0000000000000132
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...
(XEN) Resetting with ACPI MEMORY or I/O RESET_REG.
Reproduce steps:
----------------
1.Create guest with two devices.
2.We found xen painc once.
Current result:
----------------
xen panic
Expected result:
----------------
work well
Basic root-causing log:
----------------------
--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
Summary: [VT-D]Sometimes xen panic when run guest with two
devices case
Product: Xen
Version: unstable
Platform: x86-64
OS/Version: Linux-2.6
Status: NEW
Severity: critical
Priority: P1
Component: Hardware Support
AssignedTo: xen-bugs@lists.xensource.com
ReportedBy: yang.z.zhang@intel.com
Environment:
------------
Service Arch (ia32/ia32e/IA64): ia32e
Guest Arch (ia32/ia32e/IA64):
Guest OS Type (Linux/Windows):Linux
Change Set: 23198:697ac895c11c
Hardware: Westmere-EP
Other:
pvops git:
commit bb1a15e55ec665a64c8a9c6bd699b1f16ac01ff4
Merge: df3a556... bd51e05...
Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Date: Tue Mar 29 15:17:46 2011 -0700
Bug detailed description:
--------------------------
I seen the following panic once when runing our test case that create guest
with two NICs.
vt-nhm7 login: (XEN) [VT-D]iommu.c:853: iommu_fault_status: Primary Pending
Fault
(XEN) [VT-D]iommu.c:828: DMAR:[DMA Write] Request device [0a:00.0] fault addr
2b4830942000, iommu reg = ffff82c3ffe57000
(XEN) DMAR:[fault reason 05h] PTE Write access is not set
(XEN) print_vtd_entries: iommu = ffff83013fffa5b0 bdf = a:0.0 gmfn = 2b4830942
(XEN) root_entry = ffff83013ffd4000
(XEN) root_entry[a] = 13c492001
(XEN) context = ffff83013c492000
(XEN) context[0] = 102_11cb9e005
(XEN) l4 = ffff83011cb9e000
(XEN) l4_index = 56
(XEN) l4[56] = 0
(XEN) l4[56] not present
(XEN) [VT-D]io.c:329: d6: unbind: m_gsi=127 g_gsi=36 device=5 intx=0
(XEN) [VT-D]io.c:387: d6 unmap: m_irq=127 device=5 intx=0
(XEN) [VT-D]io.c:305: d6: bind: m_gsi=17 g_gsi=36 device=5 intx=0
(XEN) msi.c:815: MSI is already in use on device 0a:00.0
(XEN) msi.c:815: MSI is already in use on device 0a:00.0
INIT: Id "co" respawning too fast: disabled for 5 minutes
[ 1069.049714] pci-stub 0000:08:02.0: restoring config space at offset 0x1 (was
0x2300400, writing 0x2300007)
(XEN) [VT-D]iommu.c:1500: d6:PCI: unmap bdf = 8:2.0
(XEN) [VT-D]iommu.c:1373: d0:PCI: map bdf = 8:2.0
[ 1069.067489] pci-stub 0000:0a:00.0: restoring config space at offset 0x1 (was
0x100400, writing 0x100407)
(XEN) [VT-D]iommu.c:1490: d6:PCIe: unmap bdf = a:0.0
(XEN) [VT-D]iommu.c:1363: d0:PCIe: map bdf = a:0.0
(XEN) irq.c:1590: dom6: forcing unbind of pirq 16
(XEN) irq.c:1590: dom6: forcing unbind of pirq 17
(XEN) irq.c:1590: dom6: forcing unbind of pirq 125
(XEN) irq.c:1590: dom6: forcing unbind of pirq 126
(XEN) ----[ Xen-4.2-unstable x86_64 debug=y Not tainted ]----
(XEN) CPU: 10
(XEN) RIP: e008:[<ffff82c4801b57b8>] vioapic_irq_positive_edge+0x9f/0xe7
(XEN) RFLAGS: 0000000000010202 CONTEXT: hypervisor
(XEN) rax: 0000000000000130 rbx: 0000000000000024 rcx: 0000000000000000
(XEN) rdx: 0000000000000297 rsi: 0000000000000024 rdi: ffff8301032826dc
(XEN) rbp: ffff83013efafe00 rsp: ffff83013efafde0 r8: 0000000000000002
(XEN) r9: ffff83013efb7280 r10: 0000ffff0000ffff r11: 00ff00ff00ff00ff
(XEN) r12: ffff830103282000 r13: 0000000000000000 r14: ffff830103282000
(XEN) r15: 0000000000000005 cr0: 000000008005003b cr4: 00000000000026f0
(XEN) cr3: 00000000bf0a4000 cr2: 0000000000000132
(XEN) ds: 002b es: 002b fs: 0000 gs: 0000 ss: e010 cs: e008
(XEN) Xen stack trace from rsp=ffff83013efafde0:
(XEN) 0000ffff0000ffff ffff8301032826e0 0000000000000005 0000000000000000
(XEN) ffff83013efafe30 ffff82c4801b05b4 0000000000000000 ffff8301032826d8
(XEN) ffff830103282000 0000000000000005 ffff83013efafe60 ffff82c4801b0879
(XEN) ffff8301033ef7a0 0000000000000000 0000000000000330 0000000000000011
(XEN) ffff83013efafec0 ffff82c48013f2d4 ffff830103282190 0000000000000330
(XEN) ffff830103282000 ffff83011cb9f010 000000113efaff18 000000000000000a
(XEN) ffff83013efb70e0 ffff83011cb9f340 ffff83013efb70d0 ffff83013efb7040
(XEN) ffff83013efafef0 ffff82c4801257d0 ffff83013efaff18 ffff8300bf7fa000
(XEN) ffffffffffffffff ffff83013efb7060 ffff83013efaff10 ffff82c480153787
(XEN) ffff82c4801234fe ffff8300bf7fa000 ffff83013efafe10 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 ffff88003fccbf10
(XEN) ffffffff81878950 0000000000000246 ffff88003c18bc18 ffffffff81067fbb
(XEN) 0000000000000000 0000000000000000 ffffffff810093aa 0000000000000000
(XEN) 00000000deadbeef 00000000deadbeef 0000010000000000 ffffffff810093aa
(XEN) 000000000000e033 0000000000000246 ffff88003fccbef8 000000000000e02b
(XEN) 000000000000beef 000000000000beef 000000000000beef 000000000000beef
(XEN) 000000000000000a ffff8300bf7fa000 0000003cbecde480 0000000000000000
(XEN) Xen call trace:
(XEN) [<ffff82c4801b57b8>] vioapic_irq_positive_edge+0x9f/0xe7
(XEN) [<ffff82c4801b05b4>] __hvm_pci_intx_assert+0x7c/0xd3
(XEN) [<ffff82c4801b0879>] hvm_pci_intx_assert+0x3f/0x5c
(XEN) [<ffff82c48013f2d4>] hvm_dirq_assist+0x12e/0x1ea
(XEN) [<ffff82c4801257d0>] do_tasklet+0xf4/0x16f
(XEN) [<ffff82c480153787>] idle_loop+0x4d/0x58
(XEN)
(XEN) Pagetable walk from 0000000000000132:
(XEN) L4[0x000] = 000000013fff5063 5555555555555555
(XEN) L3[0x000] = 000000013fff4063 5555555555555555
(XEN) L2[0x000] = 000000013fff3063 5555555555555555
(XEN) L1[0x000] = 0000000000000000 ffffffffffffffff
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 10:
(XEN) FATAL PAGE FAULT
(XEN) [error_code=0000]
(XEN) Faulting linear address: 0000000000000132
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...
(XEN) Resetting with ACPI MEMORY or I/O RESET_REG.
Reproduce steps:
----------------
1.Create guest with two devices.
2.We found xen painc once.
Current result:
----------------
xen panic
Expected result:
----------------
work well
Basic root-causing log:
----------------------
--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs