From nobody Sat Oct 28 21:38:03 2023 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 4SHtDx12Mpz4y48H for ; Sat, 28 Oct 2023 21:38:09 +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 4SHtDw3LW9z4XWy for ; Sat, 28 Oct 2023 21:38:08 +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.17.1/8.15.2) with ESMTPS id 39SLc4oZ083767 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sat, 28 Oct 2023 14:38:04 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.17.1/8.15.2/Submit) id 39SLc3NT083766; Sat, 28 Oct 2023 14:38:04 -0700 (PDT) (envelope-from fbsd) Date: Sat, 28 Oct 2023 14:38:03 -0700 From: bob prohaska To: Mark Millard Cc: freebsd-arm@freebsd.org Subject: Re: Stable/14 dropping ssh connections to FT232 usb-serial adapter Message-ID: References: <33D1AACD-62FB-444A-868C-B8DE92A7BF50@yahoo.com> 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: <33D1AACD-62FB-444A-868C-B8DE92A7BF50@yahoo.com> 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] X-Rspamd-Queue-Id: 4SHtDw3LW9z4XWy [Apologies for the confusion over lengthy output; I mixed up two different hosts and thought I had vastly more to post than I did] On Sat, Oct 28, 2023 at 10:31:53AM -0700, Mark Millard wrote: > On Oct 26, 2023, at 07:42, bob prohaska wrote: > > > ucom_inwakeup: tp=0xd6c38800 > > ucom_inwakeup: tp=0xd6c38800 > > ucom_close: tp=0xd6c38800 > > ucom_shutdown: > > ucom_dtr: onoff = 0 > > ucom_line_state: on=0x00, off=0x01 > > ucom_rts: onoff = 1 > > ucom_line_state: on=0x02, off=0x00 > > ucom_cfg_close: > > To me this just looks like the process using ucom for this > just quit using it for this, closing the use down in a normal > manor. The question likely becomes what is going on in that > more overall context. It would be good to figure out what > sequence initiated what lead to ucom_close, not that I've a > clue for a good way to get that information. > The next two candidates seem to be ssh (used to link hosts) and tip (used to link the shell spawned by loging to the USB end of the usb-serial adapter). Ssh was in the past invoked with -v to obtain debugging information but no explicit errors turned up. Is there any error reporting for tip? I don't see anything about debug features in the man page. For quite some time there were (I thought) complaints about fragmented packets causing network connections to break. Did that get fixed and migrated to armv7? -current used to have problems with dropped ssh connections which seem to have been fixed. > I've not seen anything that I'd guess to be an error visible > via the USB messages. (But I'm no expert.) > Thanks for replying! bob prohaska