Date: Wed, 7 Jan 2026 14:39:53 -0800 From: Adrian Chadd <adrian@freebsd.org> To: Mark Johnston <markj@freebsd.org> Cc: Renato Botelho <garga@freebsd.org>, Gleb Smirnoff <glebius@freebsd.org>, freebsd-current@freebsd.org, src-committers@freebsd.org, "David E. O'Brien" <obrien@freebsd.org> Subject: Re: December 2025 stabilization week Message-ID: <CAJ-Vmo=0dZujrsZaP=sTAqvh01VLuANKh4Q_4337PONZ3iAYLA@mail.gmail.com> In-Reply-To: <aV7TmgFqbsQGc0OM@nuc> References: <aUkIoWMkgaBtQkZD@cell.glebi.us> <aUrYyGG0Gil_oJ6a@cell.glebi.us> <aV1T0NA63Qc_MasK@cell.glebi.us> <a224a8fd-1ed1-40bf-8cab-a37d96845ebc@FreeBSD.org> <aV7TmgFqbsQGc0OM@nuc>
index | next in thread | previous in thread | raw e-mail
On Wed, 7 Jan 2026 at 13:44, Mark Johnston <markj@freebsd.org> 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 bug mentioned s3 suspend/resume doesn't work with tpm disabled? What's up with that comment, any ideas? -ahome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=0dZujrsZaP=sTAqvh01VLuANKh4Q_4337PONZ3iAYLA>