On Wed, 2016-03-30 at 22:46 -0700, Nicholas A. Bellinger wrote: > Hi Patrick & Co, > > (Adding target-devel CC') (Adding missing target-devel CC' again) > > On Thu, 2016-03-24 at 19:24 +0000, Patrick Li-SSI wrote: > > Hi, Nicholas, > > > > > > > > When we use Mellanox connect-4 to set up ISER, whenever the initiator > > tries to connect the target(iser_enabled) with ISER interface. > > > > The target crashes. We list the /var/log/syslog below. > > > > The target is Ubuntu 14.04.4, kernel 4.2. > > > > We saw a few versions of ib_isert.c online. I attached the one is > > running now. > > > > http://lxr.free-electrons.com/source/drivers/infiniband/ulp/isert/ib_isert.c > > > > https://github.com/Canonical-kernel/Ubuntu-kernel/blob/master/drivers/infiniband/ulp/isert/ib_isert.c > > > > > > > > > > > > Any ideas/comments/suggestions are appreciated. > > > > <SNIP> > > > > > /var/log/syslog: > > > > > > > > Mar 23 18:11:11 msl-dsma-sierraes7 kernel: [ 897.928694] > > ------------[ cut here ]------------ > > > > Mar 23 18:11:11 msl-dsma-sierraes7 kernel: [ 897.928712] WARNING: > > CPU: 20 PID: 6713 at /var/lib/dkms/isert/1.0/build/ib_isert.c:1314 > > isert_rx_login_req+0x213/0x250 [ib_isert]() > > Mmmm. There is not a WARN_ON() at ib_isert.c:1314 in either of the URL > references above, so I assume your using some other modified version of > ib_isert with dkms, yes..? > > > > > Mar 23 18:11:11 msl-dsma-sierraes7 kernel: [ 897.928715] Modules > > linked in: ib_isert(OE) target_core_user uio target_core_pscsi > > target_core_file target_core_iblock iscsi_target_mod nfsv3 > > ipmi_devintf tcm_qla2xxx qla2xxx tcm_loop tcm_fc libfc > > scsi_transport_fc ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat > > nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack > > nf_conntrack ipt_REJECT nf_reject_ipv4 xt_CHECKSUM iptable_mangle > > xt_tcpudp target_core_mod bridge stp llc ip6table_filter ip6_tables > > iptable_filter ip_tables ebtable_nat ebtables x_tables cachefiles > > autofs4 nfsv4 intel_rapl iosf_mbi x86_pkg_temp_thermal > > intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul > > ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper > > ablk_helper cryptd ipmi_ssif input_leds joydev sb_edac ast ttm > > edac_core drm_kms_helper drm syscopyarea sysfillrect sysimgblt mei_me > > lpc_ich mei shpchp 8250_fintek ipmi_si rfcomm ipmi_msghandler bnep > > bluetooth acpi_power_meter acpi_pad mac_hid parport_pc ppdev knem(OE) > > nfsd lp parport auth_rpcgss nfs_acl nfs lockd grace sunrpc fscache > > rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) configfs ib_ipoib(OE) > > ib_cm(OE) ib_uverbs(OE) ib_umad(OE) mlx5_ib(OE) mlx4_ib(OE) ib_sa(OE) > > ib_mad(OE) ib_core(OE) ib_addr(OE) mlx4_en(OE) mlx4_core(OE) > > hid_generic megaraid_sas mlx5_core(OE) igb mlx_compat(OE) usbhid vxlan > > e1000e i2c_algo_bit ip6_udp_tunnel hid ahci udp_tunnel dca libahci ptp > > nvme pps_core > > So you're using the stock iscsi_target_mod, but with a ib_isert > backport.. > > ib_isert and iscsi_target_mod are joined rather closely at the hip, so > if your doing a ib_isert backport then you'll also need a > iscsi_target_mod backport to ensure matching versions too. > > Is there a reason you are not using mainline ib_isert to start..? > -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
