From nobody Fri Jan 26 00:39:51 2024 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 4TLf3W6cQVz58N4j for ; Fri, 26 Jan 2024 00:39:51 +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 4TLf3W3TwVz3xM9 for ; Fri, 26 Jan 2024 00:39:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1706229591; 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=NNohvxjtZmDl6pQyN+lCrM6x+TXIjylcun6yhQhBSKI=; b=H6O336eC4J4SLcRIqznTSy5bVyB2ioxsO7QFTkLNDDLVzThp0dARIV4WEWsXo4DWoz4irb JJdpLsnHCP10/77D1j/0lia6tfgjLh+ruKpD+jy3QsHS667wifs/KKAhCZvAi8/eVYQGMY mOa76QxaaY8orGsVNwEbD6JQtyZM1g2Z+1psqgTLTY90vJBwIhyhlJFymeSGAuxYD8YDX7 tRlb6SSxwjA+3oNplWw8BMJjHzS/QzAicMJDcYOAEKjwEIwpwCERt2rn8sbNvgtdaWfwWb yZcJIneMHmHgQsaTatXa0CQWDnNTq/Eda/yNlrSibeGAxZ9yGTGMnIvNWo9GrQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1706229591; a=rsa-sha256; cv=none; b=prC0tsw4PM+x5gww9pdBP/X/sS7R58H7rRjWv6ZboIDV5V85ayIj9Zg6Uaa7dNTVrTJU69 84MOUTWRf8os7JGUjmXlcTxiVXHZAAiP0VijrwZVI25MKSw92VDgc1sYpyARtfrY9yjYHm ZNhUSyOBjZ9b6HrL5qeKRxRBCuwgAElTqyiPMmPjUPka77/cDE10cCMEWXLjYBCLflRUph neOQSLWWHIAD/9MHUb37v2FhpYGAXW9bFpzJpyzVUJKXtHCbJsfLWG6Nr2DKlnmTiMJKK+ B6tXCK41bTkCTh+qwV75BrSHEKvRKNhSIXbrPVRIhVIkoU16XN28EONzSJ43+Q== 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 4TLf3W2ZHjzKr6 for ; Fri, 26 Jan 2024 00:39:51 +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 40Q0dpJJ032765 for ; Fri, 26 Jan 2024 00:39:51 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 40Q0dpT8032764 for bugs@FreeBSD.org; Fri, 26 Jan 2024 00:39:51 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 276587] ccp(4) causes 'sysctl -a' to hang when reading OID 'kern.geom.conftxt' Date: Fri, 26 Jan 2024 00:39:51 +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.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: freebsd@kumba.dev 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 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D276587 --- Comment #3 from Joshua Kinard --- (In reply to John Baldwin from comment #2) So it looks like I was wrong about ccp(4) seemingly working. It is still hanging when GEOM is initializing GELI on my swap drives, which I have two = in this system. What fooled me has two factors: 1. SSH came up and allowed me to login, and I never thought to look at the console 2. I recently changed the console resolution to 1280x1024, which generally works, but there is a large black rectangle being drawn over the bottom 1/8= th of the monitor, so I *thought* it was sitting at a login prompt, because I could see the swap/GELI bits printed out just above the rectangle. If that rectangle wasn't there, I'd have noticed it wasn't at a login prompt. So the reason 'sysctl -a' is hanging is because g_waitfor_event is still waiting for GELI to finish doing whatever it's stuck doing in trying to ini= t my encrypted swap volumes. That means Bug #253860 is still unfixed, so it needs to be re-opened. This= one is probably a duplicate of that bug, being a side-effect of GELI lost somew= here in space. If it helps, I can at least get you 'procstat -kk' outputs of the four GELI threads on the first encrypted swap volume, where it is stuck: > root 36041 0.0 0.0 0 16 - DL 18:50 0:00.00 [g_eli[= 0] da0p2] > root 36255 0.0 0.0 0 16 - DL 18:50 0:00.00 [g_eli[= 1] da0p2] > root 36973 0.0 0.0 0 16 - DL 18:50 0:00.00 [g_eli[= 2] da0p2] > root 37530 0.0 0.0 0 16 - DL 18:50 0:00.00 [g_eli[= 3] da0p2] > # procstat -kk 36041 > PID TID COMM TDNAME KSTACK > 36041 100531 g_eli[0] da0p2 - mi_switch+0xbb _slee= p+0x1ed g_eli_worker+0x37e fork_exit+0x7f fork_trampoline+0xe >=20 > # procstat -kk 36255 > PID TID COMM TDNAME KSTACK > 36255 100532 g_eli[1] da0p2 - mi_switch+0xbb _slee= p+0x1ed g_eli_worker+0x37e fork_exit+0x7f fork_trampoline+0xe >=20 > # procstat -kk 36973 > PID TID COMM TDNAME KSTACK > 36973 100686 g_eli[2] da0p2 - mi_switch+0xbb _slee= p+0x1ed g_eli_worker+0x37e fork_exit+0x7f fork_trampoline+0xe >=20 > # procstat -kk 37530 > PID TID COMM TDNAME KSTACK > 37530 100687 g_eli[3] da0p2 - mi_switch+0xbb _slee= p+0x1ed g_eli_worker+0x37e fork_exit+0x7f fork_trampoline+0xe This feels like there's a missed interrupt not being handled somewhere, so = the process(es) are forever waiting. Had my fair share of those on Linux when I played around with driver debugging long ago. --=20 You are receiving this mail because: You are the assignee for the bug.=