From nobody Thu Jan 09 17:53:52 2025 X-Original-To: freebsd-arm@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 4YTXTY1dQDz5jj8H for ; Thu, 09 Jan 2025 17:53:53 +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 4YTXTW4fndz4XC1 for ; Thu, 9 Jan 2025 17:53:51 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net; dmarc=none Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.18.1/8.18.1) with ESMTPS id 509Hrqkc050207 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Thu, 9 Jan 2025 09:53:53 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.18.1/8.18.1/Submit) id 509HrqQV050206 for freebsd-arm@freebsd.org; Thu, 9 Jan 2025 09:53:52 -0800 (PST) (envelope-from fbsd) Date: Thu, 9 Jan 2025 09:53:52 -0800 From: bob prohaska To: freebsd-arm@freebsd.org Subject: Re: [Bug 273566] stray characters contaminate serial console Message-ID: References: List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Rspamd-Queue-Id: 4YTXTW4fndz4XC1 X-Spamd-Bar: / X-Spamd-Result: default: False [-0.25 / 15.00]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; MID_RHS_WWW(0.50)[]; WWW_DOT_DOMAIN(0.50)[]; NEURAL_HAM_SHORT(-0.15)[-0.152]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; DMARC_NA(0.00)[zefox.net]; MIME_TRACE(0.00)[0:+]; MISSING_XM_UA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; R_DKIM_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; R_SPF_NA(0.00)[no SPF record] On Thu, Jan 09, 2025 at 12:36:42PM +0000, bugzilla-noreply@freebsd.org wrote: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273566 > > --- Comment #6 from Sulev-Madis Silber --- > i messed with things on purpose to see if they break and they did > > ftdi isolates usb ttl adapter is connected with usb end at 13.4 on amd64 and > serial end at current on armv7 > > login via serial using cu, to the armv7 board, then kill cu > > then, with ssh i execute: > > sh -c 'while :; do : | wall; done' > > on said armv7 device > > let some time pass and run cu on port again > > this is what shell history has: > > 41 14:20 Broadcast Message from root@ask-m-001 ^G^G > 42 14:20 ( /dev/pts/0 ) at 14:19 EET... > ^@BBBBBBBBBBBBBJBBBBBBgBBBB^_BBBBBBBB > BBJBBBBBBFBBBBBBwBBBB^_BBBBBBBBBBJBBBBBBFBBBBBBgB^@ > 43 14:20 h > 14:20,root@ask-m-001:~# > > is this what you experience? In short, yes, the usb end is on armv7, the serial end is arm64 : bob@nemesis:~ % Broadcast Message from bob@nemesis.zefox.com ^G^G Broadcast: Command not found. bob@nemesis:~ % bob@nemesis:~ % bob@nemesis:~ % bob@nemesis:~ % bob@nemesis:~ % bob@nemesis:~ % (/dev/pts/1) at KBBBFBBBBBBBBBBBBBBBBBBBBgëB×BBBBBBBBBBBBBBNBBBBBBfgëB×BBBBBBBBBBBBBBNBBBBB^@ Badly placed ()'s. I did this by dropping the cu connection to arm64 using ~~., using your wall command briefly, killing it with control-c and then picking up the serial connection. Recalling history on the serial (arm64) end I see 999 7:13 su 1000 19:41 exit 1001 9:17 h 1002 9:19 Broadcast Message from bob@nemesis.zefox.com ^G^G 1003 9:21 ( /dev/pts/1 ) at KBBBFBBBBBBBBBBBBBBBBBBBBgëB×BBBBBBBBBBBBBBNBBBBBBfgëB×BBBBBBBBBBBBBBNBBBBB^@ 1004 9:25 h bob@nemesis:~ % It appears that only one instance of "leakage" into the serial-end command history occurs through the duration of the wall transmissiion. Thanks for writing! bob prohaska