Date: Tue, 24 Jun 2025 13:49:54 -0400 From: Mark Johnston <markj@freebsd.org> To: Gleb Smirnoff <glebius@freebsd.org> Cc: freebsd-current@freebsd.org, src-committers@freebsd.org Subject: Re: June 2025 stabilization week Message-ID: <aFrlQqfrom12q-hk@nuc> In-Reply-To: <aFrjEdBQGUiNLRYL@cell.glebi.us> References: <aFkJwZgyZXgZkXiX@cell.glebi.us> <aFrjEdBQGUiNLRYL@cell.glebi.us>
index | next in thread | previous in thread | raw e-mail
On Tue, Jun 24, 2025 at 10:40:33AM -0700, Gleb Smirnoff wrote: > Hi, > > On Mon, Jun 23, 2025 at 01:01:05AM -0700, Gleb Smirnoff wrote: > T> This is an automated email to inform you that the June 2025 stabilization week > T> started with FreeBSD/main at main-n278153-b2e0dfc808c1, which was tagged as > T> main-stabweek-2025-Jun. > > Status update for Tuesday: > > - Personal desktop with nVidia graphics - all OK. > - Laptop with Intel graphics - drm61 kmod is broken due to disappeared > vm_page_lock_KBI(). What exactly is the problem there? Are your drm kmods built against the same kernel you're running? > - Home router/server - all OK. > > At Netflix the A/B testing against previous stabweek didn't discover any > stability issues, however there is quite a lot of performance churn (nothing > critical though!) that we are now interpreting. > > There regression with devfs rules, reported by Michael in this thread. > > Let's keep the stabweek advisory code freeze on until Intel graphics and devfs > issues are addressed and at Netflix we get some more insight into performance > changes. > > -- > Gleb Smirnoffhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aFrlQqfrom12q-hk>