On 1/12/25 11:25, bob prohaska wrote:
From: bob prohaska <f...@www.zefox.net>
To: freebsd-ker...@freebsd.org
Subject: Re: [Bug 273566] stray characters contaminate serial console
On Sun, Jan 12, 2025 at 05:02:15AM +0000, bugzilla-nore...@freebsd.org wrote:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273566
--- Comment #15 from Sulev-Madis Silber <bugs-freebsd-org...@ketas.si.pri.ee>
---
you currently have more hw than i do, it's all connected up too. can you test
it out more maybe? debugging kernels, etc. i should have multi arch usb/serial
switched remote lab on my own but i don't somehow eh, despite using fbsd since
Just for fun I installed a GENERIC-KASAN kernel on a Pi4 running -current,
but far as I can tell the problem doesn't exist on aarch64 or I don't know
how to see it. The Pi4 is providing terminal service to a Pi2 running armv7,
which since the KASAN kernel went on the Pi4 hasn't suffered a boot
stoppage. Neither have I seen any console messages on the Pi4 suggesting
something amiss. I'm guessing kasan simply generates warnings, but if so
I've not recognized any. I'll keep watching, it would really help to know
what sort of behavior I'm looking for.
I tried to build a kasan kernel on a pi2 running armv7 but buildworld
stopped with an unrecognized symbol. It's now building world/kernel with
GENERIC as a sanity check, but the kasan man page suggests armv7 is
unsupported.
If in fact armv7 does support kasan then I'll keep trying. Unfortunately
I have only one kasan-supporting host presently but have couple spare
Pi2 v1.1 boxes that can run armv7 if it's relevant.
arm64 and amd64 only today