Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 13 Aug 2001 21:48:18 -0400
From:      Leo Bicknell <bicknell@ufp.org>
To:        freebsd-hackers@freebsd.org
Subject:   Very odd tty hanging problem.
Message-ID:  <20010813214818.A84958@ussenterprise.ufp.org>

next in thread | raw e-mail | index | archive | help

I have stumbled across a bug that's driving me bonkers.  Here's
the setup:

- Log in to a 4.2-RELEASE box.
- Run mutt (1.2.5i, built from ports)
- Get dropped into an editor (new message, reply, it doesn't matter)
- Enter insert mode in vi
- Paste in > 1k (approximately) of text

Bam, frozen window.  It won't respond to anything.  Here's output
of top for that string of processes:

  PID USERNAME PRI NICE  SIZE    RES STATE  C   TIME   WCPU    CPU COMMAND
75136 bicknell  18   0  1348K   924K pause  1   0:00  0.00%  0.00% tcsh
84462 bicknell  10   0  2736K  1904K wait   0   0:00  0.00%  0.00% mutt
84475 bicknell  10   0   620K   232K wait   1   0:00  0.00%  0.00% sh
84476 bicknell   4   0  1900K  1664K ttywri 0   0:00  0.00%  0.00% vi

(tcsh -> mutt -> sh -c vi -> vi)

Vi always ends up stuck in ttywrite, and yes, I can easily reproduce
this over and over.

From another window, try to kill the processes as a user, no effect
with -9 or regular.  Try to kill them as root, no effect normal.  Kill
them -9 as root, and all but the first shell will go away, here's 
ps output from an earlier occurance:

  PID  TT  STAT      TIME COMMAND
20986  p0- IEs+   0:00.08 -tcsh (tcsh)

And top of the same:

  PID USERNAME PRI NICE  SIZE    RES STATE  C   TIME   WCPU    CPU COMMAND
20986 bicknell   4   0  1344K   908K ttywai 1   0:00  0.00%  0.00% tcsh

If I run vi on its own (or cat -, or emacs, etc) I can't make this
happen.  I can't make it happen with another editor under mutt (eg
emacs).  But let mutt start vi and paste a reasonable size junk
and bam, its frozen.  I've also tried it from different terminal
emulators, over both ssh and telnet, same results.

I'm at a loss as to what might be happening, or what to do next to
debug this particular problem.  Anyone have a suggestion?

-- 
Leo Bicknell - bicknell@ufp.org
Systems Engineer - Internetworking Engineer - CCIE 3440
Read TMBG List - tmbg-list-request@tmbg.org, www.tmbg.org

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010813214818.A84958>