NetBSD Problem Report #675

From gnats  Mon Jan  2 00:35:46 1995
Received: from pain.lcs.mit.edu (pain.lcs.mit.edu [128.52.46.239]) by sun-lamp.cs.berkeley.edu (8.6.9/8.6.9) with ESMTP id AAA07523 for <gnats-bugs@sun-lamp.cs.berkeley.edu>; Mon, 2 Jan 1995 00:35:46 -0800
Message-Id: <199501020553.QAA10205@zen.void.oz.au>
Date: Mon, 2 Jan 1995 16:53:28 +1100
From: "Simon J. Gerraty" <sjg@zen.void.oz.au>
Reply-To: sjg@zen.void.oz.au
To: gnats-bugs@netbsd.org
Subject: cannot kill process stuct in ttyout
X-Send-Pr-Version: 3.2

>Number:         675
>Category:       port-i386
>Synopsis:       unable to kill process waiting for ttyout (com.c)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    gnats-admin
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Jan 02 00:50:04 +0000 1995
>Closed-Date:    Tue Jan 16 06:54:59 +0000 1996
>Last-Modified:  Tue Jan 16 06:56:44 +0000 1996
>Originator:     Simon J. Gerraty
>Release:        1.0
>Organization:
Zen Programming...
>Environment:

System: NetBSD zen.void.oz.au 1.0 NetBSD 1.0 (ZEN) #6: Tue Dec 13 09:55:20 EST 1994 root@zen.void.oz.au:/usr/src/sys/arch/i386/compile/ZEN i386


>Description:

I've been having a lot of trouble getting term-2.2.5 working reliably.
All works well for a while - then term just sleeps forever on select().

During one such experiment I noticed that I could not even echo
anything to the tty device (trying to wakeup term).  I killed term and
woke up the kermit process, it could not talk to the modem either -
just stopped in ttyout.

I managed to kill the kermit (attempts to hangup eventually timed out
I guess).  The getty process (mgetty actually) that came along next,
could not talk to the modem either (all LEDS indicate modem is happy
etc, and cables are not lose etc etc).  Despite kill -9 many times,
mgetty is still stuck waiting on ttyout.  I'll have to re-boot to
allow this pr out...

ps -axl shows:
    0  9966     1   0   4  0   176  176 ttyout IE   ??    0:00.07 /local/bin/mg

so process is trying to exit.  Catting the device, cycling power on
the modem etc all have no effect.  Its jamed tight.

fstat /dev/tty01 shows
USER     CMD          PID   FD MOUNT      INUM MODE         SZ|DV R/W NAME
root     mgetty      9966    0 /          1664 crw-rw----   tty01 rw  /dev/tty01
root     mgetty      9966    1 /          1664 crw-rw----   tty01 rw  /dev/tty01
root     mgetty      9966    2 /          1664 crw-rw----   tty01 rw  /dev/tty01

I could not detect any major differences b/w the 1.0 com.c and the
Dec18 version (in case updating might help).

I've been running 1.0 since its release, and not had any tty related
problems before.  No hardware or system software has been altered
since 1.0 release. UUCP and kermit use tty01 all the time (hours each
day) with no problem.  mgetty has worked flawlessly since installed
more than 6 months ago.

I've got ddb in the kernel, but would need some hits as to what to
look for, before I could chase this down - sorry.

>How-To-Repeat:
	Its pretty random - this is the 1st time this has happened.
>Fix:

>Release-Note:
>Audit-Trail:

From: "Simon J. Gerraty" <sjg@zen.void.oz.au>
To: gnats-bugs@netbsd.org, gnats-admin@netbsd.org
Subject: Re: port-i386/675: cannot kill process stuct in ttyout 
Date: Sat, 28 Jan 1995 17:57:37 +1100


 Ok its happened again... before I reboot, I'll try and record some
 usefull info:

 uname -a   
 NetBSD zen.void.oz.au 1.0 NetBSD 1.0 (ZEN) #6: Tue Dec 13 09:55:20 EST 1994     root@zen.void.oz.au:/usr/src/sys/arch/i386/compile/ZEN i386

 The system is 1.0 plus patches 1-6

 Last boot:

 Jan 14 21:19:43 zen /netbsd: NetBSD 1.0 (ZEN) #6: Tue Dec 13 09:55:20 EST 1994
 Jan 14 21:19:43 zen /netbsd:     root@zen.void.oz.au:/usr/src/sys/arch/i386/comp
 ile/ZEN
 Jan 14 21:19:43 zen /netbsd: CPU: i486DX (486-class CPU)
 Jan 14 21:19:43 zen /netbsd: real mem  = 16384000
 Jan 14 21:19:43 zen /netbsd: avail mem = 14155776
 Jan 14 21:19:43 zen /netbsd: using 225 buffers containing 921600 bytes of memory
 Jan 14 21:19:43 zen /netbsd: pc0 at isa0 port 0x60-0x6f irq 1: color
 Jan 14 21:19:43 zen /netbsd: com0 at isa0 port 0x3f8-0x3ff irq 4: ns82450 or ns1
 6450, no fifo
 Jan 14 21:19:44 zen /netbsd: com1 at isa0 port 0x2f8-0x2ff irq 3: ns82450 or ns1
 6450, no fifo
 Jan 14 21:19:44 zen /netbsd: com2 at isa0 port 0x2e8-0x2ef irq 9: ns82450 or ns1
 6450, no fifo
 Jan 14 21:19:44 zen /netbsd: lpt0 at isa0 port 0x378-0x37f irq 7
 Jan 14 21:19:44 zen /netbsd: lpt1 at isa0 port 0x278-0x27f: polled
 Jan 14 21:19:44 zen /netbsd: wdc0 at isa0 port 0x1f0-0x1f7 irq 14
 Jan 14 21:19:44 zen /netbsd: wd0 at wdc0 drive 0: 124MB 1001 cyl, 15 head, 17 se
 c <ST3144AT>
 Jan 14 21:19:44 zen /netbsd: fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
 Jan 14 21:19:44 zen /netbsd: fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
 Jan 14 21:19:44 zen /netbsd: fd1 at fdc0 drive 1: 1.2MB 80 cyl, 2 head, 15 sec
 Jan 14 21:19:44 zen /netbsd: aha0 at isa0 port 0x330-0x333 irq 11 drq 5
 Jan 14 21:19:44 zen /netbsd: scsibus0 at aha0
 Jan 14 21:19:44 zen /netbsd: aha0 targ 0 lun 0: <MAXTOR  LXT-535S        8.75> S
 CSI1 direct fixed
 Jan 14 21:19:44 zen /netbsd: sd0 at scsibus0: 510MB, 1546 cyl, 11 head, 61 sec, 
 512 bytes/sec
 Jan 14 21:19:44 zen /netbsd: aha0 targ 1 lun 0: <IBM OEM 0662S12         2 21> S
 CSI2 direct fixed
 Jan 14 21:19:44 zen /netbsd: sd1 at scsibus0: 1003MB, 4119 cyl, 5 head, 99 sec, 
 512 bytes/sec
 Jan 14 21:19:44 zen /netbsd: aha0 targ 2 lun 0: <MAXTOR  XT-4380S        B5A > S
 CSI1 direct fixed
 Jan 14 21:19:44 zen /netbsd: sd2 at scsibus0: 318MB, 1224 cyl, 15 head, 35 sec, 
 512 bytes/sec
 Jan 14 21:19:44 zen /netbsd: aha0 targ 5 lun 0: <ARCHIVE VIPER 150  21247-013> S
 CSI1 sequential removable
 Jan 14 21:19:45 zen /netbsd: st0 at scsibus0: rogue, drive empty
 Jan 14 21:19:45 zen /netbsd: ed0 at isa0 port 0x280-0x29f iomem 0xd0000-0xd1fff irq 5: address 00:00:c0:ba:a4:10, type WD8003E (8-bit)
 Jan 14 21:19:45 zen /netbsd: npx0 at isa0 port 0xf0-0xff: using exception 16
 Jan 14 21:19:45 zen /netbsd: biomask 4840 netmask 23a ttymask 21a
 Jan 14 21:19:44 zen savecore: no core dump
 Jan 14 21:20:10 zen lpd[117]: restarted
 Jan 14 21:20:15 zen init: kernel security level changed from 0 to 1

 ps -axl
   100   863   849   0   4  0   616  608 ttyout IE+  p6    0:00.34 kermit -l /de

 Again the problem started with a term (2.2.5) getting into trouble and
 being killed.   I noticed that term was not transmitting, even though
 the Receive Data light on the modem was blinking maddly.

 The term process died in response to a SIGTERM, but the kermit process
 when brought to the forground and given a C-\h (hangup) command
 hung...  kill -9 had no effect after that.

 I have DDB in the kernel, but don't know whether/how I could manually
 clean up this mess. 

 Any clues as to what I should do next time this happens?

 --sjg
State-Changed-From-To: open->closed 
State-Changed-By: mycroft 
State-Changed-When: Tue Jan 16 01:54:59 EST 1996 
State-Changed-Why:  
There is a problem on some UART clones with transmit interrupts being lost, but 
this has been worked around for some time by ignoring the interrupt status bits. 
>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.