From nobody Tue May 13 20:26:22 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 4Zxp0Y1QDZz5vvmZ for ; Tue, 13 May 2025 20:26:37 +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 4Zxp0W6yygz3nkv for ; Tue, 13 May 2025 20:26:35 +0000 (UTC) (envelope-from pete@nomadlogic.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=nomadlogic.org header.s=04242021 header.b=CjEb2uLw; 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=1747167964; 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=ga2jdT62R7DpzYUHoObcb7oKScMbIBicg8A0JjH9zpM=; b=CjEb2uLwcpdosRzmDiitq4TftSVb8t03LkVMcvK9iB2BFVihy2VJcN7+zY1u5ScO2J1/vg 0DWYFJzS0PfTSIViOCPbNb68SfKP14mCW++cL5jHOc+G3TfRHgfMwXYasHqk0DTy5AekNn wvCsz42jKQp4RMyR+3ohrIMkNxNvIrA= 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 2cd5c6f5 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Tue, 13 May 2025 20:26:02 +0000 (UTC) Message-ID: <8bc8c246-52bc-4fad-81d3-54f777893754@nomadlogic.org> Date: Tue, 13 May 2025 13:26:22 -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 References: <2fe4e22b-acde-4a43-9359-bd6a4e028a37@nomadlogic.org> <01000196cb23eca0-d4b771c7-f4a9-4406-bc20-4f8b7dff09d3-000000@email.amazonses.com> Content-Language: en-US From: Pete Wright In-Reply-To: <01000196cb23eca0-d4b771c7-f4a9-4406-bc20-4f8b7dff09d3-000000@email.amazonses.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4Zxp0W6yygz3nkv X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.87 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-0.99)[-0.993]; NEURAL_HAM_SHORT(-0.87)[-0.872]; 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)[]; ASN(0.00)[asn:29802, ipnet:66.165.240.0/22, country:US]; RCVD_TLS_ALL(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_ONE(0.00)[1]; TO_DN_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-cloud@FreeBSD.org]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[nomadlogic.org:+] On 5/13/25 12:34, Colin Percival wrote: > On 5/13/25 10:22, Pete Wright wrote: >> 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. >> [...] >> >> 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. > > Ooh, very interesting, and points to something I had wondered about > earlier. > There should be a line 'hw.broken_txfifo="1"' in /boot/loader.conf; can you > try removing that and see if the problem goes away?  (In fact, it's a > sysctl > so you can flip it on and off without taking the system down.) > > If the system reproducibly prints that warning with broken_txfifo=1 and > does > not print the warning with broken_txfifo=0, we have the culprit.  And I can > just remove that from EC2 images; it's a workaround for an old emulation > bug > which *should* be long since fixed in all EC2 instance types. > oh interesting! cool i've toggled that sysctl knob: # sysctl hw.broken_txfifo=0 hw.broken_txfifo: 1 -> 0 # i did an initial test and it looks good so far, i'll let it soak for the rest of the day today and check-in tomorrow. thanks Colin! -pete -- Pete Wright pete@nomadlogic.org