Date: Tue, 24 Jun 2025 11:34:36 -0700 From: Gleb Smirnoff <glebius@freebsd.org> To: Cy Schubert <Cy.Schubert@cschubert.com> Cc: Mark Johnston <markj@freebsd.org>, freebsd-current@freebsd.org, src-committers@freebsd.org Subject: Re: June 2025 stabilization week Message-ID: <aFrvvHQoZUgw-41W@cell.glebi.us> In-Reply-To: <aFrqFmjSSQ8ULPp0@cell.glebi.us> References: <aFkJwZgyZXgZkXiX@cell.glebi.us> <aFrjEdBQGUiNLRYL@cell.glebi.us> <aFrlQqfrom12q-hk@nuc> <20250624180418.C161A306@slippy.cwsent.com> <aFrqFmjSSQ8ULPp0@cell.glebi.us>
index | next in thread | previous in thread | raw e-mail
On Tue, Jun 24, 2025 at 11:10:30AM -0700, Gleb Smirnoff wrote: T> C> > > - Laptop with Intel graphics - drm61 kmod is broken due to disappeared T> C> > > vm_page_lock_KBI(). T> C> > T> C> > What exactly is the problem there? Are your drm kmods built against the T> C> > same kernel you're running? T> C> T> C> This problem was fixed a couple of weeks ago when patches were applied to T> C> the drm-66-kmod port. Make sure ports are up to date. T> T> Yes, looks like ports are buildable at least. Probably FreeBSD-kmods pkg repo T> is lagging behind. Confirmed. The drm packages just need to be manually rebuilt from ports. -- Gleb Smirnoffhelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aFrvvHQoZUgw-41W>