Mailing List Archive

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1742





------- Comment #2 from jason.kwon@ericsson.com 2011-02-14 16:49 -------
msi.c WARN message:

(XEN) Xen WARN at msi.c:635
(XEN) ----[ Xen-4.1.0-rc4-pre x86_64 debug=y Not tainted ]----
(XEN) CPU: 1
(XEN) RIP: e008:[<ffff82c480160ef8>] pci_enable_msi+0x464/0x960
(XEN) RFLAGS: 0000000000010206 CONTEXT: hypervisor
(XEN) rax: 0000000000000000 rbx: 00000000e1500000 rcx: 0000000000000001
(XEN) rdx: ffff82c480257a40 rsi: 0000000000000246 rdi: ffff82c480257a40
(XEN) rbp: ffff830199fefdd8 rsp: ffff830199fefd08 r8: 0000000000000010
(XEN) r9: 0000000000000038 r10: 0000000000000072 r11: 0000000000000010
(XEN) r12: ffff830199fefea8 r13: 0000000000000003 r14: ffff830199f66bf0
(XEN) r15: ffff830199fefe28 cr0: 0000000080050033 cr4: 00000000000026f0
(XEN) cr3: 000000019f50c000 cr2: 000000000264a000
(XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e010 cs: e008
(XEN) Xen stack trace from rsp=ffff830199fefd08:
(XEN) 0000000000000282 ffff830199fefd28 ffff82c4801236b2 01ff830100000003
(XEN) ffff830100000003 ffff82c48012a4e0 0000000000000020 00000070c0028e40
(XEN) ffff830199578fa0 0000000300000034 0000000100000010 0000000300000072
(XEN) 0000000100000010 00000000000e1500 00000000000e1500 00000000e1500000
(XEN) 00000000e1500000 ffff83019e988378 0000000000000202 ffff830199fefdb8
(XEN) ffff82c480123627 ffff830199fefea8 ffff8301992ba000 0000000000000034
(XEN) 000000000000002a 00000000ffffffed ffff830199fefe58 ffff82c480162cdf
(XEN) ffff83019e820808 00000000802d44c0 00000000000000d0 000000000000002a
(XEN) 00000000000000a8 ffff83019e841580 ffff830199f66bf0 ffff830199fefe38
(XEN) ffff82c480123627 ffff830199fefea8 0000000002430004 0000000000000034
(XEN) 000000000000002a 0000000000000006 ffff830199fefef8 ffff82c480176a21
(XEN) ffff830199feff18 ffff8300df7d6000 0000000000000001 ffffffffffffffff
(XEN) 0000008100000003 0000000000000000 00000000e1500000 0000000000000202
(XEN) 0000008100000003 000000000000002a 00000000e1500000 0000000000000033
(XEN) ffff8301992ba000 ffff82c480165f22 ffff8300df7d6000 00007fffbd3dc4f0
(XEN) 0000000000305000 0000000000305000 00007cfe660100c7 ffff82c480208b68
(XEN) ffffffff8100942a 0000000000000021 0000000000000006 0000000000305000
(XEN) 0000000000305000 00007fffbd3dc4f0 ffff88003ee51e88 ffff88003ff0b780
(XEN) 0000000000000282 0000000200000035 0000000000000000 0000000000000001
(XEN) 0000000000000021 ffffffff8100942a 0000000000000001 0000000002430004
(XEN) Xen call trace:
(XEN) [<ffff82c480160ef8>] pci_enable_msi+0x464/0x960
(XEN) [<ffff82c480162cdf>] map_domain_pirq+0x213/0x30d
(XEN) [<ffff82c480176a21>] do_physdev_op+0x951/0x12f0
(XEN) [<ffff82c480208b68>] syscall_enter+0xc8/0x122
(XEN)

Sample IOMMU page fault message:

(XEN) [VT-D]iommu.c:853: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:841: INTR-REMAP: Request device [03:10.0] fault index 26,
iommu reg = ffff82c3fff56000
(XEN) INTR-REMAP:[fault reason 22h] Present field in the IRTE entry is clear


--
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

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1742





------- Comment #3 from jason.kwon@ericsson.com 2011-02-14 16:51 -------
Additional info: PCI passthrough and network functionality of 82599 physical
functions always works, no matter which guest kernel; only the VF functionality
is broken when switching guest kernels.


--
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

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1742





------- Comment #4 from jason.kwon@ericsson.com 2011-02-15 11:26 -------
Host driver version:

ixgbe 3.1.17-NAPI (Intel(R) 10 Gigabit PCI Express Network Driver)

Guest driver version(s):

ixgbevf 1.0.0-k0 (Intel(R) 82599 Virtual Function Driver)
ixgbevf 1.0.17-NAPI (Intel(R) 82599 Virtual Function Driver)

Multiple driver versions for the VF were tried in the guest, with no apparent
difference in behavior.


--
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

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1742





------- Comment #5 from jason.kwon@ericsson.com 2011-02-15 19:09 -------
Steps to reproduce issue:

Case 1 (VF passthrough functionality fails with IOMMU page faults):
1) Boot Xen on hardware, with iommu=verbose.
2) Boot DomU with VF passthrough. Select original DomU distro kernel (in my
case, 2.6.35-22-server). Observe MSI warning messages in 'xm dmesg.'
3) Configure VF in guest, verify that network is functional.
4) Shut down guest.
5) Boot DomU again, this time selecting a _different_ kernel (in my case,
2.6.35-23-server).
6) Configure VF in guest, and attempt to access network. Network will not be
functional. Observe IOMMU page fault messages in 'xm dmesg.'

The xen-dmesg file attached to this bug follows Case 1. For step 5, I tried
many different kernels, and none worked except for the kernel that was
originally installed with the distro. I also tried a RedHat guest and observed
the same thing--only the 2.6.18 kernel installed at guest creation gave a
functional VF, any other kernel did not allow VF network traffic.

Case 2 (VF passthrough functionality fails silently):
1) Boot Xen on hardware, with iommu=verbose.
2) Boot DomU with VF passthrough. Select kernel _other than_ original distro
kernel (in my case, 2.6.35-23-server). Observe that there are _no_ MSI warning
messages in 'xm dmesg.'
3) Configure VF in guest, and attempt to access network. Network will not be
functional. Observe that there are _no_ IOMMU page fault messages in 'xm
dmesg.'

Case 3 (MSI warnings appear only in first boot of guest):
1) Boot Xen on hardware, with iommu=verbose.
2) Boot DomU with VF passthrough. Select original DomU distro kernel (in my
case, 2.6.35-22-server). Observe MSI warning messages in 'xm dmesg.'
3) Configure VF in guest, verify that network is functional.
4) Shut down guest.
5) Boot DomU again, booting the original DomU distro kernel again (in my case,
2.6.35-22-server). Observe that there are _no_ new MSI warning messages in 'xm
dmesg.'

Case 3 is not strictly a 'failure' case, but it does illustrate a difference in
behavior between boots of the same guest.


--
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