From: Brian Edmonds (edmonds@cs.ubc.ca)
Date: 10/01/92


From: edmonds@cs.ubc.ca (Brian Edmonds)
Subject: BUGS (minor)
Date: 1 Oct 1992 17:20:24 -0700

I have been running version 0.96c since it came out, and have found it
to be very stable. I noticed a few small but consistent bugs in it,
but wanted to wait until I upgraded to see if they vanished. Today I
upgraded to 0.98, and they're still present, so here we go:

1) I have a terminal attached to /dev/ttys3 which I use for most of
my work (I guess I just like an ascii interface :). Approximately
every two hours, my shell gets terminated. Usually I'm running
screen, which apparently receives a SIGHUP, and detaches itself, so
it's not a problem except that I have to log back in and reattach. If
it's just a shell, then I get logged out and jobs running under it
(such as kermit) get immediately terminated. If it is just sitting at
the login prompt, login appears to terminate similarly, so over time
the prompts (and /etc/issue reissued) will scroll up the screen. I
have no reason to suspect that my cable is faulty, as otherwise the
connection works flawlessly.

2) I am running with four serial ports, 3 16450s and one 16550A. The
450s work fine, and generally keep up. I would like to use the 550A,
but it is behaving extremely strangely. I start up kermit and talk to
the modem for a while, then I can dial, and receive the connect
message, but no data received by the modem is passed to the computer.
Data generated by the modem itself (connect msgs for example) arrive
no problem. Could this be a problem with the chip itself, and if so,
is there a test to confirm it? I have no trouble with exactly the
same modem on a 450 port. An interesting and occasional side-effect
on the 550A port is that if I type enough (with no response) while
connected, the console will freeze completely: I can't switch VCs.
I believe the terminal still works, but I haven't rigourously tested
this.

3) This one is X, not kernel: I'm running version 1.1. When I leave
X, it has never restored text mode properly. I'm usually left with a
screen that is badly out out sync horizontally, so it just looks like
snow across the screen where text is. Should I just get a copy of 2.0,
and then report if it still doesn't work? Have other people had this
problem fixed by 2.0?

System configuration:
    486/33 with 8M RAM, 80M IDE, 1.44M floppy.
    Tseng ET4000 SVGA card with Samatron SC-431VS 14" monitor (yawn).
    External US Robotics V.32bis/V.42bis modem.
    Ann Arbor Ambassador terminal on ttys3 at 9600 baud.

Kernel configuration:
    Linux 0.98 (very minor CAPS->CTRL and backspace patches by me).
    No SCSI, no TCP, no math emulation.
    Only minix fs, compiled with -m486.

======================================================================
Brian Edmonds (MSc CompSci) edmonds@cs.ubc.ca