Date: Fri, 11 Jun 2021 09:18:32 +0200 From: Hans Petter Selasky <hps@selasky.org> To: "Herbert J. Skuhra" <herbert@gojira.at>, freebsd-arm@freebsd.org Subject: Re: Easily reproducible stable/13 kernel crash Message-ID: <6d268f28-373e-fd84-9fe8-9e39831760e5@selasky.org> In-Reply-To: <87wnr0vq79.wl-herbert@gojira.at> References: <63c37775-f1f6-def7-1ca2-4ac0460c46e2@shrew.net> <87y2bhuehz.wl-herbert@gojira.at> <87wnr0vq79.wl-herbert@gojira.at>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/11/21 9:02 AM, Herbert J. Skuhra wrote: > On Fri, 11 Jun 2021 08:00:56 +0200, "Herbert J. Skuhra" wrote: >> >> On Fri, 11 Jun 2021 07:42:27 +0200, Matthew Grooms wrote: >>> >>> Hey all, >>> >>> If I build an up-to-date stable/13 arm64 kernel and type sysctl -a on >>> a rpi4 system, it reboots every time. I've blown away the source and >>> object tree multiple times and still get the same result. >>> >>> FreeBSD generic 13.0-STABLE FreeBSD 13.0-STABLE #1 >>> stable/13-n245932-04c4bd7f7b5: Fri Jun 11 00:09:11 CDT 2021 >>> mgrooms@x.x.x:/var/rpi4/build/usr/src/arm64.aarch64/sys/GENERIC arm64 >>> >>> Has anyone else been testing stable builds recently? I'll try to build >>> a debug kernel and see if I can dig up more info. >> >> I can confirm this issue: Rasperry Pi 2 (armv7), 3 and 4 (both aarch64). >> When booting kernel.old (from May 17th; e0f2b8aaf1ed) 'sysctl -a' >> doesn't crash the system. > > The kernel from the May 27th snapshot (stable/13-n245691-024a9aa7010) > is OK, the one from June 3rd (13-n245852-4775325dd66) isn't. > Do you have the kernel backtrace of the resulting panic? --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6d268f28-373e-fd84-9fe8-9e39831760e5>