From nobody Fri Jan 05 16:15:40 2024 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 4T67qC2JsFz55DmC for ; Fri, 5 Jan 2024 16:15:51 +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 "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T67q94Zxnz4x12 for ; Fri, 5 Jan 2024 16:15:49 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=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 Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.17.1/8.15.2) with ESMTPS id 405GFf60080127 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 5 Jan 2024 08:15:42 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.17.1/8.15.2/Submit) id 405GFeGW080126; Fri, 5 Jan 2024 08:15:40 -0800 (PST) (envelope-from fbsd) Date: Fri, 5 Jan 2024 08:15:40 -0800 From: bob prohaska To: Marcin Cieslak Cc: Mark Millard , John F Carr , ticso@cicely.de, freebsd-arm@freebsd.org Subject: Re: USB-serial adapter suggestions needed Message-ID: References: <9o7q7p36-o7pn-27o9-62no-8p1r6o127123@fncre.vasb> 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=us-ascii Content-Disposition: inline In-Reply-To: X-Spamd-Bar: - X-Spamd-Result: default: False [-1.02 / 15.00]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.92)[-0.918]; WWW_DOT_DOMAIN(0.50)[]; MID_RHS_WWW(0.50)[]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; TO_DN_SOME(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; RCVD_TLS_LAST(0.00)[]; MISSING_XM_UA(0.00)[]; R_SPF_NA(0.00)[no SPF record]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; R_DKIM_NA(0.00)[]; FROM_HAS_DN(0.00)[]; FREEMAIL_CC(0.00)[yahoo.com,mit.edu,cicely.de,freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; DMARC_NA(0.00)[zefox.net]; RCPT_COUNT_FIVE(0.00)[5] X-Rspamd-Queue-Id: 4T67q94Zxnz4x12 On Sun, Dec 31, 2023 at 09:41:06AM +0000, Marcin Cieslak wrote: > On Sat, 30 Dec 2023, bob prohaska wrote: > > > On Sat, Dec 30, 2023 at 07:05:32PM +0000, Marcin Cieslak wrote: > > > are you running with the default /etc/ttys ? > > > > > Yes, I am. > > > > > If yes, > > > > > > can you please edit /etc/ttys on the serial port > > > side as follows (as root) > > > > > > # ed /etc/ttys 2216 > > > /ttyu0 > > > ttyu0 "/usr/libexec/getty 3wire" vt100 onifconsole secure > > > .s/3wire/3wire.9600/ > > > . > > > ttyu0 "/usr/libexec/getty 3wire.9600" vt100 onifconsole secure > > > w > > > q > > > > Couple of questions: > > > > Is it necessary to use ed? I'm less bad with vi 8-) > > > > Should I plan to change tip settings once FreeBSD boots? > > /ttyu0 > .s/3wire/3wire.9600/ > . > w > q > > are the commands you need to enter. > > Please also adjust tip(1) line speed to 9600. It's been discovered that turning off powerd on both the terminal server host and the console host seems to eliminate the disconnect problem entirely. The necessity of eliminating powerd on the terminal server is uncertain, I did it in the spirit of thoroughness. With powerd off, the host www.zefox.org ran a complete buildworld, buildkernel, installworld, installkernel and poudriere jail update over about five days without a single loss of communication from workstation to serial console via the terminal server pelorus and usb-serial adapter. The serial connection was initiated at 115200 baud and remained clean the entire time. On www.zefox.org /etc/ttys still contains ttyu0 "/usr/libexec/getty 3wire" vt100 onifconsole secure ttyu1 "/usr/libexec/getty 3wire" vt100 onifconsole secure ttyu2 "/usr/libexec/getty 3wire" vt100 onifconsole secure ttyu3 "/usr/libexec/getty 3wire" vt100 onifconsole secure Config.txt contains dtoverlay=disable-bt and uname -a now reports FreeBSD www.zefox.org 15.0-CURRENT FreeBSD 15.0-CURRENT #104 main-n267335-499e84e16f56: Thu Jan 4 16:42:10 PST 2024 bob@www.zefox.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64 On the terminal server pelorus /etc/remote contains ucom:dv=/dev/cuaU0:br#115200:pa=none: and the command tip ucom was used to initiate the connection. Uname -a reports FreeBSD pelorus 14.0-RELEASE-p4 FreeBSD 14.0-RELEASE-p4 #0 releng/14.0-n265400-4edf3b80733e: Wed Dec 27 20:21:26 PST 2023 bob@pelorus:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64 To all appearances, the troublemaker is powerd. The question is what to try next. A very simple experiment is to start powerd on www.zefox.org and repeat the build/install cycle. Alternatively, I could try the experiment you suggested, setting ttyu0 to 9600 baud. Or, I could do both at the same time. Or, something else. Please let me know what would be most informative. It would be very desirable to use powerd, as it substantially improves performance. Thanks for your help! bob prohaska