Date: Wed, 28 Jan 2026 12:49:26 -0800 From: Gleb Smirnoff <glebius@freebsd.org> To: freebsd-current@freebsd.org, src-committers@freebsd.org Cc: ShengYi Hung <aokblast@freebsd.org> Subject: Re: January 2026 stabilization week Message-ID: <aXp2VvOLn063IcUs@cell.glebi.us> In-Reply-To: <aXctKTNm_CEau0yB@cell.glebi.us>
index | next in thread | previous in thread | raw e-mail
On Mon, Jan 26, 2026 at 01:00:25AM -0800, Gleb Smirnoff wrote: T> This is an automated email to inform you that the January 2026 stabilization week T> started with FreeBSD/main at main-n283376-8ef8c6abfadf, which was tagged as T> main-stabweek-2026-Jan. The snapshot underwent A/B performance testing at Netflix and several people upgraded their laptops, desktops and home routers. Following problems were identified in this snapshot: 1) INVARIANTSs panic when using ipfw(4) dynamic rules. ipfw(4) users are recommended to cherry-pick d8a78048a246 and 29c3350f395a. 2) The AMD CPPC switched on by default instead of Cool`n'Quiet caused problems on certain hardware. For laptops see bug 292615. At Netflix A/B test we discovered that CPPC mode reports wrong frequency levels to powerd, which results in reduced performance. This problem is still not resolved. 3) Panic in vm_map code: https://people.freebsd.org/~novel/misc/core20260128.txt Note that this was discovered on pre-stabweek CURRENT. Only Roman seen this panic and there's no reproduce yet, so unresolved. The advisory code freeze is over. -- Gleb Smirnoffhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aXp2VvOLn063IcUs>