Thread (12 messages) 12 messages, 3 authors, 2012-08-10

Re: mellanox mlx4_core and SR-IOV

From: Yinghai Lu <yinghai@kernel.org>
Date: 2012-08-01 18:29:07
Also in: lkml

On Wed, Aug 1, 2012 at 10:37 AM, Roland Dreier [off-list ref] wrote:
On Wed, Aug 1, 2012 at 6:38 AM, Lukas Hejtmanek [off-list ref] wrote:
quoted
[    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 [off-list ref] wrote:
On Wed, Aug 1, 2012 at 6:38 AM, Lukas Hejtmanek [off-list ref] wrote:
quoted
[    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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help