#: 14760 S12/OS9/68000 (OSK)
    02-Apr-92  21:19:31
Sb: #more serial wierdness
Fm: Steve Wegert 76703,4255
To: Carl Kreider 71076,76 (X)

Carl (and Kev),

I recently completed adding the remaining serial ports to my MM/1. I now
have all five ports available. On the surface .... they all work. /t2,/t3
and /t4 have always functioned, so I tested /t0 and /t1 by swapping a
terminal to each port, firing up a shell and issuing a few commands.

But, when I try something a bit more intense I find I have more serial
weridness. For instance, with a terminal on /t0 and a shell active, I fire
up my com program with the following command: sterm -l /t3

As soon as I get any activity from sterm, the port is locked up. (other
port still function). Attempting to kill the process on /t0 will lock
up the entire machine. The same thing will happen if I use Kermit.

Mark muttered somthing about interupts, so I grabbed a snapshot with the
IRQS command:

OS9 St. Louis  MM/1  OS-9/68K V2.4      (max devs: 32, max irqs: 32)

 vector prior port addr data addr  irq svc    driver   device
------- ----- --------- --------- ---------  --------- ------
 28 (4)    1  $00e00291 $0017b710 $0000e252  sc68681   t4       
 28 (4)    1  $00e00281 $0016e520 $0000e252  sc68681   t3       
 28 (4)    2  $00e00000 $001ffdc0 $0001b912  scsi_mm1d           
 28 (4)    5  $00e00381 $001f5560 $0000d8d0  sc68901   t2       
 29 (5)    1  $009ffc41 $001f9814 $00014f94  keydrv             
 29 (5)    3  $009ffc00 $00000000 $0000c098  tk68901            
 29 (5)    5  $009ffc01 $001877a0 $0000d8d0  sc68901   t1       
 29 (5)    9  $009ffcc1 $001f2140 $00019c1c  rb37c65   d0       
 29 (5)  255  $009ffc0d $001f2e10 $0000ce7c  sc68070   t0       

Immediately the 255 priority on /t0 strikes me as odd. 

(more in the reply)


There are 2 Replies.