From owner-freebsd-stable@freebsd.org  Wed Jan 25 10:15:17 2017
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 39322CB5D0A
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Wed, 25 Jan 2017 10:15:17 +0000 (UTC) (envelope-from lists@opsec.eu)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (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 F39DE1068
 for <freebsd-stable@freebsd.org>; Wed, 25 Jan 2017 10:15:16 +0000 (UTC)
 (envelope-from lists@opsec.eu)
Received: from pi by home.opsec.eu with local (Exim 4.87 (FreeBSD))
 (envelope-from <lists@opsec.eu>)
 id 1cWKbl-0007iC-2n; Wed, 25 Jan 2017 11:15:17 +0100
Date: Wed, 25 Jan 2017 11:15:17 +0100
From: Kurt Jaeger <lists@opsec.eu>
To: "Eugene M. Zheganin" <emz@norma.perm.ru>
Cc: freebsd-stable@freebsd.org
Subject: Re: reset not working like 70% of the time
Message-ID: <20170125101517.GW13006@home.opsec.eu>
References: <5888754F.2040901@norma.perm.ru>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5888754F.2040901@norma.perm.ru>
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jan 2017 10:15:17 -0000

Hi!

> does anyone suffer from this too ? Right now (and for several last
> years) a 100% decent way to reset a terminal session (for instance,
> after a connection reset, after acidentally displaying a binary file
> with symbols that are treated as terminal control sequence, after
> breaking a cu session, etc) is to launch midnight commander and then
> quit from it. And the reset is working like in 30% of cases only.
[...]
> Am I the only person seeing this ?

I had some cases in the past where xterm was hanging, too -- but
not with *that* high rate of problems.

Most of the times, xterm's Full Reset options works fine.

The question is: how to debug that... ?

-- 
pi@opsec.eu            +49 171 3101372                         3 years to go !