On Mon, Sep 7, 2015 at 7:29 PM, Bradley W. Dutton < brad-fbsd-stable at duttonbros.com> wrote:> 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? > >Looks like on ESXi we are using Xen HVM init ops, which do not enable MSI. And the isci driver is not reverting to INTx resource allocation when MSIx vector allocation fails. I've added reverting to INTx in the attached patch - can you try once more? Thanks, -Jim -------------- next part -------------- A non-text attachment was scrubbed... Name: isci.patch Type: application/octet-stream Size: 1034 bytes Desc: not available URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20150907/e7b7f573/attachment.obj>
Quoting Jim Harris <jim.harris at gmail.com>:> On Mon, Sep 7, 2015 at 7:29 PM, Bradley W. Dutton < > brad-fbsd-stable at duttonbros.com> wrote: > >> 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? >> >> > Looks like on ESXi we are using Xen HVM init ops, which do not enable MSI. > And the isci driver is not reverting to INTx resource allocation when MSIx > vector allocation fails. I've added reverting to INTx in the attached > patch - can you try once more? > > Thanks, > > -JimThat patch worked. No allocation errors and the drives work as expected. Thanks again, Brad