Bug 2152214

Summary:	[RHEL-9.2] rcopy fails on E810 iwarp
Product:	Red Hat Enterprise Linux 9	Reporter:	Brian Chae <bchae>
Component:	rdma-core	Assignee:	Kamal Heib <kheib>
Status:	CLOSED MIGRATED	QA Contact:	Infiniband QE <infiniband-qe>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.2	CC:	hwkernel-mgr, infiniband-qe, kheib, nobody, rdma-dev-team, zguo
Target Milestone:	rc	Keywords:	MigratedToJIRA
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	2117150	Environment:
Last Closed:	2023-09-21 14:32:15 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2117150
Bug Blocks:

Description Brian Chae 2022-12-09 19:07:34 UTC

+++ This bug was initially created as a clone of Bug #2117150 +++

Description of problem:


Version-Release number of selected component (if applicable):
Clients: rdma-dev-31
Servers: rdma-dev-30

DISTRO=RHEL-9.2.0-20221122.2

+ [22-12-05 23:58:30] cat /etc/redhat-release
Red Hat Enterprise Linux release 9.2 Beta (Plow)

+ [22-12-05 23:58:30] uname -a
Linux rdma-dev-31.rdma.lab.eng.rdu2.redhat.com 5.14.0-197.el9.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Nov 16 14:31:27 EST 2022 x86_64 x86_64 x86_64 GNU/Linux

+ [22-12-05 23:58:30] cat /proc/cmdline
BOOT_IMAGE=(hd0,gpt2)/vmlinuz-5.14.0-197.el9.x86_64 root=UUID=87accd11-ea2a-4af5-a8ca-f326ac50c8ba ro crashkernel=1G-4G:192M,4G-64G:256M,64G-:512M resume=UUID=1576e515-95f8-4d34-b3a3-07974d8a3c9f console=ttyS0,115200n81

+ [22-12-05 23:58:30] rpm -q rdma-core linux-firmware
rdma-core-41.0-3.el9.x86_64
linux-firmware-20221012-128.el9.noarch
+ [22-12-05 23:58:30] tail /sys/class/infiniband/irdma0/fw_ver /sys/class/infiniband/irdma1/fw_ver
==> /sys/class/infiniband/irdma0/fw_ver <==
1.52

==> /sys/class/infiniband/irdma1/fw_ver <==
1.52
+ [22-12-05 23:58:30] lspci
+ [22-12-05 23:58:30] grep -i -e ethernet -e infiniband -e omni -e ConnectX
04:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01)
04:00.1 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01)
04:00.2 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01)
04:00.3 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01)
44:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-C for QSFP (rev 02)
44:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-C for QSFP (rev 02)
hca_id:	irdma1
	transport:			iWARP (1)
	fw_ver:				1.52
	node_guid:			b696:91ff:fead:8aa9
	sys_image_guid:			b696:91ff:fead:8aa9
	vendor_id:			0x8086
	vendor_part_id:			5522
	hw_ver:				0x2
	phys_port_cnt:			1
	max_mr_size:			0x200000000000
	page_size_cap:			0x40201000
	max_qp:				131069
	max_qp_wr:			4063
	device_cap_flags:		0x00220000
					MEM_WINDOW
					MEM_MGT_EXTENSIONS
	max_sge:			13
	max_sge_rd:			13
	max_cq:				262141
	max_cqe:			1048574
	max_mr:				2097150
	max_pd:				262141
	max_qp_rd_atom:			127
	max_ee_rd_atom:			0
	max_res_rd_atom:		0
	max_qp_init_rd_atom:		255
	max_ee_init_rd_atom:		0
	atomic_cap:			ATOMIC_NONE (0)
	max_ee:				0
	max_rdd:			0
	max_mw:				2097150
	max_raw_ipv6_qp:		0
	max_raw_ethy_qp:		0
	max_mcast_grp:			131072
	max_mcast_qp_attach:		8
	max_total_mcast_qp_attach:	1048576
	max_ah:				131072
	max_fmr:			0
	max_srq:			0
	max_pkeys:			0
	local_ca_ack_delay:		0
	general_odp_caps:
	rc_odp_caps:
					NO SUPPORT
	uc_odp_caps:
					NO SUPPORT
	ud_odp_caps:
					NO SUPPORT
	xrc_odp_caps:
					NO SUPPORT
	completion timestamp_mask:			0x000000000001ffff
	core clock not supported
	device_cap_flags_ex:		0x220000
	tso_caps:
		max_tso:			0
	rss_caps:
		max_rwq_indirection_tables:			0
		max_rwq_indirection_table_size:			0
		rx_hash_function:				0x0
		rx_hash_fields_mask:				0x0
	max_wq_type_rq:			0
	packet_pacing_caps:
		qp_rate_limit_min:	0kbps
		qp_rate_limit_max:	0kbps
	tag matching not supported
	num_comp_vectors:		27
		port:	1
			state:			PORT_ACTIVE (4)
			max_mtu:		4096 (5)
			active_mtu:		4096 (5)
			sm_lid:			0
			port_lid:		1
			port_lmc:		0x00
			link_layer:		Ethernet
			max_msg_sz:		0x7fffffff
			port_cap_flags:		0x00050000
			port_cap_flags2:	0x0000
			max_vl_num:		invalid value (0)
			bad_pkey_cntr:		0x0
			qkey_viol_cntr:		0x0
			sm_sl:			0
			pkey_tbl_len:		0
			gid_tbl_len:		1
			subnet_timeout:		0
			init_type_reply:	0
			active_width:		4X (2)
			active_speed:		25.0 Gbps (32)


How reproducible:
Always

Steps to Reproduce:

Server:$ rcopy 
waiting for connection...

Client: $ rcopy /root/iser_lun 172.31.50.130
rconnect failed
: Operation not supported


Actual results:
rconnect failed
: Operation not supported

Expected results:
The file can be copied to the client.

Additional info:
If this is expected behavior, please close it. BTW, rcopy works on E810 roce.

Comment 1 Brian Chae 2022-12-14 08:46:20 UTC

*** Bug 2152213 has been marked as a duplicate of this bug. ***

Comment 2 RHEL Program Management 2023-09-21 14:28:54 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 3 RHEL Program Management 2023-09-21 14:32:15 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.