From nobody Wed Jan 07 22:52:12 2026 X-Original-To: freebsd-current@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 4dmjwG6BNHz6NQxC; Wed, 07 Jan 2026 22:52:14 +0000 (UTC) (envelope-from markj@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 "smtp.freebsd.org", Issuer "R12" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4dmjwG5VMVz3pYL; Wed, 07 Jan 2026 22:52:14 +0000 (UTC) (envelope-from markj@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1767826334; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=fxGSF8L26U9TQ5cZ1SlC010NfHoY/uTRsqAIZKwd9v0=; b=O4FPqISXZjGer0/a+3f3m71vpo5RY+9fuEOYAwjCLlv7e/6sxdsng0tKAiTB6hyU02oHv0 zTt1yZWNVCDKuM7BK/PpRQkzYAVUPnJF3PK7Z7eBELWxftcJBVDhylN5Sdqj4eSTImqfGY KKBeBdwLKq3gU1BmfVQcBi+ab+lVOePzfec8ooVpg9TWkE+slRgGtz7K4TnnS9o/wA+j9f K8sLwn+gpPtF6iU5mDGp15rs0L8x76THvq3yl8x9JkLYH7dyF3Q4nedaMyYHQXo0O1Um88 kgj84ZcqAyX+9z7RUTZga/vjO+rPJeoO6DyFQKQb1PiU01lns3eHi85+Qsf27g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1767826334; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=fxGSF8L26U9TQ5cZ1SlC010NfHoY/uTRsqAIZKwd9v0=; b=P5Tx/aXvGy7vBOvlGL0MbNmXeBRdqZgz2koJaVzy0/5edNLLVe2RB8MkE0FSO0JOt9cTUN o+lkw5fTN+WH6nQShY2gS+GgTG3Qs6HahSlWBrxITi2QRVdRRbK5XiElgsScCFCCIHJfJB nlRoM8l/xMbFEqoeRc5b7gq6FcHXFC4fGfyv7e8CqGeDUpebhMNNkthiZc9wdiqAjeuuuQ J5UeAufIjoj1T8n4osSySyHM4N5DKEekBoiSoeg3VE18gLAoFOhoRcRRdYz+QjXKnbw2y9 auPXKcAzwDwYGF3dd4zxZOfEaSoUkwDuUd5lk9WdLMXMAvyEGKs+aQCHUakZEQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1767826334; a=rsa-sha256; cv=none; b=AdWJVH7Sr6WInEb85XCNYhwA4jhuaJ3Qh3wBIn3X6a/ktU/Zf0SfmpCDI2xpNKX/PDV7xV JTlgg2rffxDoAwULMyGdD4TnFT/nxIT/WNrYAwbQzBt56hWPYHppZoWKmOHS0zxPyo/H/c Ph8tIWvMErskxzcUxdukC9Rj4+SrZNpbhju/mLqZIcbFrLNOPLFdJ5CKGhFA9tYjL0yjLk vPbt9YuRJNzrle4BpSukWvh+gQOmbejWUqEHu3ZnhbZs64cza7HlvvtbB43EHfM57oRQk8 7vdO12ueQt0y6FXO8AgsM9/DVXo80ME7hShp1SO1AYkaHynNfGbkhQXBZqXl+w== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from nuc (192-0-220-237.cpe.teksavvy.com [192.0.220.237]) (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) (Authenticated sender: markj) by smtp.freebsd.org (Postfix) with ESMTPSA id 4dmjwG3XTcz8wD; Wed, 07 Jan 2026 22:52:14 +0000 (UTC) (envelope-from markj@freebsd.org) Date: Wed, 7 Jan 2026 17:52:12 -0500 From: Mark Johnston To: Adrian Chadd Cc: Renato Botelho , Gleb Smirnoff , freebsd-current@freebsd.org, src-committers@freebsd.org, "David E. O'Brien" Subject: Re: December 2025 stabilization week Message-ID: References: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Wed, Jan 07, 2026 at 02:39:53PM -0800, Adrian Chadd wrote: > On Wed, 7 Jan 2026 at 13:44, Mark Johnston wrote: > > > > [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291067 > > > > Indeed, I propose simply removing the driver from amd64 kernels for now: > > https://reviews.freebsd.org/D54587 > > Did it work before? I'm looking to see whether the change added tpm or > some way to gather entropy from it. The change added to tpm to GENERIC and enabled entropy harvesting by default. Users have reported that resume from S3 fails whenever tpm is compiled in the kernel, no matter whether or not harvesting is configured. > The bug mentioned s3 suspend/resume doesn't work with tpm disabled? > What's up with that comment, any ideas? Yes, see the bugzilla link. I noticed that we don't disable the harvester when suspending, so I wrote a patch to do that, see D53835. Apparently it's not sufficient. I suspect we have to do more and reinitialize the tpm firmware when resuming, but I don't have time right now to look further.