From nobody Mon May 12 18:25:43 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 4Zx7Mh18Ywz5vcys for ; Mon, 12 May 2025 18:25:52 +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 4Zx7Mg1bfRz45pv; Mon, 12 May 2025 18:25:51 +0000 (UTC) (envelope-from pete@nomadlogic.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=nomadlogic.org header.s=04242021 header.b=Esmqjarl; 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=1747074325; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=e9tWEpMG+COpVblfO/MiBWmCJbi2FnYHa4/AeKx+j1c=; b=EsmqjarlR5EeQuYYXo43CZQV0XBAQbcJKsPJo7kFLDYCFt0LqO1pBM299La9e4ZnOOyvy3 szununpE0wPlOCHcDtbWDpmhYuxqEtyWO3Re4cnsblUNqcqYQwJMUN6OsIPlk0YOaxf3X5 XoCYeATmDATk/WNS3Erx9C6alQJ0ZM4= 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 6ed6108c (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Mon, 12 May 2025 18:25:25 +0000 (UTC) Message-ID: <527aa929-4083-4935-8147-e59b6416c3bf@nomadlogic.org> Date: Mon, 12 May 2025 11:25:43 -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 Subject: Re: ena(4) tx timeout messages in dmesg To: Colin Percival , freebsd-cloud@FreeBSD.org Cc: Arthur Kiyanovski References: <01000196c5b6fa5f-b8ed430e-23ca-47fd-9dd9-374a1de9c67c-000000@email.amazonses.com> Content-Language: en-US From: Pete Wright In-Reply-To: <01000196c5b6fa5f-b8ed430e-23ca-47fd-9dd9-374a1de9c67c-000000@email.amazonses.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4Zx7Mg1bfRz45pv X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.97 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.97)[-0.970]; DMARC_POLICY_ALLOW(-0.50)[nomadlogic.org,quarantine]; R_SPF_ALLOW(-0.20)[+mx]; R_DKIM_ALLOW(-0.20)[nomadlogic.org:s=04242021]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; TO_DN_SOME(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:29802, ipnet:66.165.240.0/22, country:US]; RCVD_COUNT_ONE(0.00)[1]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-cloud@FreeBSD.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[nomadlogic.org:+] On 5/12/25 11:17, Colin Percival wrote: > [+ akiyano, maintainer of the ena(4) driver] > > On 5/12/25 11:04, Pete Wright wrote: >> 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. > > I've heard that this can be caused by a thread being starved for CPU, > possibly > due to FreeBSD kernel scheduler issues, but that was on a far more heavily > loaded system.  What instance type are you running on? > oh of course, forgot to provide useful info: # uname -ar FreeBSD airflow-nfs.q0.ringdna.net 14.2-RELEASE-p1 FreeBSD 14.2-RELEASE-p1 GENERIC amd64 Instance type: t3a.xlarge I also verified I have plenty of available "burstable credit" available since this is a t class system (current balance is steady at 2,300 credits). the exported filesystem resides on a dedicated zfs pool, and the dataset itself can reside fully in memory as such there is basically zero disk i/o happening while serving %99 reads from nfsd. the virtual-env is ~500MB thanks! -pete -- Pete Wright pete@nomadlogic.org