search for: ib_ipoib

...and then hardware/Infiniband I should blame. I have a direct IPoIB link between two hosts, gluster replica volume, libvirt store disk images there. I start a guest on hostA and I get below on hostB(which is IB subnet manager): [Mon Oct 23 16:43:32 2017] Workqueue: ipoib_wq ipoib_cm_tx_start [ib_ipoib] [Mon Oct 23 16:43:32 2017]? 0000000000008010 00000000553c90b1 ffff880c1c6eb818 ffffffff816a3db1 [Mon Oct 23 16:43:32 2017]? ffff880c1c6eb8a8 ffffffff81188810 0000000000000000 ffff88042ffdb000 [Mon Oct 23 16:43:32 2017]? 0000000000000004 0000000000008010 ffff880c1c6eb8a8 00000000553c90b1 [Mon Oc...

...-ni.c:1002:lnet_startup_lndnis()) Can''t load LND > o2ib, module ko2iblnd, rc=256 > > lsmod | grep ib > libcfs 103060 1 lnet > ib_ucm 19332 0 > ib_addr 10756 1 rdma_cm > ib_cm 31968 2 ib_ucm,rdma_cm > ib_ipoib 48400 0 > ib_sa 16652 3 rdma_cm,ib_cm,ib_ipoib > ib_uverbs 38312 2 rdma_ucm,ib_ucm > ib_umad 17968 0 > ib_mthca 116240 0 > ib_mad 36116 4 ib_cm,ib_sa,ib_umad,ib_mthca > ib_core...

...oaded modules : ** * # /etc/modules: kernel modules to load at boot time. # # This file contains the names of kernel modules that should be loaded # at boot time, one per line. Lines beginning with "#" are ignored. # Parameters can be specified after the module name. loop mlx4_ib ib_umad ib_ipoib ib_srp root@blade1:/# When I''m on the Xen kernel (with 4.0.1 en 4.1.3 version of Xen) I have this problem on the log with "ib_umad" module Dec 18 13:16:33 blade4 kernel: [ 133.118783] user_mad: process ibsrpdm did not enable P_Key index support. Dec 18 13:16:33 blade4 kerne...

We have a new install of CentOS 6.7 with infiniband support installed. We can see the card in hardware and we can see the mlx4 drivers loaded in the kernel but cannot see the card as an ethernet interface, using ifconfig -a. Can you recommend an install procedure to see this as an ethernet interface? Thanks On 05/25/2016 07:32 AM, Fabian Arrotin wrote: > On 25/05/16 03:08, Pat Haley

.../ofa_kernel-1.2/drivers/infiniband/hw/cxgb3/core -I/root/ lustre/1.6.4.2/ofa_kernel-1.2/drivers/net/cxgb3 -I/root/lustre/ 1.6.4.2/ofa_kernel-1.2/drivers/net/rds -DMODULE -D"KBUILD_STR(s) =#s" -D"KBUILD_BASENAME=KBUILD_STR(ipoib_fs)" - D"KBUILD_MODNAME=KBUILD_STR(ib_ipoib)" -c -o /root/lustre/1.6.4.2/ ofa_kernel-1.2/drivers/infiniband/ulp/ipoib/.tmp_ipoib_fs.o /root/ lustre/1.6.4.2/ofa_kernel-1.2/drivers/infiniband/ulp/ipoib/ipoib_fs.c /root/lustre/1.6.4.2/ofa_kernel-1.2/drivers/infiniband/ulp/ipoib/ ipoib_fs.c: In function ?ipoib_mcg_open?: /root/lustre/1.6...

...net/mellanox/mlx5/core/ipoib/ethtool.c > > @@ -39,7 +39,7 @@ static void mlx5i_get_drvinfo(struct net_device *dev, > > struct mlx5e_priv *priv = mlx5i_epriv(dev); > > > > mlx5e_ethtool_get_drvinfo(priv, drvinfo); > > - strlcpy(drvinfo->driver, DRIVER_NAME "[ib_ipoib]", > > + strlcpy(drvinfo->driver, KBUILD_MODNAME "[ib_ipoib]", > > sizeof(drvinfo->driver)); > > } > > > > diff --git a/drivers/net/ethernet/mellanox/mlx5/core/main.c > > b/drivers/net/ethernet/mellanox/mlx5/core/main.c > > index 71...

...n ethernet > interface, using ifconfig -a. Can you recommend an install procedure > to see this as an ethernet interface? It's not an ethernet interface. I guess you're referring to a TCP/IP interface. TCP/IP is provided on infiniband by the IPoIB ULP (upper level protocol) and the ib_ipoib kernel module. ibstat and ibv_devinfo are commands for showing infiniband interfaces. /Peter K -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

...BOOT_VLAN_EN_P20 BOOT_RETRY_CNT_P20 LEGACY_BOOT_PROTOCOL_P21 BOOT_VLAN_P21 Needed packages: Most if not all packages appear to be installed on server [root at mseas-data2 ~]# service rdma status Low level hardware support loaded: ??????? mlx4_ib Upper layer protocol modules: ??????? ib_ipoib User space access modules: ??????? rdma_ucm ib_ucm ib_uverbs ib_umad Connection management modules: ??????? rdma_cm ib_cm iw_cm Configured IPoIB interfaces: none Currently active IPoIB interfaces: ib0

Hi have what might be some elementary questions. Really, what I"d love would be for someone who has had good success to publish his/her configuration files and, maybe, the output from ifconfig. At this point, when I see the not-so-good performance I"m getting, I don't realistically know if I'm in the right ballfield. It seems to me, that with so many mellanox cards out

...bdclass libcfs 189784 12 osc,mgc,lustre,lov,lquota,mdc,ksocklnd,ko2iblnd,ptlrpc,obdclass,lnet,lvf s rdma_cm 65940 4 ko2iblnd,ib_iser,rdma_ucm,ib_sdp ib_core 88576 16 ko2iblnd,ib_iser,rdma_ucm,ib_ucm,ib_srp,ib_sdp,rdma_cm,ib_cm,iw_cm,ib_lo cal_sa,ib_ipoib,ib_sa,ib_uverbs,ib_umad,ib_mthca,ib_mad I''d be grateful for any hints. Regards, Michael

An user reported that he has hit an annoying deadlock while playing with ceph based on btrfs. Current updating device tree requires space from METADATA chunk, so we -may- need to do a recursive chunk allocation when adding/updating dev extent, that is where the deadlock comes from. If we use SYSTEM metadata to update device tree, we can avoid the recursive stuff. Reported-by: Jim Schutt

Hi I am hitting this Warning reproducible, the workload is a ceph osd, kernel ist 3.1.0-rc5. Best Regards, martin [ 5472.099766] ------------[ cut here ]------------ [ 5472.099833] WARNING: at fs/btrfs/inode.c:2193 btrfs_orphan_commit_root+0xb0/0xc0 [btrfs]() [ 5472.099838] Hardware name: MS-96B3 [ 5472.099842] Modules linked in: radeon ttm drm_kms_helper drm i2c_algo_bit psmouse sp5100_tco

...at_amanda nf_conntrack_amanda nf_conntrack_tftp nf_conntrack_sip nf_conntrack_proto_sctp nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrack_netbios_ns nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp xt_physdev xt_hashlimit nfs ib_iser libiscsi scsi_transport_iscsi ib_ucm ib_ipoib rdma_ucm rdma_cm ib_cm iw_cm ib_sa ib_addr ib_uverbs ib_umad mlx4_ib ib_mthca ib_mad ib_core i7core_edac edac_core mlx4_core iTCO_wdt iTCO_vendor_support > [ 605.112285] > [ 605.112419] Pid: 16666, comm: mount Not tainted 2.6.37stg #6 X8DTU/X8DTU > [ 605.112586] RIP: 0010:[<ffffffff...

From: Leon Romanovsky <leonro at nvidia.com> Changelog: v1: * Renamed _mlx5_rescan_driver to be mlx5_rescan_driver_locked like in other parts of the mlx5 driver. * Renamed MLX5_INTERFACE_PROTOCOL_VDPA to tbe MLX5_INTERFACE_PROTOCOL_VNET as a preparation to coming series from Eli C. * Some small naming renames in mlx5_vdpa. * Refactored adev index code to make Parav's SF series

It seems the problems running mthca in a Xen domU have uncovered a bug in mthca: mthca uses dma_sync_single in mthca_arbel_write_mtt_seg() and mthca_arbel_map_phys_fmr() to sync the MTTs that get written. However, Documentation/DMA-API.txt says: void dma_sync_single(struct device *dev, dma_addr_t dma_handle, size_t size, enum dma_data_direction direction) synchronise a single