Date: Sat, 2 Apr 2022 21:58:00 +0200 From: Christian Weisgerber <naddy@mips.inka.de> To: freebsd-stable@freebsd.org Subject: Re: FreeBSD 13.1-RC1 Now Available Message-ID: <YkiqyGMaLK6k6/SV@lorvorc.mips.inka.de> In-Reply-To: <CANCZdfqx2pCDBeags7=pcC5pOEaKY5Gajy-uOHsQVUcGF1JdNw@mail.gmail.com> References: <20220401024029.GR76435@FreeBSD.org> <a16fe272-3e1a-c9d5-6e02-4b76f2502ee9@nicandneal.net> <8dc4c525-7117-4fc6-8b10-812128bf07c1@www.fastmail.com> <CANCZdfqx2pCDBeags7=pcC5pOEaKY5Gajy-uOHsQVUcGF1JdNw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Warner Losh:
> This suggests that we've broken the KBI we were trying to keep stable
> between 13.0
> and 13.1....
When I updated my stable/13 machine from source, from
March 16 to March 30, DRM was broken (did nothing).
Rebuilding graphics/drm-fbsd13-kmod fixed it.
So there was an ABI break in this time window. This entry from
UPDATING implicates LinuxKPI changes as a likely candidate:
20220327:
Bump __FreeBSD_verion to 1301501 after merging LinuxKPI and
net80211 changes in order to help out-of-tree consumers to deal
accordingly.
--
Christian "naddy" Weisgerber naddy@mips.inka.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YkiqyGMaLK6k6/SV>