From owner-freebsd-arm@freebsd.org Mon Feb 26 18:31:33 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6D2E0F3905D for ; Mon, 26 Feb 2018 18:31:33 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F2CC88216B for ; Mon, 26 Feb 2018 18:31:32 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 401baffb-1b23-11e8-91c6-33ffc249f3e8 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id 401baffb-1b23-11e8-91c6-33ffc249f3e8; Mon, 26 Feb 2018 18:31:26 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w1QIVLnP075625; Mon, 26 Feb 2018 11:31:21 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1519669881.91697.295.camel@freebsd.org> Subject: Re: Strange behavior from cu on armv7 From: Ian Lepore To: bob prohaska , freebsd-arm@freebsd.org Date: Mon, 26 Feb 2018 11:31:21 -0700 In-Reply-To: <20180226170320.GA21104@www.zefox.net> References: <20180226170320.GA21104@www.zefox.net> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Feb 2018 18:31:33 -0000 On Mon, 2018-02-26 at 09:03 -0800, bob prohaska wrote: > Lately cu sessions (or something closely-related) have taken to > misbehaving on a Pi2 running -current. > > The situation is: > > ssh into armv7 host which has a pl2303 plugged into it > su to root > run cu -l cuaU0 -s 115200 to connect to the serial port of a Pi3  > > Most of the time the connection behaves normally. The pl2303 is prone > to locking up over time, seemingly faster (an hour) when the armv7 host > is loaded. In that case, unplugging and replugging the pl2303 aborts > the cu connection, which can then be restarted and again behaves normally. > > Lately, the unplug-replug cycle produces the normal recognition and  > allows the cu session to be restarted, but no data is tranferred. > A "connected" prompt comes back, but there's no echo and no data.  > Further unplug-replug attempts don't change anything. A reboot of > the armv7 host restores normal behavior.  > > In a couple of cases unprintable characters displayed: > > root@www:/home/bob # cu -l cuaU0 -s 11520oo}root@www:/home/bob # cu -l cuaU0 -s 115200 > Connected > [hex characters didn't copy/paste] > > FreeBSD/arm64 (www.zefox.org) (ttyu0) > > login: � > > FreeBSD/arm64 (www.zefox.org) (ttyu0) > > login:  > > And all is well, for now. > > Thanks for reading, and any ideas. > > bob prohaska Hmm.  I've noticed for the past week or two (maybe longer) that if I connect to a wandboard serial console via an ftdi usb-serial and cu, and then I do "stty size 24 140" I get exactly the symptom you describe... no response to ^C or ^T, and neither un/replugging the ftdi nor closing and reopening the cu connection makes data flow in either direction until the arm board is rebooted.  Ssh connections to the board continue to work fine and the system appears to be running fine, it's only the serial console that's dead.  Killing the getty on the console doesn't help either, a new non-responsive getty starts up immediately. So, I guess all in all I have nothing much to offer here except a too- wordy "me too". -- Ian