Date: Thu, 25 Aug 2022 12:38:18 +0200 From: Marek Soudny <soumar@soudny.net> To: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: wireguard, was: kernel: Fatal data abort - issue on rpi4 Message-ID: <998e444a-e15a-005d-f411-8b6d0548a5c2@soudny.net> In-Reply-To: <182d4586275.c5ad92b7110345.909616784164730917@bluelife.at> References: <15b7779f-db37-efd7-69ba-378636b93017@soudny.net> <Yv1zyQob9Q0aHLm%2B@phouka1.phouka.net> <e71cbb3f-2f69-a913-1b85-e1df9d1d8eb1@soudny.net> <YwOO0eaMbMBowyRv@phouka1.phouka.net> <e937fef0-5c28-27ac-2f36-41991d344610@soudny.net> <182d4586275.c5ad92b7110345.909616784164730917@bluelife.at>
next in thread | previous in thread | raw e-mail | index | archive | help
> There is no need to waste any more time on this. We have seen this all > already and it's caused because all ports (latest and quarterly branch) for > FreeBSD 13.x are build on 13.0 currently. But because of an ABI break in > 13.1 the wireguard kernel module will panic when used. > > FreeBSD 13.0 is EoL in less than a week (August 31, 2022), so official > package builders will switch soon - the next full build will not have that > problem anymore. > > -- > Bernhard Fröhlich > https://www.bluelife.at/ > Thank you for the info! I think I can wait 2-3 weeks for official packages. Thank you, Marek
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?998e444a-e15a-005d-f411-8b6d0548a5c2>