>Number:         21447
>Category:       port-sparc64
>Synopsis:       tty port ttya with sabtty driver gets unusable after ^S current-20030503-221512
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    port-sparc64-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun May 04 13:48:01 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Frank Kardel
>Release:        NetBSD 1.6R current-20030503-221512
>Organization:
	
>Environment:
	
	
System: NetBSD mephisto 1.6R NetBSD 1.6R (MEPHISTO_ISDN) #1: Sun May 4 15:00:04 MEST 2003 kardel@pip:/fs/IC35L060-0-a/src/NetBSD/netbsd/sys/arch/sparc64/compile/obj.sparc64/MEPHISTO_ISDN sparc64
Architecture: sparc64
Machine: sparc64
>Description:
	When entering ^S on a sabtty-port (console) the output is stopped as expected but
	^Q doesn't resume output. processes seem unable to get through the exit-code (close).
	Output processes wait at ttout.
UID PID PPID CPU PRI  NI  VSZ   RSS WCHAN    STAT TT    TIME COMMAND
  0 845  202   6   4   0  144   832 ttyout   S+   a  0:00.01 ls 

ls could be killed but the csh hangs in exit even after a kill -1 kill -9.
UID PID PPID CPU PRI  NI  VSZ   RSS WCHAN    STAT TT    TIME COMMAND
  0 202    1   0   4   0  256  1048 ttyout   SEs+ a  0:00.11 (csh)

	Strangely enough syslog output gets through.

>How-To-Repeat:
	Log in con console of an sabtty machine. repeat 1000 ls -la
	hit ^S
	try to recover.
>Fix:
	sometimes it helps going into the ddb and back.
>Release-Note:
>Audit-Trail:
>Unformatted: