search for: mlnx

hi johnny, >> anyone any hints how to debug this or some clues what could be going >> wrong here. > > Do you have an exclude in /etc/yum.conf for ibutils-libs? how embarassing. there was indeed an exclude on ibutils-libs. (this must be some leftover from using mlnx ofed. we are switching from c73+mlnx ofed 3.4 to c74 stock ib (there's no mlnxofed3.4 for c74, and our old testbed has connectx2, so we can't use mlnxofed 4.1) ) never start debugging things on a friday evening i guess ;) thanks and sorry for the noise. stijn > > > > ___...

...redistribute vectors kernel: [ 23.270395] i40e 0000:1a:00.3: Added LAN device PF3 bus=0x1a dev=0x00 func=0x03 kernel: [ 23.271911] i40e 0000:1a:00.3: Features: PF-id[3] VFs: 32 VSIs: 34 QP: 56 RSS FD_ATR FD_SB NTUPLE CloudF DCB VxLAN NVGRE PTP ... kernel: [ 250.279739] Compat-mlnx-ofed backport release: f8de107 kernel: [ 250.280006] Backport based on mlnx_ofed/mlnx-ofa_kernel-4.0.git f8de107 kernel: [ 250.280261] compat.git: mlnx_ofed/mlnx-ofa_kernel-4.0.git kernel: [ 250.287865] mlx5_core 0000:3b:00.0: firmware version: 14.23.1020 kernel: [ 250.293492] t...

hi all, in case someone else runs into it, it is the opfed-scripts rpm that has a postinstall and postuninstall script that changes the yum.conf (bad, mellanox, bad) for a pure/regular uninstall it works fine, but to swap ibutils from mlnxofed to ib stack from os, yum obviously doesn't know that the exclude will be removed. i've seen worse in vendor-provided rpms, but i guess it caught me offguard ;) stijn On 09/30/2017 11:51 AM, Stijn De Weirdt wrote: > hi johnny, > >>> anyone any hints how to debug this o...

hi all, i'm trying to understand an issue i'm having with a yum repo (it's a mirror of the c74 repo). there's an rpm in the repo (ibutils-libs in this case); but the client using this repo says it cannot find this rpm (i did yum info ibutils-libs --disablerepo=* --enablerepo=c74 to exclude all other repos). other rpms are ok to use, so nothing structural going wrong (i think)

...mcloud 2. install kernel, kernel-firmware, kernel-headers, and kernel-devel * in this case, it''s the rpm files with "2.6.32-279.14.1.el6_lustre.x86_64" in their name 3. reboot into this lustre kernel 4. install the remaining rpms 5. download ofed from mellanox "MLNX_OFED_LINUX-1.5.3-3.1.0-rhel6.3-x86_64.iso" * build mellanox ofed bits using the lustre kernel and kernel-devel info * install mellanox ofed 6. reboot 7. upon reboot, if I do NOT have o2ib3 in my lnet networks parameters, I can modprobe lnet and lustre. 8. if I DO have o2ib3 p...

...ny Device 61b0 Physical Slot: 5 Flags: fast devsel Memory at f3000000 (64-bit, prefetchable) [size=8M] Capabilities: [60] Express Endpoint, MSI 00 Capabilities: [9c] MSI-X: Enable- Count=4 Masked- Kernel modules: mlx4_core With the VM using a generic 2.6.32 Centos 6-3 kernel, I installed the MLNX 2.0-beta drivers (they actually compile with standard rhel kernel). The problem is when I modprobe mlx4_core, I get the following error in the VM: mlx4_core: Mellanox ConnectX core driver v1.1 (Dec, 2011) mlx4_core: Initializing 0000:00:05.0 mlx4_core 0000:00:05.0: Detected virtual function - runn...