There are 2 devices in the same group so I passed both of them:
http://duttonbrosllc.com/misc/vmware_esxi_passthrough_config.png
At the time I wasn't sure if this was necessary but I just tried the
Centos 7 VM and it worked without the SMBus device being passed
through. I then tried the FreeBSD VM without SMBus and saw the same
allocation error as before. Looks like the SMBus device is a red
herring?
Thanks,
Brad
Quoting Scott Long <scottl at samsco.org>:
> This is really weird. According to what you?ve posted, it?s
> advertising itself as an SMBus controller with no BARs. Maybe
> you?re passing through the wrong device, or someone added the wrong
> PCI device id data to the driver?
>
> Scott
>
>> On Sep 7, 2015, at 11:34 AM, Bradley W. Dutton
>> <brad-fbsd-stable at duttonbros.com> 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 at 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 at 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?
>>
>> Thanks,
>> Brad
>>
>> _______________________________________________
>> freebsd-stable at freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
>> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at
freebsd.org"