linux-kernel - Re: mellanox mlx4

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAE9FiQUSFeBpGaFByOfENUa8qg7t89WTiUann8=4ezT7s2qmzw@mail.gmail.com>
Date:	Wed, 1 Aug 2012 11:29:02 -0700
From:	Yinghai Lu <yinghai@...nel.org>
To:	Roland Dreier <roland@...nel.org>
Cc:	Lukas Hejtmanek <xhejtman@....muni.cz>,
	linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org
Subject: Re: mellanox mlx4_core and SR-IOV

On Wed, Aug 1, 2012 at 10:37 AM, Roland Dreier <roland@...nel.org> wrote:
> On Wed, Aug 1, 2012 at 6:38 AM, Lukas Hejtmanek <xhejtman@....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@...nel.org> wrote:
> On Wed, Aug 1, 2012 at 6:38 AM, Lukas Hejtmanek <xhejtman@....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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/