From nobody Mon Jan 13 00:25:13 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YWY1Z0Qg3z5k7DY for ; Mon, 13 Jan 2025 00:25:06 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "pelorus.zefox.org", Issuer "pelorus.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YWY1Y0WF3z3yfy; Mon, 13 Jan 2025 00:25:04 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Authentication-Results: mx1.freebsd.org; none Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.18.1/8.18.1) with ESMTPS id 50D0PEPl066440 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sun, 12 Jan 2025 16:25:14 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.18.1/8.18.1/Submit) id 50D0PEae066439; Sun, 12 Jan 2025 16:25:14 -0800 (PST) (envelope-from fbsd) Date: Sun, 12 Jan 2025 16:25:13 -0800 From: bob prohaska To: Kyle Evans Cc: freebsd-current@freebsd.org Subject: Re: [Bug 273566] stray characters contaminate serial console Message-ID: References: <5e6620f9-ac6c-4a2d-8b9e-2cc1cafc17a4@FreeBSD.org> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5e6620f9-ac6c-4a2d-8b9e-2cc1cafc17a4@FreeBSD.org> X-Rspamd-Queue-Id: 4YWY1Y0WF3z3yfy X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US] On Sun, Jan 12, 2025 at 02:04:24PM -0600, Kyle Evans wrote: > On 1/12/25 11:25, bob prohaska wrote: > > > > 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 OK, so armv7 can't help. If arm64 GENERIC-KASAN does find something amiss will it show up on the serial console or /var/log/messages? Thanks for writing! bob prohaska