Messages in this thread | | | Date | Wed, 1 Aug 2012 11:29:02 -0700 | Subject | Re: mellanox mlx4_core and SR-IOV | From | Yinghai Lu <> |
| |
On Wed, Aug 1, 2012 at 10:37 AM, Roland Dreier <roland@kernel.org> wrote: > On Wed, Aug 1, 2012 at 6:38 AM, Lukas Hejtmanek <xhejtman@ics.muni.cz> wrote: >> [ 3.558296] mlx4_core 0000:02:00.0: not enough MMIO resources for SR-IOV (nres: 0, iov->nres: 1) > > This comes from the core sriov_enable() function, not anything in mlx4. > (although my kernel doesn't have the print of nres in that message) > > Not sure what it means.
On Wed, Aug 1, 2012 at 10:37 AM, Roland Dreier <roland@kernel.org> wrote: > On Wed, Aug 1, 2012 at 6:38 AM, Lukas Hejtmanek <xhejtman@ics.muni.cz> wrote: >> [ 3.558296] mlx4_core 0000:02:00.0: not enough MMIO resources for SR-IOV (nres: 0, iov->nres: 1) > > This comes from the core sriov_enable() function, not anything in mlx4. > (although my kernel doesn't have the print of nres in that message) > > Not sure what it means.
iov bar is not assigned by BIOS, and kernel can not find range for it too.
Lukas, can you post whole boot log with PCI_DEBUG enabled? That will tell exact why kernel does not assign them.
Recent kernel from 3.4... should enable realloc when SRIOV bar is not assigned.
Thanks
Yinghai
| |