From nobody Wed Oct 23 06:20:49 2024 X-Original-To: freebsd-net@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4XYJp237ckz5ZtDm for ; Wed, 23 Oct 2024 06:20:58 +0000 (UTC) (envelope-from lexi@le-fay.org) Received: from fuchsia.eden.le-Fay.ORG (fuchsia.eden.le-fay.org [81.187.47.195]) by mx1.freebsd.org (Postfix) with ESMTP id 4XYJp11Bl4z40dT for ; Wed, 23 Oct 2024 06:20:57 +0000 (UTC) (envelope-from lexi@le-fay.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=le-fay.org header.s=fuchsia header.b=TJ02FdRB; spf=pass (mx1.freebsd.org: domain of lexi@le-fay.org designates 81.187.47.195 as permitted sender) smtp.mailfrom=lexi@le-fay.org; dmarc=none Received: from iris.eden.le-Fay.ORG (iris.eden.le-fay.org [IPv6:2001:8b0:aab5:4::1]) by fuchsia.eden.le-Fay.ORG (Postfix) with ESMTP id 4488D37B6E for ; Wed, 23 Oct 2024 06:20:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=le-fay.org; s=fuchsia; t=1729664450; bh=s0TIEegeM9y6KXIucipbdOo6UFysqR3+nYG/t1tWk/k=; h=Date:To:From:Subject; b=TJ02FdRBqmO4eQJ4v8aHwyrfkYPeqsaiUIfBMJdLd+QJIwPb+WD6pwVJH53RsYgc9 Xv2rfZOOhCEQCBi/UAHiXHjRja2S7j1VOtG4X5nTveMtjRnShyWMU5EUwig+jwZ3hR 4tx2Z8s0Niga+KLVW38iQdK1ueMrqDOYSNHDUiE8= Received: from [IPV6:2001:8b0:aab5:c210:899b:3939:5d83:3445] (unknown [IPv6:2001:8b0:aab5:c210:899b:3939:5d83:3445]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (secp384r1) server-digest SHA384) (No client certificate requested) by iris.eden.le-Fay.ORG (Postfix) with ESMTPSA id AD00E2C0475 for ; Wed, 23 Oct 2024 07:20:49 +0100 (BST) Message-ID: Date: Wed, 23 Oct 2024 07:20:49 +0100 List-Id: Networking and TCP/IP with FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-net List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-net@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-GB To: freebsd-net@freebsd.org From: Lexi Winter Subject: Chelsio / cxlv(4): strange messages, SR-IOV interface does not work Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-3.39 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[le-fay.org:s=fuchsia]; R_SPF_ALLOW(-0.20)[+ip4:81.187.47.195]; RCVD_NO_TLS_LAST(0.10)[]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:20712, ipnet:81.187.0.0/16, country:GB]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; DMARC_NA(0.00)[le-fay.org]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-net@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-net@freebsd.org]; DKIM_TRACE(0.00)[le-fay.org:+] X-Rspamd-Queue-Id: 4XYJp11Bl4z40dT X-Spamd-Bar: --- hello, i'm trying to configure a cxlv(4) device, which is a VF of a Chelsio T540-CR on a host running bhyve. host: FreeBSD 15.0-CURRENT #3 lf/main-n269068-2cff93ced1d: Wed Oct 23 02:48:20 BST 2024 guest: FreeBSD 15.0-CURRENT #2 lf/main-n269067-56dd459904b: Sat Oct 19 18:36:40 BST 2024 the VF appears correctly in the VM: root@lily:~ # kldload if_cxlv t5vf0: mem 0xc000e000-0xc000efff,0xc0000000-0xc0007fff,0xc0008000-0xc0009fff at device 6.0 on pci0 t5vf0: 1 ports, 2 MSI-X interrupts, 4 eq, 2 iq cxlv0: on t5vf0 cxlv0: 2 txq, 1 rxq (NIC) and after bringing the interface 'up' everything seems fine: root@lily:~ # ifconfig cxlv0 cxlv0: flags=1008843 metric 0 mtu 1500 options=6ec07bb ether 06:44:3f:e7:60:30 media: Ethernet 10Gbase-Twinax (10Gbase-Twinax ) status: active nd6 options=29 however, trying to assign an IP address causes immediate problems: root@lily:~ # ifconfig cxlv0 inet6 2001:8b0:aab5:7::10/64 root@lily:~ # Oct 23 06:16:07 lily kernel: cxlv0: a looped back NS message is detected during DAD for fe80:3::444:3fff:fee7:6030. Another DAD probes are being sent. root@lily:~ # dmesg|grep loop cxlv0: a looped back NS message is detected during DAD for fe80:3::444:3fff:fee7:6030. Another DAD probes are being sent. cxlv0: a looped back NS message is detected during DAD for fe80:3::444:3fff:fee7:6030. Another DAD probes are being sent. cxlv0: a looped back NS message is detected during DAD for fe80:3::444:3fff:fee7:6030. Another DAD probes are being sent. cxlv0: a looped back NS message is detected during DAD for fe80:3::444:3fff:fee7:6030. Another DAD probes are being sent. cxlv0: a looped back NS message is detected during DAD for fe80:3::444:3fff:fee7:6030. Another DAD probes are being sent. cxlv0: a looped back NS message is detected during DAD for fe80:3::444:3fff:fee7:6030. Another DAD probes are being sent. cxlv0: a looped back NS message is detected during DAD for fe80:3::444:3fff:fee7:6030. Another DAD probes are being sent. i find this strange because the link local IP address in the kernel error is not even configured on the interface: root@lily:~ # ifconfig cxlv0 cxlv0: flags=1008843 metric 0 mtu 1500 options=6ec07bb ether 06:44:3f:e7:60:30 inet6 2001:8b0:aab5:7::10/64 inet6 fe80::444:3fff:fee7:6030%cxlv0/64 tentative scopeid 0x3 media: Ethernet 10Gbase-Twinax (10Gbase-Twinax ) status: active nd6 options=21 am i doing something wrong here? thanks, lexi.