Date: Sat, 26 Feb 2022 18:42:06 -0800 From: Mark Millard <marklmi@yahoo.com> To: bob prohaska <fbsd@www.zefox.net> Cc: freebsd-net@freebsd.org, Free BSD <freebsd-arm@freebsd.org> Subject: Re: Erratic ping behavior, was Re: Pi3 answers ssh only if outbound ping is running on -current Message-ID: <8936EFD1-F1FD-48CF-9ED3-4D42595464DC@yahoo.com> In-Reply-To: <64138E81-2415-4D4A-A31A-D901DC53EB01@yahoo.com> References: <20220212185618.GA37391@www.zefox.net> <34F5C092-7C35-4CBB-9CC3-99E373D1F785@yahoo.com> <F5FC2E50-C1E8-4E84-B4D4-DC7BFC3C9C14@yahoo.com> <20220215034924.GA46139@www.zefox.net> <8F9A6C9A-69BF-4D42-9886-A3F08BCB2EA0@yahoo.com> <506CD1A7-3D34-4E1B-AEAA-A1A819C6CC73@yahoo.com> <B186B406-233A-4765-9B1B-EB8136D01F2B@yahoo.com> <20220216231826.GA54961@www.zefox.net> <64138E81-2415-4D4A-A31A-D901DC53EB01@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2022-Feb-17, at 00:02, Mark Millard <marklmi@yahoo.com> wrote: > On 2022-Feb-16, at 15:18, bob prohaska <fbsd@www.zefox.net> wrote: >=20 >> [changed subject to more clearly reflect the symptoms] >>=20 >> On Mon, Feb 14, 2022 at 09:59:23PM -0800, Mark Millard wrote: >>>>>>> Since I have a context working based on the kernel in: >>>>>>>=20 >>>>>>> = https://artifact.ci.freebsd.org/snapshot/stable-13/371633ece3ae88e3b3d7a02= 8c372d4ac4f72b503/arm64/aarch64/kernel.txz >>>>>>>=20 >>>>>>> I recommend that you try that exact same kernel in your >>>>>>> stable/13 context. I recommend renaming the existing >>>>>>> /boot/kernel before expanding the kernel.txz into / and >>>>>>> so causing a new /boot/kernel/ to be filled in. >>>=20 >>=20 >> It looks like the kernel isn't an obvious culprit: Versions >> from late October to a few days ago all behave the same way. >>=20 >> Even when booted single-user, with the ue0 device brought up >> by hand, only about 1% of incoming pings are answered. That >> figure rises to a little over 50% when there's an outgoing ping >> process (both running a 1/seccond). Destination of the ping >> does not seem to matter, an unused IP seems to work fine.=20 >>=20 >> AIUI, nothing of userland apart from a shell and the ping >> process will be running under those circumstances. Is this >> correct?=20 >>=20 >> Might the trouble be inherited from the boot files? I've left >> them alone since the machine does boot and updating them=20 >> isn't automated. Right now the machine boots from microSD >> and then runs bootcmd_usb0. >>=20 >> One oddity noticed during the kernel-swapping experiments >> is that at the loader prompt some kernel names don't seem >> to be recognized. If I type kernel or kernel.old it's >> loaded immediately. If I type kernel.no-bpf which is one >> I built, booted using the name kernel and then saved with >> the name kernel.no-bpf it can't be found, even though it's >> visible via ls at the OK prompt. Might - be a prohibited >> or priviledged character to the loader? Names like >> kernel.20220214 are likewise not recognized, even though >> they're visible using ls. There might be a name length restriction on the directory name that contains the kernel files? I know I used to have problems on old PowerMacs and got in the habit of using only short names. (So I've not challenged the assumption in a long time.) >> For lack of immediately better ideas I've started stress2 >> running in single-user mode to see if anything of interest >> results. The following are now available for experiments with microsd card boot media for testing: main [so: 14]: = http://ftp3.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/14.0/FreeBSD-14.0= -CURRENT-arm64-aarch64-RPI-20220224-45c23c2608e-253384.img.xz stable/13 as 13.1-PRERELEASE (no releng/13.1 branch yet): = http://ftp3.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/13.1/FreeBSD-13.1= -PRERELEASE-arm64-aarch64-RPI-20220224-9134a398506-249729.img.xz Can you repeat the problem with either of these as your boot media content? Which one(s)? =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?8936EFD1-F1FD-48CF-9ED3-4D42595464DC>