From owner-freebsd-arm@freebsd.org Mon Feb 26 18:54:37 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 0C9E4F3AA47 for ; Mon, 26 Feb 2018 18:54:37 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5FAB683441; Mon, 26 Feb 2018 18:54:36 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w1QIsYf3021511 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 26 Feb 2018 10:54:35 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w1QIsYfF021510; Mon, 26 Feb 2018 10:54:34 -0800 (PST) (envelope-from fbsd) Date: Mon, 26 Feb 2018 10:54:34 -0800 From: bob prohaska To: Ian Lepore Cc: freebsd-arm@freebsd.org, bob prohaska Subject: Re: Strange behavior from cu on armv7 Message-ID: <20180226185434.GC21104@www.zefox.net> References: <20180226170320.GA21104@www.zefox.net> <1519669881.91697.295.camel@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1519669881.91697.295.camel@freebsd.org> User-Agent: Mutt/1.5.24 (2015-08-30) 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:54:37 -0000 On Mon, Feb 26, 2018 at 11:31:21AM -0700, Ian Lepore wrote: > 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". > Well, at least I'm in good company.....8-) Thanks for writing, bob prohaska