Date: Fri, 4 Mar 2022 17:36:20 -0800 From: Mark Millard <marklmi@yahoo.com> To: bob prohaska <fbsd@www.zefox.net> Cc: freebsd-arm@freebsd.org Subject: Re: Panic while making buildlernel on RPi3 Message-ID: <29044F99-661A-4C75-9493-28857DAB963F@yahoo.com> In-Reply-To: <E30ECA49-14A0-49A1-9B36-BE25FD646CBF@yahoo.com> References: <20220304214836.GA21411@www.zefox.net> <E30ECA49-14A0-49A1-9B36-BE25FD646CBF@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2022-Mar-4, at 17:29, Mark Millard <marklmi@yahoo.com> wrote: > On 2022-Mar-4, at 13:48, bob prohaska <fbsd@www.zefox.net> wrote: >=20 >> For the first time a panic has occurred while making buildkernel >> on an RPi3. The same machine successfully ran stress2's misc/all.sh >> test suite for a couple of days, so I'm surprised. Granted, that was >> a few updates ago and this is on -current, but still..... buildkernel >> is not the trigger expected. >>=20 >> The backtrace and build logs >=20 > Unfortunately, the crash means that the buffers were not > flushed to media when the problem occurred. The build log > is incomplete compared to what actually built and where > it actually stopped. >=20 > So I'm not sure how you got: >=20 > --- ng_pppoe.kld --- > ld: error: no input files > *** [ng_pppoe.kld] Error code 1 Poorly worded on my part. I mean that I'm not sure how you would know it was "in the same place" when you re-ran. > When I looked at the buildkernel.log file provided, > it stopped without such: >=20 > --- all_subdir_netgraph --- > Building = /usr/obj/usr/src/arm64.aarch64/sys/GENERIC/modules/usr/src/sys/modules/net= graph/pptpgre/ng_pptpgre.o >=20 > It had no more. >=20 >=20 > With the then-running kernel file and its .debug file in > place, it would be possible to dump the instructions > in _rm_rlock_debug(), sysctl_root_handler_locked(), > sysctl_root(), and so on. Someone might then be able to > associate the code around: >=20 > _rm_rlock_debug+0x8c > sysctl_root_handler_locked+0x140 > sysctl_root+0x1ac > userland_sysctl+0x140 >=20 > with whatever corresponds in the source code. >=20 >> are at=20 >> http://www.zefox.net/~fbsd/rpi3/crashes/20220304/readme >> but unfortunately I didn't anticipate trouble and so didn't >> capture very much. >>=20 >=20 >=20 =3D=3D=3D Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?29044F99-661A-4C75-9493-28857DAB963F>