From nobody Tue Jun 24 17:40:33 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4bRXKc4fhKz6044W for ; Tue, 24 Jun 2025 17:40:36 +0000 (UTC) (envelope-from glebius@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4bRXKc18wCz4Hcs; Tue, 24 Jun 2025 17:40:36 +0000 (UTC) (envelope-from glebius@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1750786836; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=zLEzz6Zs3cHdtCupoNZ+0QToGXfir0DerHPseRbi+uc=; b=lK+b68/HXJ+f7r3hEryQKw+bx9+H7QfxnAb3jsWJVcAcoUGuR+lT7l0294pdsFkrJQaedh e+j8tD5ODCatF/9yHHPIfmuAI7g6wIZcZvHxI2vf4vyiZh9reY0fcy+/Pk6LkTyoV+3t9K ENNCxGv/Prn8DRR6+vobhl8K+W3l+S8c4tJ8/53gfLelAgd61RHaaSLKofS3I71ccs2N7Q ivqWv5eDcHq8bvIsOXEqBgXExAtAXld4bx2n7SIs3XJp9YM0Eox71eKoHBSLOBzO1gl+9O d/faBCYfVewMvYIZCGhN5yYzeternklgb1gqs5QXAMr+PA7ldj/LrvI0SBuWhw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1750786836; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=zLEzz6Zs3cHdtCupoNZ+0QToGXfir0DerHPseRbi+uc=; b=F+RkLogqa5AeZDmx/0NhCuNMP60PDKftBf7h1PnGgAOCodGV07s5+tJdLjKeQ5fDox0gk6 gXl74IsNK0b4hp8dw8UQgGDOgVRyUOsYvb2D8FaLqP8iGybx9pOnvelwsyXgZRCZ9qdBfK 9Hw/vHBqdUk/RG249F4PYzjvy4+ndqa1dYyQdd3QPhMANE4rUFxAEgDr5bTxUImUodrQWp bnxH5rgS2P50lYinAyeP1x4Vr7gC15S0p4gCzaTp5llWs2jTEBcLqy/7m4ZgwbDfyJzc3b 04iuI2NH9Ei2c7P7nAJGjzVE5a3GDTkkB9V78njwTwHA8G8tUOrcaR8Vc7NB4w== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1750786836; a=rsa-sha256; cv=none; b=HUeICAVR7wzMV/1eu6XMAGlUoxvfjJWdcN4MVepstFIxDNFSCKsAfXnyGnwUSUH9cO2djl rDGbeCFlym8D3rTU+q21oAbSkZgVPAfjyD32YdZxxLb+03GL2jEIsx+AHfQB/rdqEOl+dU bbddNkTXVwW2Ahr2K780pitD7okphLt+eUY9+orrtJ0jCfuJUaYED3YLNNMdjOe6Mbad21 CD+4AVEDGo6COy0dIMbQOh86Y1E4+wIlbbgMbtjG03apvy1o2N5Fj0JzDs5GQ1cGQW0If2 kEAVUj06CISS74wRf+FPq+AS1+2RHNk3uV3Vw2oiq90rfh8Cuun/5cVeB/8h1g== Received: from cell.glebi.us (glebi.us [162.251.186.162]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: glebius) by smtp.freebsd.org (Postfix) with ESMTPSA id 4bRXKb57YfzpFl; Tue, 24 Jun 2025 17:40:35 +0000 (UTC) (envelope-from glebius@freebsd.org) Date: Tue, 24 Jun 2025 10:40:33 -0700 From: Gleb Smirnoff To: freebsd-current@freebsd.org, src-committers@freebsd.org Subject: Re: June 2025 stabilization week Message-ID: References: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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(). - 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 Smirnoff