Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 24 Jun 2025 11:42:45 -0700
From:      Cy Schubert <Cy.Schubert@cschubert.com>
To:        Gleb Smirnoff <glebius@freebsd.org>
Cc:        Cy Schubert <Cy.Schubert@cschubert.com>, Mark Johnston <markj@freebsd.org>, freebsd-current@freebsd.org, src-committers@freebsd.org
Subject:   Re: June 2025 stabilization week
Message-ID:  <20250624184245.7835628C@slippy.cwsent.com>
In-Reply-To: <aFrvvHQoZUgw-41W@cell.glebi.us>
References:  <aFkJwZgyZXgZkXiX@cell.glebi.us> <aFrjEdBQGUiNLRYL@cell.glebi.us> <aFrlQqfrom12q-hk@nuc> <20250624180418.C161A306@slippy.cwsent.com> <aFrqFmjSSQ8ULPp0@cell.glebi.us> <aFrvvHQoZUgw-41W@cell.glebi.us>

index | next in thread | previous in thread | raw e-mail

In message <aFrvvHQoZUgw-41W@cell.glebi.us>, Gleb Smirnoff writes:
> 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 disappea
> red
> 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 r
> epo
> T> is lagging behind.
>
> Confirmed.  The drm packages just need to be manually rebuilt from ports.

Ports are built against 14.2. Those of us using -CURRENT need to rebuild 
any kmod ports ourselves.


-- 
Cheers,
Cy Schubert <Cy.Schubert@cschubert.com>
FreeBSD UNIX:  <cy@FreeBSD.org>   Web:  https://FreeBSD.org
NTP:           <cy@nwtime.org>    Web:  https://nwtime.org

			e**(i*pi)+1=0




home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20250624184245.7835628C>