From nobody Mon May 12 18:04:50 2025 X-Original-To: freebsd-cloud@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 4Zx6vh1p8qz5vc69 for ; Mon, 12 May 2025 18:05:04 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [66.165.241.226]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Zx6vf5QT3z3vhs for ; Mon, 12 May 2025 18:05:02 +0000 (UTC) (envelope-from pete@nomadlogic.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=nomadlogic.org header.s=04242021 header.b=IgeSwbbF; spf=pass (mx1.freebsd.org: domain of pete@nomadlogic.org designates 66.165.241.226 as permitted sender) smtp.mailfrom=pete@nomadlogic.org; dmarc=pass (policy=quarantine) header.from=nomadlogic.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nomadlogic.org; s=04242021; t=1747073070; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=tLZ3JLkdO7Lr18p7w8tQy2wlnX8krJVQrieGySCKLWQ=; b=IgeSwbbFAehslWLsSLk0gxqOT81SrwN5flfhcCKq1HiUmBU6O/loKiiXd/uhNyo0BOI802 a/ssAdlbICnJEh79oZDvg6JnnZUcqEKOF7fuzQW91yCE5alBKqJNoH0rSNavYKMnCzPVFK jHLIsXuttPZG8XR0++znCSRjc8DIv9Y= Received: from [192.168.1.182] (47-154-20-141.fdr01.snmn.ca.ip.frontiernet.net [47.154.20.141]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 72a02da8 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO) for ; Mon, 12 May 2025 18:04:30 +0000 (UTC) Message-ID: Date: Mon, 12 May 2025 11:04:50 -0700 List-Id: FreeBSD on cloud platforms (EC2, GCE, Azure, etc.) List-Archive: https://lists.freebsd.org/archives/freebsd-cloud List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-cloud@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US To: freebsd-cloud@FreeBSD.org From: Pete Wright Subject: ena(4) tx timeout messages in dmesg Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Zx6vf5QT3z3vhs X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.994]; DMARC_POLICY_ALLOW(-0.50)[nomadlogic.org,quarantine]; R_DKIM_ALLOW(-0.20)[nomadlogic.org:s=04242021]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:29802, ipnet:66.165.240.0/22, country:US]; MLMMJ_DEST(0.00)[freebsd-cloud@FreeBSD.org]; RCPT_COUNT_ONE(0.00)[1]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-cloud@freebsd.org]; DKIM_TRACE(0.00)[nomadlogic.org:+] hey there - i have an ec2 instance that i'm using as a nfs server and have noticed the following messages in my dmesg buffer: ena0: Found a Tx that wasn't completed on time, qid 2, index 593. 10 msecs have passed since last cleanup. Missing Tx timeout value 5000 msecs. ena0: Found a Tx that wasn't completed on time, qid 2, index 220. 1 msecs have passed since last cleanup. Missing Tx timeout value 5000 msecs. ena0: Found a Tx that wasn't completed on time, qid 3, index 240. 1 msecs have passed since last cleanup. Missing Tx timeout value 5000 msecs. ena0: Found a Tx that wasn't completed on time, qid 3, index 974. 1 msecs have passed since last cleanup. Missing Tx timeout value 5000 msecs. ena0: Found a Tx that wasn't completed on time, qid 2, index 730. 1 msecs have passed since last cleanup. Missing Tx timeout value 5000 msecs. ena0: Found a Tx that wasn't completed on time, qid 2, index 864. 10 msecs have passed since last cleanup. Missing Tx timeout value 5000 msecs. ena0: Found a Tx that wasn't completed on time, qid 3, index 998. 1 msecs have passed since last cleanup. Missing Tx timeout value 5000 msecs. the system is not overly loaded, but does have a steady %25 CPU usage and averages around 2MB/sec network throughput (the system serves a python virtual-environment to a cluster of data processing systems). The man page states: "Packet was pushed to the NIC but not sent within given time limit. It may be caused by hang of the IO queue." I was curious if anyone had any idea if these messages indicate a poorly tuned system, or are they just informational. Looking at the basics like mbuf's and other base metrics and the system looks OK from that perspective. thanks! -pete -- Pete Wright pete@nomadlogic.org