From nobody Thu Jan 27 22:43:30 2022 X-Original-To: bugs@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 859A81992D1D for ; Thu, 27 Jan 2022 22:43:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4JlFxH3ZXZz3nbh for ; Thu, 27 Jan 2022 22:43:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id ACDFC1F3A5 for ; Thu, 27 Jan 2022 22:43:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 20RMhUxg009437 for ; Thu, 27 Jan 2022 22:43:30 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 20RMhUrM009436 for bugs@FreeBSD.org; Thu, 27 Jan 2022 22:43:30 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 261291] ESX NFS4.1 client hangs, server never responds to EXCHANGE_ID/CREATE_SESSION Date: Thu, 27 Jan 2022 22:43:30 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 13.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rmacklem@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bugs@freebsd.org MIME-Version: 1.0 ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1643323411; 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=IXbtqe2ojpdaSlnDYEueQMvW++pUKBnUzfowtFuoUxs=; b=KTaqhlNaQ5L4QrGKsHQ8pNrMr4LE1MMYEyA8/A5LWrdEKi3d+nOEdQOEp4+/yJtw6Z3ADa 1oH2tKRkZJrBNuPHtaZ1m/FKcnM8imIQEQkZsX0O3CwvRLYw98R5HxHZW0B52Ho2a8t8O/ E1qUeIFNIqgBY9XTpufhbJB4s2sMHMwfe6kIbfWf511F8RrHrCBVaZFo4aE4r3lXWTrCtE h9JNyJQRD5ClHS+fCt/WD7OZ2Dl5sW9LN8qH6hakRD4+jYSCS6SK2eA9cPgM/pRVHpLkjx dyXIDXa/kqhxHfl8+2/3A+DToq8AY+p+6yyz2aEAlBXPFKBpie1C6NrdQ0HZjw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1643323411; a=rsa-sha256; cv=none; b=UxKvDRRA8PCYzCQ/Xhba9X0RM3BFics7Jv2M4PWSSp2b1h1UwxnmDbUutRfgnZB22POdAN VW1Thrh1Xt86b51TtEFnCtbpMQz8bwKEL7zQ9Lk9o9V5DBtbQ7cOM6E4g+FXUlvPuroEJe qHyPmBRgaxZQPzdubePjzj3gxMIf5on1lMwtLHr8TIPnYMFzZvPTM1JKO2CRABOhIIHNc1 TjSey0JtvlxKhLZzHIYx0Ye/+gDx2OJDVziz+IpjE7Q3C6lirgbk9t/FcLCGQ1yMTWBIgj FYXRJTTb+7Rnx+8km9uU4JMeU7N979n6PRZ1hY23egn2Jt/romMbKCJvfNf2Wg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D261291 --- Comment #8 from Rick Macklem --- When I looked at the packet trace, I noted where the problem occurred, which was long before the ExchangeID repeats. (I think the client is somehow trying to recover, but in a weird way.) In the packet trace, there was no reply to the request in packet #644. It is a packet with two compounds in it, but Linux does that to the server without any problems, from time to time. If there is no "stuck" TCP connection and no hung nfsd threads, then hmm... I'll take another look at the packet trace (I think I still have it), focusing on the session (sequence ops) around where the request does not get a reply. --> Is it possible for your server's net interface to drop a reply such that it doesn't show up in the packet trace? --> Did you try disabling TSO, which is the most common breakage for net interfaces and their device drivers. Actually, the fact that there is no non-zero RecvQ is good news, since that indicates that the PR256280 breakage isn't still broken. --=20 You are receiving this mail because: You are the assignee for the bug.=