Re: [Xen-devel] [BUG] pci-passthrough on dom0 kernel versions above 3.8 crashes dom0

[Kristoffer Egefelt <kristoffer@xxxxxxx>]

Here's the bisect (my first - hope it looks allright) - let me know if you need 
anything else.

root@builder:/k/linux-stable# git bisect log
git bisect start
# bad: [00cfbb8ad0a6419f40660362b4d8b5baa30d3efe] Linux 3.8.6
git bisect bad 00cfbb8ad0a6419f40660362b4d8b5baa30d3efe
# good: [aa4cfdeb17e3559fe1e80175c7338e065553dce5] Linux 3.8.5
git bisect good aa4cfdeb17e3559fe1e80175c7338e065553dce5
# bad: [dfa7981463bbf902057c7c2b36c1e9e98f1651c4] USB: mos7840: fix broken 
TIOCMIWAIT
git bisect bad dfa7981463bbf902057c7c2b36c1e9e98f1651c4
# bad: [f80725b652aca0871ea2cc8b2e037edf67de7630] usb: ftdi_sio: Add support 
for Mitsubishi FX-USB-AW/-BD
git bisect bad f80725b652aca0871ea2cc8b2e037edf67de7630
# good: [4911ece4056be5d62a8a3db13d80bf86166bcf7a] HID: usbhid: quirk for 
Realtek Multi-card reader
git bisect good 4911ece4056be5d62a8a3db13d80bf86166bcf7a
# good: [a3f6fd302bab90e11c1d7952c3565e3f3c244824] tg3: fix length overflow in 
VPD firmware parsing
git bisect good a3f6fd302bab90e11c1d7952c3565e3f3c244824
# bad: [ccaa606d2301cb33da35a463951e1ed117d927cc] xen/blkback: correctly 
respond to unknown, non-native requests
git bisect bad ccaa606d2301cb33da35a463951e1ed117d927cc
# good: [e131628113867748a05c9080b9aaf67740d24057] iommu/amd: Make sure dma_ops 
are set for hotplug devices
git bisect good e131628113867748a05c9080b9aaf67740d24057
# bad: [a420a7e3a40a8396104d9a62f676205f2db1a671] xen-pciback: notify 
hypervisor about devices intended to be assigned to guests
git bisect bad a420a7e3a40a8396104d9a62f676205f2db1a671
# bad: [a420a7e3a40a8396104d9a62f676205f2db1a671] xen-pciback: notify 
hypervisor about devices intended to be assigned to guests
git bisect bad a420a7e3a40a8396104d9a62f676205f2db1a671
# bad: [a420a7e3a40a8396104d9a62f676205f2db1a671] xen-pciback: notify 
hypervisor about devices intended to be assigned to guests
git bisect bad a420a7e3a40a8396104d9a62f676205f2db1a671
# bad: [a420a7e3a40a8396104d9a62f676205f2db1a671] xen-pciback: notify 
hypervisor about devices intended to be assigned to guests
git bisect bad a420a7e3a40a8396104d9a62f676205f2db1a671

root@builder:/k/linux-stable# git bisect bad
a420a7e3a40a8396104d9a62f676205f2db1a671 is the first bad commit
commit a420a7e3a40a8396104d9a62f676205f2db1a671
Author: Jan Beulich <JBeulich@xxxxxxxx>
Date:   Tue Mar 12 15:06:23 2013 +0000

    xen-pciback: notify hypervisor about devices intended to be assigned to 
guests
    
    commit 909b3fdb0dd4f3db07b2d75425a00a2adb551383 upstream.
    
    For MSI-X capable devices the hypervisor wants to write protect the
    MSI-X table and PBA, yet it can't assume that resources have been
    assigned to their final values at device enumeration time. Thus have
    pciback do that notification, as having the device controlled by it is
    a prerequisite to assigning the device to guests anyway.
    
    This is the kernel part of hypervisor side commit 4245d33 ("x86/MSI:
    add mechanism to fully protect MSI-X table from PV guest accesses") on
    the master branch of git://xenbits.xen.org/xen.git.
    
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
    Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>

:040000 040000 431896b0135448c76f8787f6cd31596228db71f0 
2b62653093dbf5de13f7c33ea65b61506fb8a557 M      arch
:040000 040000 e6b4f73c9d28c8912870e3a5e271b9dc45c2a4b4 
d042d0455b9ae00401cb6307f6ed5bfe28d98611 M      drivers
:040000 040000 ffe88a72f395700149e7f6d2b982d91331a7dd78 
11b587a7d3b26f6f443fd44f36a9c2be8bc464f1 M      include


On 07/10/2013, at 13.59.13, David Vrabel <david.vrabel@xxxxxxxxxx> wrote:

> On 07/10/13 11:19, Kristoffer Egefelt wrote:
>> Do you still need a bisect, or is Andrews:
>> 
>>> This Xen crash appears to be as a result of d1b6d0a0248 "x86: enable
>>> multi-vector MSI", and is likely a mishanding of some error state
>>> caused by the initial pci attach failure/partial setup.
>> 
>> enough ?
> 
> The Xen bug has been identified but as Jan notes, this shouldn't have
> been triggered by the kernel so it would be useful to know why.
> 
> David
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxx
> http://lists.xen.org/xen-devel
> 


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel