PROBLEM:  (QAR 50783)		 (Patch ID: OSF415-410048)
********
Under some circumstances type ahead characters are not processed if a new line 
is not entered.  This is prevalently seen on screen tools which switch from 
canonical mode (line process mode) to raw mode.

PROBLEM: (HPAQ41AAX STLQ23067 UVO105389 HPAQ116QT HPAQ50RP5 HPAQ400K4 ZPOBA0391
********  ZPOB60233) (Patch ID: OSF415-410090)
This is a mandatory patch for all systems.

This patch fixes a wide variety of system panics and other problems caused by
random memory corruption.  The problem has typically shown up at universities,
or Internet service providers hosting a lot of streams activity.

The following symptoms have appeared in a variety of places throughout the
kernel.  Corrupted memory buckets are usually the 256-byte size, although 
they could be any other size.

o Lock timeouts
o Kernel memory faults
o Unaligned kernel accesses

A typical stack trace is shown in the following example:

   3 panic("pmap_activate lock timeout")
   4 pmap_activate() [/src/kernel/arch/alpha/pmap.c":2710]
   5 thread_run() [src/kernel/kern/sched_prim.c":2295]
   6 idle_thread() [src/kernel/kern/sched_prim.c":3105]

In the stack trace above, the lock timed out because the lock structure
(at 0xfffffc0067fefe00) appeared to be locked when it really was not.
This was due to corruption of the structure by user data that had overflowed
from an mblk structure preceding this memory block.

To identify whether you have this memory corruption problem you have to
look beyond the stack trace.  The stack traces will vary considerably,
even on the same system, so the only way to identify this problem is to
find the corrupted memory bucket and look at the contents.

This is a typical 512-byte corrupted memory bucket.  The first 17 bytes of
data have been overwritten by data that belongs to another thread.  The
17 bytes have overflowed from an mblk structure preceding this memory bucket,
and have corrupted this memory bucket, overwriting pointers or locks or
whatever the first 3 quadwords used to contain.

(kdbx) 0xfffffc0067fefe00/32X
fffffc0067fefe00:  6918a5e6f04e78d3 cf7814aca7a32d6f
fffffc0067fefe10:  0000000000000043 0000000000000000
fffffc0067fefe20:  0000000000000000 fffffffffffffff8
fffffc0067fefe30:  0000000000000000 0000000000000001
fffffc0067fefe40:  000000000044a5cc 000000000000001a

        ...

If you display the block of memory immediately preceding the corrupted memory,
you may see an mblk structure there, if it is still around by the time the
crash dump takes place.

Sometimes the data that has corrupted the memory bucket is readable ASCII,
but more often it is unreadable binary data.

The number of bytes of data can be anywhere from 1 byte to several quadwords
of data.

PROBLEM:  (CLD MGO103100)	 (Patch ID: OSF415-410136)
********
This patch fixes a problem when printing to slow printers using Digital UNIX
LAT through a terminal server.  The end of a large file fails to print and
no error is reported.

PROBLEM:  (QAR 59061) (Patch ID: OSF415-410151)
********
The ASDU netbeui server (nbelink) will not close a connection.  It will hang
in dlcb_close awaiting a STREAMS event.  Subsequently, new connecitons will not
be able to connect to nbelink.

This fix corrects a problem introduced by the STREAMS fix to CLD MCGM80LHH/QAR
55462.