On Mon, Sep 7, 2015 at 10:34 AM, Bradley W. Dutton < [email protected]> wrote:
> Hi, > > I'm having trouble with the isci driver in both stable and current. I see > the following dmesg in stable: > > isci0: <Intel(R) C600 Series Chipset SAS Controller (SATA mode)> port > 0x5000-0x50ff mem 0xe7afc000-0xe7afffff,0xe7400000-0xe77fffff irq 19 at > device 0.0 on pci11 > isci: 1:000051 ISCI bus_alloc_resource failed > > > I'm running FreeBSD on VMWare ESXi 6 with vt-d passthrough of the isci > devices, here is the relevant pciconf output: > > none2@pci0:3:0:0: class=0x0c0500 card=0x062815d9 chip=0x1d708086 > rev=0x06 hdr=0x00 > vendor = 'Intel Corporation' > device = 'C600/X79 series chipset SMBus Controller 0' > class = serial bus > subclass = SMBus > cap 10[90] = PCI-Express 2 endpoint max data 128(128) link x32(x32) > speed 5.0(5.0) ASPM disabled(L0s) > cap 01[cc] = powerspec 3 supports D0 D3 current D0 > cap 05[d4] = MSI supports 1 message > ecap 000e[100] = ARI 1 > isci0@pci0:11:0:0: class=0x010700 card=0x062815d9 chip=0x1d6b8086 > rev=0x06 hdr=0x00 > vendor = 'Intel Corporation' > device = 'C602 chipset 4-Port SATA Storage Control Unit' > class = mass storage > subclass = SAS > cap 01[98] = powerspec 3 supports D0 D3 current D0 > cap 10[c4] = PCI-Express 2 endpoint max data 128(128) link x32(x32) > speed 5.0(5.0) ASPM disabled(L0s) > cap 11[a0] = MSI-X supports 2 messages > Table in map 0x10[0x2000], PBA in map 0x10[0x3000] > ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 corrected > ecap 000e[138] = ARI 1 > ecap 0017[180] = TPH Requester 1 > ecap 0010[140] = SRIOV 1 > > > I haven't tried booting on bare metal but running a linux distro (centos > 7) in the same VM works without issue. Is is possible the SRIOV option is > causing trouble? I don't see a BIOS option to disable that setting on this > server like I have on some others. Any other ideas to get this working? > I do not think the SRIOV is the problem here. I do notice that isci(4) does not explicitly enable PCI busmaster, which will cause problems with PCI passthrough. I've attached a patch that rectifies that issue. I'm not certain that is the root cause of the interrupt resource allocation failure though. Could you: 1) Apply the attached patch and retest. 2) If you still see the resource allocation failure, reboot in verbose mode and provide the resulting dmesg output. Thanks, -Jim > Thanks, > Brad > > _______________________________________________ > [email protected] mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[email protected]" >
isci_busmaster.patch
Description: Binary data
_______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[email protected]"
