From nobody Wed Sep 18 19:07:36 2024 X-Original-To: net@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 4X87Sm35hPz5XJC8 for ; Wed, 18 Sep 2024 19:07:36 +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 "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4X87Sl6v4Mz4lnL for ; Wed, 18 Sep 2024 19:07:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1726686456; a=rsa-sha256; cv=none; b=Ab5W/qcJui3enXKR5YVvWseBFna7vUypzcby/g7ORpjI3Zuc8DLqFPbIEr5duCB8EV/KxZ 77xZ1TjEj+O6uB3W7xPooHRfEbatcW5yvRJLsJ7EDbdgqgORSVsgPSqGyxsr6fERob1dkD 65VfT3MPlFrrXECCPkYoJzyFGZv7n/SIMsjlmB8Ht9DITmD+49hLny9fhuUEUxbcogfKKM XWLjk23YYd5oUy5aa6BlrGTdfcfNAffwnCPcv1gRdNPXk5FgJlv6jiiGtWHdEKMc5TF6U3 ksfYLRllEEeKJSKyivctPMLkH0JSzUz3O2usStYD0aD8p9oAPu73BrTrW8UxzA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1726686456; 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=JHFLvn0eEhxa3pbjSTwhMTTeffr27tPoptfsoTNlGcg=; b=Ytjc7SPyySOBvOt5jIpXb66C+0PhqBh3a0mPbLWxSkf/Vye8p6W9j1EI7BeEiSWtJjxISs 1KQR49CYPFgRDGS/g83DTBhbXhxnMzPhM4bBiC2kJLAZrGhutoFmOauafb6JlCm6SGri6Q vxg8ejTYZVKLYI69RUZ0HJSqgrA+vKnx8tCGYLvn6yVrQVAJNbYIWScemYqXb0tyrkiTAi sO69o9vhdukmkuDKaxM1c+Ag8eIWZ307AqoPDnNLF7OFYAoT+jvK3Bk9d6x1Sy/7ZFmXTp Pw9dm0DUQQ3ZCNilWupRbUhzoLj8jxLfos1qE5FvhX/0wtq01hgoTRyammhvTQ== 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 4X87Sl6NxPzZWH for ; Wed, 18 Sep 2024 19:07:35 +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 48IJ7ZQS096172 for ; Wed, 18 Sep 2024 19:07:35 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 48IJ7ZHn096171 for net@FreeBSD.org; Wed, 18 Sep 2024 19:07:35 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: net@FreeBSD.org Subject: [Bug 281560] gve (4) uma deadlock during high tcp throughput Date: Wed, 18 Sep 2024 19:07:36 +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: 14.1-RELEASE X-Bugzilla-Keywords: vendor X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: kib@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: net@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: Networking and TCP/IP with FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-net List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-net@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D281560 --- Comment #3 from Konstantin Belousov --- If you have WITNESS configured, then you can get an overview of the locks ownership on the system, using the 'show alllocks' ddb command. This should allow you to see lock owners, including the shared locks (like read-locked rwlocks). Another hint is that ddb 'ps' command output wchan ia the address of lock (or something very close to it) where the thread blocked. This should be enough to see the loops. Basically, take any blocked thread, see which lock it needs ('ps'), then find a thread that owns the lock. Now look at the backtrace of the lock owner and see why it does not make progre= ss, e.g. typically waiting for yet another lock, and so on. --=20 You are receiving this mail because: You are the assignee for the bug.=