| 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
| ||
|
Message-ID: <CAE9FiQWmgyirjjCwn54PkAsfvWxZSY5RhRVDkhhbK7E0NPzqaw@mail.gmail.com> Date: Wed, 1 Aug 2012 14:32:17 -0700 From: Yinghai Lu <yinghai@...nel.org> To: Lukas Hejtmanek <xhejtman@....muni.cz> Cc: Roland Dreier <roland@...nel.org>, linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org Subject: Re: mellanox mlx4_core and SR-IOV On Wed, Aug 1, 2012 at 1:56 PM, Lukas Hejtmanek <xhejtman@....muni.cz> wrote: > On Wed, Aug 01, 2012 at 11:29:02AM -0700, Yinghai Lu wrote: >> 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. > > sorry for confusing, PCI_DEBUG does not break mlx driver, it is reallocation > code that results: > [ 3.555008] mlx4_core 0000:02:00.0: Missing UAR, aborting. yes, i knew that. one patch in my for-pci-next should address that. http://git.kernel.org/?p=linux/kernel/git/yinghai/linux-yinghai.git;a=patch;h=fcce563f868e296f46a2eeaa88d6959bcee26a2d 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/
Powered by blists - more mailing lists