From nobody Tue May 13 17:22:18 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 4Zxjw52CZJz5vgSH for ; Tue, 13 May 2025 17:22:29 +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 4Zxjw41VZzz414s for ; Tue, 13 May 2025 17:22:27 +0000 (UTC) (envelope-from pete@nomadlogic.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=nomadlogic.org header.s=04242021 header.b=14mY54m0; 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=1747156918; 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: in-reply-to:in-reply-to:references:references; bh=Yzk5p3wO3q9xSYeUOJTxarlvFYY6fKOT66dtNPEDGHk=; b=14mY54m0a3+qSL2gLc4CFCQT0OVCobZ/VEntT/YEpPWbgDHACzuO9khZU4e/cSozfEVLM0 UoDvuLASF8tQDTOhqe0g9zseg6LDFOHpuvlussHhdzfAdXkOId6hE5PyqZPUMCujKDEixO 1vdsufWz61pdQpECJjQoMj02aLk/MvU= 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 5e08f01b (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO) for ; Tue, 13 May 2025 17:21:58 +0000 (UTC) Message-ID: <2fe4e22b-acde-4a43-9359-bd6a4e028a37@nomadlogic.org> Date: Tue, 13 May 2025 10:22:18 -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 From: Pete Wright To: freebsd-cloud@FreeBSD.org References: Content-Language: en-US In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Zxjw41VZzz414s X-Spamd-Bar: - X-Spamd-Result: default: False [-1.35 / 15.00]; NEURAL_HAM_SHORT(-1.00)[-0.995]; NEURAL_SPAM_LONG(0.97)[0.971]; DMARC_POLICY_ALLOW(-0.50)[nomadlogic.org,quarantine]; NEURAL_HAM_MEDIUM(-0.33)[-0.330]; R_DKIM_ALLOW(-0.20)[nomadlogic.org:s=04242021]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:29802, ipnet:66.165.240.0/22, country:US]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-cloud@FreeBSD.org]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-cloud@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[nomadlogic.org:+] 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. > > So I've found an interesting pattern, the above messages get printed to /var/log/messages and the dmesg buffer when i "su" to root apparently: May 9 19:19:23 airflow-nfs su[66523]: ec2-user to root on /dev/pts/3 May 9 19:19:23 airflow-nfs kernel: 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. May 9 19:19:23 airflow-nfs kernel: 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. M May 12 17:55:25 airflow-nfs su[29272]: ec2-user to root on /dev/pts/0 May 12 17:55:25 airflow-nfs kernel: 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. May 12 17:55:25 airflow-nfs kernel: Found a Tx that wasn't completed on time, qid 1, index 975. 1 msecs have passed since last cleanup. Missing Tx timeout value 5000 msecs. May 12 17:55:25 airflow-nfs kernel: Found a Tx that wasn't completed on time, qid 1, index 428. 1 msecs have passed since last cleanup. Missing Tx timeout value 5000 msecs. May 13 17:17:14 airflow-nfs su[16099]: ec2-user to root on /dev/pts/0 May 13 17:17:14 airflow-nfs kernel: Found a Tx that wasn't completed on time, qid 1, index 289. 1 msecs have passed since last cleanup. Missing Tx timeout value 5000 msecs. May 13 17:17:14 airflow-nfs kernel: Found a Tx that wasn't completed on time, qid 1, index 159. 1 msecs have passed since last cleanup. Missing Tx timeout value 5000 msecs. I have no idea what that means, but certainly feels like an interesting data-point. i'm ssh'ing as the ec2-user, then "su -" to become root and as you can see from the timestamps something triggers those log events. i'm not seeing any other occurances of these log messages outside of su'ing too. this is a very vanilla system, not krb auth or other network interactions should happen when i become root. -pete -- Pete Wright pete@nomadlogic.org