search for: ib_mthca

...advise. I was able to get up Dom0 to work with infiniband, but not DomU. I am using Xen 3.0.2 with vmlinuz-2.6.16-xen and initrd-2.6.16-xen.img for DomU kernel and ram image respectively. I am getting the error of "Unknown symbol in module" when i am trying to insert infiniband modules ib_mthca.ko and ib_umad.ko to domU kernel. I made sure that the kernel was configured with infiniband support. However, the dmesg output does not show that domU recognized infiniband hardware at bootup. Should I be specifying anything about infiniband in domain config file? Any help very much appreciated,...

...dard host kernel and that did the same thing. The guest dmesg output in the guest is similar on both permissive and normal mode. I''m getting issues with detecting the firmware on the card for some reason... Any help would be appreciated. Thanks, - David Brown === GUEST dmesg output === ib_mthca: Mellanox InfiniBand HCA driver v1.0 (February 28, 2008) ib_mthca: Initializing 0000:00:00.0 PCI: Enabling device 0000:00:00.0 (0000 -> 0002) PCI: Setting latency timer of device 0000:00:00.0 to 64 ib_mthca 0000:00:00.0: QUERY_FW command failed, aborting. ib_mthca: probe of 0000:00:00.0 failed w...

...dard host kernel and that did the same thing. The guest dmesg output in the guest is similar on both permissive and normal mode. I''m getting issues with detecting the firmware on the card for some reason... Any help would be appreciated. Thanks, - David Brown === GUEST dmesg output === ib_mthca: Mellanox InfiniBand HCA driver v1.0 (February 28, 2008) ib_mthca: Initializing 0000:00:00.0 PCI: Enabling device 0000:00:00.0 (0000 -> 0002) PCI: Setting latency timer of device 0000:00:00.0 to 64 ib_mthca 0000:00:00.0: QUERY_FW command failed, aborting. ib_mthca: probe of 0000:00:00.0 failed w...

...roblem according to google.. Again, all servers and clients are ubuntu 10.04.3/64b, running self-compiled 3.3b1. the IB device is: 02:00.0 InfiniBand: Mellanox Technologies MT25204 [InfiniHost III Lx HCA] (rev a0) dmesg says: ================================== $ dmesg |grep ib_ [ 12.592406] ib_mthca: Mellanox InfiniBand HCA driver v1.0 (April 4, 2008) [ 12.592411] ib_mthca: Initializing 0000:02:00.0 [ 12.592777] ib_mthca 0000:02:00.0: PCI INT A -> Link[LNKD] -> GSI 17 (level, low) -> IRQ 17 [ 12.592790] ib_mthca 0000:02:00.0: setting latency timer to 64 [ 14.996462] ib_mthca...

...ort PCI device from Dom0 into DomU. I''ve enabled permisive device in Dom0. However, inserting infiniband module results in the following messages (with little more verbosity which I have added): pcifront pci-0: Installing PCI frontend pcifront pci-0: Creating PCI Frontend Bus 0000:08 ... ib_mthca: Mellanox InfiniBand HCA driver v0.08 (February 14, 2006) ib_mthca: Initializing 0000:08:00.0 PCI: Enabling device 0000:08:00.0 (0000 -> 0002) PCI: Setting latency timer of device 0000:08:00.0 to 64 ib_mthca 0000:08:00.0: Reset OK! Go bit val: -1 mthca_cmd_post_hcr: returning EAGAIN mthca_cmd_bo...

...ntly working on the latest version of xen with debian (lenny), and I have done 2 PCI passthrough, the fisrt one is with eth1 and i got no probleme with this one, but the second one is with a infiniband adapter=> It''s not working I got this message with dmesg on my DomU : [ 4.111023] ib_mthca: Mellanox InfiniBand HCA driver v1.0 (April 4, 2008) [ 4.111047] ib_mthca: Initializing 0000:00:00.0 [ 4.111501] ib_mthca 0000:00:00.0: enabling device (0000 -> 0002) [ 4.112859] ib_mthca 0000:00:00.0: No bridge found for 0000:00:00.0 [ 15.526745] ib_mthca 0000:00:00.0: PCI device did...

...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 49024 9 > ib_ucm,rdma_cm,ib_cm,ib_ipoib,ib_sa,ib_uverbs,ib_umad,ib_mthca,ib_mad > > nm /lib/modules/2.6.16.21-0.8-smp/kernel/drivers/infiniband/core/ib_core.ko | grep ib_al...

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

...784 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

...hdog, mptbase, e1000, ixgb, > tg3, aacraid, ahci, ata_piix, iscsi_sfnet, libata, qla2100, > qla2200, qla2300, qla2322, qla2xxx, qla6312, sata_nv, > sata_promise, sata_svw, sata_sx4, sata_vsc, cifs > * Driver additions including > bnx2, dell_rbu, ib_mthca, megaraid_sas, qla2400, typhoon > > - Security enhancements: > * Execshield updates > * Begin use of gcc FORTIFY_SOURCE build option in some > package updates > * SELinux policy updates > * Updated kernel key management support > > - Syst...

...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:[<ffffffff81100a7a>] [<ffffffff81100a7a>] bio_add_page+0xa/0x40 > [ 605.11...

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