PROBLEM:	(HPXQ43C4D, TKTR52185, QAR 46016)    (Patch ID: OSF410-039)
********
This patch fixes some hangs that may occur after the message "syncing disks..." 
is printed when the system panics.  When these hangs occur, the completion of 
the "syncing disks..." message - the word "failed" or "done" does not get 
printed, and the system does not take a dump.

In addition to fixing these known hangs, a timout mechanism is added to the
"syncing disks" logic that will improve the reliability of getting a dump by
using the system clock to break out of the "syncing disks" path and take
a dump if no progress is being made on reducing the number of buffers to be
flushed.  The numbers printed periodically between the "syncing disks..."
and "done" messages are the number of buffers left to flush.

This patch also makes it more likely that AdvFS buffers will be flushed to
disk during the "syncing disks..." processing after a system panic.  There
is still no guarantee that writes in progress at the time of a panic will be
completed.

PROBLEM:	(QAR 49523)	(Patch ID: OSF410-034)
********
The vmstat(1) command may display negative numbers when run with the '-P' 
option.  To reproduce the problem type:   vmstat -P

NOTE: The problem may not exist on all platforms / configurations because 
      it is dependent on how the kernel build various internal data structures.

PROBLEM:	(QAR 49556)	(Patch ID: OSF410-405037)
********
A "kernel memory fault" panic will be seen originating from the malloc() 
routine.  The top stack entries will be as follows.  Many different kernel
routines may appear in the stack below malloc().

        panic("kernel memory fault")
        trap()
        _XentMM()
        malloc()

This problem is due to malloc() bucket corruption that occurs when there are 
racing fdetach()/ file-on-file unmounts.  File-on-file mounting is most often 
used with the fattach() library call and System V Environment pipes.

PROBLEM:	(QAR 49556)	(Patch ID: OSF410-405037)
********
Racing fdetach() or file-on-file unmounts can also cause threads to hang in
the kernel with the following stack trace.

        0 thread_block()
        1 vfs_busy()
        2 dounmount()
        3 unmount()
        4 syscall()
        5 _Xsyscall()

PROBLEM:    (CLDs HPAQ92E5E,TKTR90455/QAR 49011)  (Patch ID: OSF410-400100)
********
This patch prevents a "kernel memory fault" in the bread() routine while 
performing sync operations.  

The stack trace will look similar to the following:

0 boot()      ["../../../../src/kernel/arch/alpha/machdep.c"]
1 panic("kernel memory fault") ["../../../../src/kernel/bsd/subr_prf.c"]
2 trap()      ["../../../../src/kernel/arch/alpha/trap.c"]
3 _XentMM()   ["../../../../src/kernel/arch/alpha/locore.s"]
4 bread()     ["../../../../src/kernel/vfs/vfs_bio.c"]
5 iupdat()    ["../../../../src/kernel/ufs/ufs_inode.c"]
6 ufs_sync()  ["../../../../src/kernel/ufs/ufs_vfsops.c";
7 sync()      ["../../../../src/kernel/vfs/vfs_syscalls.c"]
8 syscall()   ["../../../../src/kernel/arch/alpha/syscall_trap.c"]
9 _Xsyscall() ["../../../../src/kernel/arch/alpha/locore.s"]

PROBLEM:        (QAR 47666)     (Patch ID: OSF410-405036)
********
Sometimes the system cannot contact a device when it should be able to.
The problem is that if a device got a selection timeout, the EDT structure
is released.  The next time the system tries to access that device,
it fails if the device does not respond within the timeout period.

PROBLEM:        (HPXQB6189/QAR 49949)   (Patch ID: OSF410-400141)
********
This patch fixes a network socket problem with select() missing state changes 
on clients from non-write to writable.

PROBLEM:        (MCPM94D74, QAR 49067)  (Patch ID: OSF410-400165)
********
Fixes system crash when setting the date for SMP systems.

A representative stack trace follows:

panic("resettodr: cpu not master") 
["../../../../src/kernel/bsd/subr_prf.c":753,]
resettodr() ["../../../../src/kernel/arch/alpha/clock.c":322,]
setthetime() ["../../../../src/kernel/bsd/kern_time.c":543,]
settimeofday() ["../../../../src/kernel/bsd/kern_time.c":499,]

PROBLEM:  	(QAR 51688, CLD USG-04543)  (Patch ID: OSF410-052)
********
The ObjectStore application from Object Design, Inc. fails with the following
error:

 	"Fatal error Invalid argument(errno = 22) munmap failed: cl_mmap:"

PROBLEM:  	(USG-04536,51700) (Patch ID: OSF410-059)
********
Idle processes display poor interactive responsiveness. this patch prevents
idle processes from being outswapped too soon.

PROBLEM:   (QAR 36779)	 (Patch ID: OSF410-405054)
********
This patch fixes a problem that occurs when running the NetWorker Version 4.2c
application.  The NetWorker application is unable to reset the atime (access
time) attribute on files being accessed. No errors or warnings are displayed.

Without this patch, NetWorker Version 4.2c will not perform well.

PROBLEM:   (HPXQB6BA4)	       (Patch ID: OSF410-062)
********
This patch fixes a problem in which the user or system setting of UAC_NOPRINT
is ignored when an unaligned access trap is taken on a user address while
in kernel mode.  When this is a common event due to a customer application,
the console and "messages" file can be flooded with error messages of the
sort show below:

Oct 19 03:20:18 dekalb vmunix: Unaligned kernel access va=0x140018554 pc=0xfffff
c00004f5f24 ra=0xfffffc000025bc80 inst=0xffffffff
 
PROBLEM:    (QAR 49818)         (Patch ID: OSF410-400127)
********
System panics with messgae: "vm_map_swapout: negative resident count".

The crash will most likely occur on a multi-processor system during
a heavy paging load.


  panic("vm_map_swapout: negative resident count")

   vm_map_swapout()
   task_swapout()
   task_swapout_thread()

PROBLEM:  (CLD MCPMB7DEJ, QAR 50938)     (Patch ID: OSF410-400197)
********
This patch resolves a kernel memory fault.

A representative stack trace follows:

panic("kernel memory fault") ["../../../../src/kernel/bsd/subr_prf.c":753, ]
trap() ["../../../../src/kernel/arch/alpha/trap.c":1457, ]
_XentMM() ["../../../../src/kernel/arch/alpha/locore.s":1392, ]
simple_lock_D() ["../../../../src/kernel/arch/alpha/lockprim.s":730, ]
u_anon_dupmcopy() ["../../../../src/kernel/vm/u_mape_anon.c":1603, ]
u_anon_dupmcopy() ["../../../../src/kernel/vm/u_mape_anon.c":1603, ]
u_anon_dup() ["../../../../src/kernel/vm/u_mape_anon.c":1321, ]
u_map_copyin() ["../../../../src/kernel/vm/vm_umap.c":2085, ]
vm_map_copyin() ["../../../../src/kernel/vm/vm_map.c":1691, ]
procfs_psinfo() ["../../../../src/kernel/procfs/procfs_subrs.c":2425, ]
procfs_ioctl() ["../../../../src/kernel/procfs/procfs_ioctl.c":301, ]
vn_ioctl() ["../../../../src/kernel/vfs/vfs_vnops.c":1165, ]
procfs_ioctl_interface() ["../../../../src/kernel/procfs/procfs_ioctl.c":1716, ]
ioctl_base() ["../../../../src/kernel/bsd/sys_generic.c":426, ]
ioctl() ["../../../../src/kernel/bsd/sys_generic.c":374, ]

PROBLEM:     (QAR 51161, QAR 51813)	 (Patch ID: OSF410-063)
********
This patch corrects problems encountered when using signals with multi-thread
programs. Specifcally, three problem may be encountered, all of them usually
resulting in an application hang:

1. Missed thread-specific signals. These are signal sent via the pthread_kill()
   function. Under extremely intensive use, a signal sent by pthread_kill()
   can be lost. This will usually manifest itself as an application hang, as 
   expected signal goes unreceived.

2. Inconsistent compute-bound hangs in the libpthreads.so.  Typically, a stack
   trace for such a hang would have the following mutex-related frames at the
   top of its stack:

        0 pthread_mutex_unblock()
        1 __pthread_mutex_unlock()
        2 (unknown)()
        3 free()
        .
        .
        .

   The frames below the mutex frames could be any routine that calls 
   pthead_mutex_unlock().

3. Unexpected error return from system calls. When using process-level signals,
   certain system calls may return unexpectedly with an EINTR error without a
   signal actually having been delivered. Typcial victims of this problem are
   are the sigwait() and read() functions.  Particularly in the case of read(),
   an application is likely to reissue the system call without noticiing the
   error, resulting in a compute-bound loop.

PROBLEM:  (EVT101963, QAR 52024) (Patch ID: OSF410-405062)
********
The kernel panics with a "kernel memory fault".  Typical stack traces will
panic in either vm_zeroed_pg_alloc() or vm_pg_alloc() as shown below:

>  0 boot                 src/kernel/arch/alpha/machdep.c : 2361
   1 panic                src/kernel/bsd/subr_prf.c : 791
   2 trap                 src/kernel/arch/alpha/trap.c : 1457
   3 _XentMM              src/kernel/arch/alpha/locore.s : 1388
   4 vm_zeroed_pg_alloc   src/kernel/vm/vm_resident.c : 1289
   5 vm_anon_page_alloc   src/kernel/vm/vm_anonpage.c : 119
   6 anon_pagezero_alloc  src/kernel/vm/vm_anon.c : 448
   7 u_anon_faultpage     src/kernel/vm/u_mape_anon.c : 968
   8 u_anon_fault         src/kernel/vm/u_mape_anon.c : 861
   9 u_map_fault          src/kernel/vm/vm_umap.c : 501
  10 vm_fault             src/kernel/vm/vm_fault.c : 134
  11 trap                 src/kernel/arch/alpha/trap.c : 1467
  12 _XentMM              src/kernel/arch/alpha/locore.s : 1388

>  0 stop_secondary_cpu   src/kernel/arch/alpha/cpu.c : 414
   1 panic                src/kernel/bsd/subr_prf.c : 703
   2 event_timeout        src/kernel/arch/alpha/cpu.c : 811
   3 xcpu_puts            src/kernel/bsd/subr_prf.c : 844
   4 printf               src/kernel/bsd/subr_prf.c : 379
   5 panic                src/kernel/bsd/subr_prf.c : 753
   6 trap                 src/kernel/arch/alpha/trap.c : 1457
   7 _XentMM              src/kernel/arch/alpha/locore.s : 1388
   8 vm_pg_alloc          src/kernel/vm/vm_resident.c : 1162
   9 ubc_alloc            src/kernel/vfs/vfs_ubc.c : 3278
  10 ubc_page_alloc       src/kernel/vfs/vfs_ubc.c : 2240
  11 ubc_lookup           src/kernel/vfs/vfs_ubc.c : 1779
  12 page_lookup          src/kernel/msfs/bs/bs_buffer2.c : 1041
  13 seq_ahead            src/kernel/msfs/bs/bs_buffer2.c : 5258
  14 seq_ahead_cont       src/kernel/msfs/bs/bs_buffer2.c : 5013
  15 bs_refpg_int         src/kernel/msfs/bs/bs_buffer2.c : 1867
  16 bs_refpg             src/kernel/msfs/bs/bs_buffer2.c : 1596
  17 fs_read              src/kernel/msfs/fs/fs_read_write.c : 1549
  18 msfs_read            src/kernel/msfs/osf/msfs_vnops.c : 1883
  19 vn_read              src/kernel/vfs/vfs_vnops.c : 864
  20 rwuio                src/kernel/bsd/sys_generic.c : 1217
  21 read                 src/kernel/bsd/sys_generic.c : 1167
  22 syscall              src/kernel/arch/alpha/syscall_trap.c : 540
  23 _Xsyscall            src/kernel/arch/alpha/locore.s : 1173

PROBLEM:  (QAR 50693, QAR 49421) (Patch ID: OSF410-400216)
********
This patch corrects a problem with the exec() system function.  A shell script
that has "#! <a setuid program>" as the first line of the script, invokes the
the program but does not set the effective user id for the execution of the
program. For example:

$ cat myprog.c
 #include <unistd.h>
 main()
 {
         printf("geteuid() return  effective user ID of the calling
process=%d\n",geteuid());
 }

 $ cat test.sh
 #!./myprog
 echo "done with myprog"

 As root:
 # chmod 4755 myprog
 # chown root myprog

 As user ww
 $ ./myprog
 geteuid() return  effective user ID of the calling process=0

 $ ./test.sh
 geteuid() return  effective user ID of the calling process=7301
 In this case ./test.sh should return an euid of 0.

PROBLEM:  (CLD EVT101664) 	(Patch ID: OSF410-400232)
********
This patch fixes a performance problem that occurs with UFS file systems.
Data written to a file greater than 32 GB in length will be slower than
data written to the file when it is less than 32 GB in length.

PROBLEM:  (HPAQC07YV)            (Patch ID: OSF410-400208)
********
This patch fixes a problem that occurs when the system panics with the
following error message:

             kernel memory fault

The following is a typical stack trace of the system panic:

 0 boot()                       [../../../../src/kernel/arch/alpha/machdep.c]
 1 panic("kernel memory fault") [../../../../src/kernel/bsd/subr_prf.c]
 2 trap()                       [../../../../src/kernel/arch/alpha/trap.c]
 3 _XentMM()                    [../../../../src/kernel/arch/alpha/locore.s]
 4 _svcauth_unix()              [../../../../src/kernel/rpc/svc_auth_unix.c]
 5 _authenticate()              [../../../../src/kernel/rpc/svc_auth.c]
 6 nfs_rpc_recv()               [../../../../src/kernel/rpc/svc.c]
 7 nfs_rpc_input()              [../../../../src/kernel/rpc/svc.c]
 8 nfs_input()                  [../../../../src/kernel/nfs/nfs_server.c]
 9 nfs_thread()                 [../../../../src/kernel/nfs/nfs_server.c]

PROBLEM:  (QAR 50697, MGO102332, FNO100130) (Patch ID: OSF410-400198)
********
This patch fixes a number of problems relating to signals and POSIX
1003.1b timers in multi-threaded programs running on multi-processor systems.
These problems can result in missed timer-expiration signals and system
crashes. These issues involve synchronizing timer creation, timer
deletion, and timer reset within multi-threaded programs.

Two distinct crashes are typical of the problems.

Here's a sample of the first crash, a signal panic:

        panic (cpu 0): psig: catch not set

With the following stack trace:

        > 0 boot
          1 panic
          2 psig
          3 syscall
          4 _Xsyscall

A sample of the second crash is shown in the following example:

    from vmcore.3 :
    .
    .
    .
    simple_lock: time limit exceeded
    .
    .
    .
        pc of caller:         0xfffffc000024a5a4
        lock address:         0xfffffc003d93b210
        current lock state:   0x000000000043af85
                              (cpu=0,pc=0xfffffc000043af84,busy)
    .
    .
    .
    panic (cpu 2): simple_lock: time limit exceeded

While a stack trace would show:

    kernel stack of CPU 0
    >  0 boot
       1 panic
       2 event_timeout
       3 simple_lock_miss
       4 netisr_timeout
       5 softclock_scan
       6 lwc_schedule
       7 thread_preempt
       8 boot
       9 panic
      10 cpu_ip_intr
      11 _XentInt
      12 swap_ipl_preempt_check
      13 wanTimerSysTick
    .
    .
    .
     kernel stack of CPU 1
    >  0 stop_secondary_cpu   ...
       1 panic                  :
       2 cpu_ip_intr            :  THIS PART OF THE KERNEL STACK
       3 _XentInt               :  IS VERY TYPICAL FOR THIS CLASS
       4 sigq_enqueue_tail      :  OF CRASHES.
       5 psignal_internal       :
       6 psx4_tod_expire_sig  ..:
       7 psignal_lwc
       8 lwc_schedule
       9 do_preemption
      10 simple_unlock_preempt
      11 sigwaitprim
      12 syscall
      13 _Xsyscall
    .
    .
    .
    kernel stack of CPU 2
    >  0 stop_secondary_cpu
       1 panic
       2 event_timeout
       3 xcpu_puts
       4 printf
       5 panic
       6 simple_lock_fault
       7 simple_lock_time_violation
       8 psx4_set_todtimer
       9 syscall
      10 _Xsyscall
    .
    .
    .
    kernel stack of CPU 3
    >  0 stop_secondary_cpu
       1 panic
       2 cpu_ip_intr
       3 _XentInt
       4 swap_ipl_preempt_check
       5 netisr_thread
       6 wanTimerTick
    .
    .
    .

This patch closes MP race conditions for multi-threaded use of POSIX
timers and signals.

PROBLEM:     (MCPMA986D)     (Patch ID: OSF410-405044)
********
This patch is a kernel fix for network sockets left in FIN_WAIT_1 state forever.

This patch contains a "tunable" kernel parameter.  It is recommended that only
experienced system administrators attempt to set this parameter from the
default value.

How to recognize this problem.

This is an example of the problem with tcpdump running in the background
listening on the destination ip address shown in the netstat output.

# netstat -An | grep 203.232.10.221
Active Internet connections
PCB      Proto Recv-Q Send-Q  Local Address      Foreign Address    (state)
94276c00 tcp        0    759  192.86.154.82.80   203.232.10.221.162
FIN_WAIT_1
9418ef00 tcp        0    759  192.86.154.82.80   203.232.10.221.162
FIN_WAIT_1

13:28:03.472384 www-2.us.oracle.com.80 > 203.232.10.221.1626: . 0:1(1) ack 1
win 33232
13:28:12.973072 www-2.us.oracle.com.80 > 203.232.10.221.1623: . 0:1(1) ack 1
win 33232

What is observed here is the destination is clearly dead.  The source is
sending an ACK to the destination looking for his ACK of our FIN.  This is
commonly refered to as "persist mode".  A socket in this state will never
timeout and system resources associated with it will not be released.

The new kernel modification to tcp_timer.o can be "tuned" by dbx'ing the
tcp_keepidle parameter on the system.  By default, this is set to 14400
1/2 seconds (2 hours).  It can be easily set to any value appropriate for
the system to "balance" the number of sockets in FIN_WAIT_1 state at any
time.  The system may always have some sockets in FIN_WAIT_1 as well as
CLOSE_WAIT, this is NORMAL.  What you don't want is a large number of sockets
in FIN_WAIT_1 forever.  It is not recommended that tcp_keepidle be set to
less than 5 minutes on the system.

Reference the man page to dbx for guidelines when using the dbx command.

PROBLEM:  (ZUO101015/QAR 49750)          (Patch ID: OSF410-405053)
********
This patch fixes ICMP REDIRECTS.  When an ICMP REDIRECT is received, the
routing table was updated properly, but the IP layer didn't use the new route
information.

PROBLEM:  (CLD MCPMB04E3)                (Patch ID: OSF410-405059)
********
This patch resolves a TCP/IP network hang due to an IP Q ACK deadlock. When
this condition occurs the IP Q becomes full due to saturation. Representative
console messages indicating this condition are shown below:

        SIS00-00-root: IP q full, 315617 packets dropped in the last 5 mins.

PROBLEM:  (CA7Q10994)        		 (Patch ID: OSF410-049)
********
This patch fixes a problem that occurs on all systems that use networking
services.

The problem can be seen when a system attempts to ping a Digital UNIX Alpha
system connected to a token ring network and the ping uses a message size that
requires fragmentation. The Digital UNIX Alpha system receiving the ping
cannot respond. The token ring driver displays the following error message
to the console and resets the token ring adapter:

                        List Error in transmit

PROBLEM:  (HPXQB4C4B) 			(Patch ID: OSF410-400186)
********
This patch fixes a problem in which the system can panic with "lock already
owned by thread".  A typical stack trace shows:

        boot
        panic
        lock_fault
        lock_write
        solock
        socket_send
        ip_mforward
        ip_output
        rip_output
        raw_usrreq
        rip_usrreq
        sosend
        sendit
        sendto
        syscall

PROBLEM:  (CLD MCPMB04E3)        (Patch ID: OSF410-400233)
********
This patch resolves a TCP/IP network hang due to an IP Q ACK deadlock.
When this condition occurs the IP Q becomes full due to saturation.
Representative console messages indicating this condition are shown below:

   SIS00-00-root: IP q full, 315617 packets dropped in the last 5 mins.

PROBLEM:  (CLD: MCPM3028N)       (Patch ID: OSF410-400250)
********
This patch fixes a problem in which network applications communicating to
one of the host's own addresses, may hang, or receive the error message:

             no buffer space available

The problem occurs due to a queue full condition on the interface.

In an Available Server (ASE) or TruCluster environment, the daemons will no
longer be able to communicate with each other, and the asemgr utility will
appear to hang.

PROBLEM:  (MCPMC07S7)		 (Patch ID: OSF410-400201)
********
This patch fixes a kernel memory fault in ether_output packet filter, when
running tcpdump.

A representative stack trace of the 'tcpdump' process following:

 read_io_port() src/kernel/io/dec/pci/pcia.c : 707
 fta_poll_cmd_req() src/kernel/io/dec/netif/if_fta.c : 3065
 ftaioctl() src/kernel/io/dec/netif/if_fta.c : 1831
 enetSetIfflags() src/kernel/net/pfilt.c : 3311
 decCopyAllCount() src/kernel/net/pfilt.c : 3367
 Pfilt_close() src/kernel/net/pfilt.c : 1376
 speclose() src/kernel/vfs/spec_vnops.c : 2486
 spec_close() src/kernel/vfs/spec_vnops.c : 2616
 ufsspec_close() src/kernel/ufs/ufs_vnops.c : 3632
 vn_close() src/kernel/vfs/vfs_vnops.c : 1280
 closef() src/kernel/bsd/kern_descrip.c : 1539
 close() src/kernel/bsd/kern_descrip.c : 1217

PROBLEM:(CLD HPXQ87202,QAR 49448,QAR 49474,QAR 49475) (Patch ID: OSF410-400242)
********
This patch fixes a problem in which the the lastcomm accounting command 
doesn't print the "S" flag at appropriate times.  This patch also improves
the performance of lastcomm.

The problem was that the kernel did not properly update the accounting field
that prints the "S" flag. The "S" flag should be printed for each command
that is run with an effective user id of 0.  Commands that are set-user-id
to root, will print the "S" flag.  Also, commands that are executed by root,
but are not set-user-id, will print the "S" flag.  Therefore, when "S" is
printed from lastcomm for a certain command, it means that the user had root
privileges at some time during the execution of the command.

The algorithm used by lastcomm has been enhanced to improve its performance.

PROBLEM:  (HGOBB0043, HGOBB0597)  (Patch ID: OSF410-405045)
********
Intermittently, the probe of an isp will fail during a boot.  This happens
maybe once in 20 system boots, so a workaround is to try the boot again.

A typical console listing looks like this when it fails:
        .
        .
        .
  Created FRU table configuration errorlog packet
  tiop0 at tlsb0 node 8
  tiop0: cpu interrupt mask being set as 1.
  pci0 at tiop0 slot 0
  isp0 at pci0 slot 0
  isp0: QLOGIC ISP1020 - Differential Mode
  cam_logger: CAM_ERROR packet
  cam_logger: bus 0
  isp_mailbox complete
  Timeout on mailbox command completion scheduling chip reinit
  cam_logger: CAM_ERROR packet
  cam_logger: bus 0
  isp_init
  Mailbox operations not functional for common init
  cam_logger: CAM_ERROR packet
  cam_logger: bus 0
  isp_probe
  Common init failure - Failing probe
  isp0: Not probed.
  isp in slot 0 not configured.
        .
        .
        .

PROBLEM:  (Patch ID: OSF410-068)
********
This network patch, which greatly improves Digital UNIX networking performance
is targeted at high traffic Web server systems or any system which handles a
large number of TCP connections simultaneously, ie. more than several thousand
at one time.

The summary of improvements include:

Network kernel SMP locking improvements
	Increased throughput due to reduced lock contention throughout
        network stack on multi-processor (SMP) systems

Socket code improvements
        Improved performance in socket listen queue handling
        somaxconn, sominconn listen backlog support was increased
        from 32K to 64K maximum

TCP code improvements
        Fully dynamic TCP hash table, can change size on the fly
        without having to reboot (tcbhashsize) support for TCP
        hash table size larger than 1024 (tcbhashsize) improved
        TCP timer algorithm eliminates a large percentage of the
        processing overhead needed to handle the tcp timer task
        more efficient port allocation code decreases outgoing
        connection overhead (ipport_userreserved) randomized TCP
        initial sequence number IP reassembly fix for >12Gb memory
        systems and other minor TCP/IP bug fixes

Kernel malloc improvements
        Improved kernel malloc pool performance on SMP platforms

Kernel select improvements
        Improved kernel select performance on SMP platforms when many
        open file descriptors are selected simultaneously

Additional kernel network tunable variables (using sysconfig):
        sobacklog_drops
        sobacklog_hiwat
        somaxconn_drops
        ipport_userreserved
        tcp_rexmit_interval_min
        tcp_cwnd_segments
        tcp_keepalive_default

PROBLEM:  (QAR 50363)    (Patch ID: OSF410-400235)
********
This patch fixes a problem with the fsck command. When fsck is run on a
a non-existent file system or on a currently mounted file system, it returns
a success status of zero. It should return a non-zero status.

An example where this problem is exhibited is shown here:

# fsck /dev/rz2a
/sbin/ufs_fsck /dev/rz2a
** /dev/rrz2a
Error: /dev/rrz2a or an overlapping partition is open.
FSCK CANNOT BE RUN ON AN ACTIVE FILESYSTEM.
# echo $?
0

ALSO:

# fsck /mnt
/sbin/ufs_fsck /mnt
Can't make sense out of name /mnt
# echo $?
0

PROBLEM:  (QAR 46424)	 (Patch ID: OSF410-400221)
********
This patch fixes a problem in which the UFS property list can become corrupted

To reproduce this problem, complete the following steps:

1. Create a relatively large property value on a file.
2. Create another property value on the same file.
B
3. Change the property value created in Step 1 to a smaller value.
4. Run fsck with the -o flag.

The fsck command reports that the file system is corrupted and displays the
following error message:

        ** Phase 1 - Check Blocks and Sizes
        PROPERTY LIST BLOCK CORRUPTED I=3
        CLEAR? [yn]

PROBLEM:  (TKTB68852)    (Patch ID: OSF410-405068)
********
This patch fixes a performance regression that may occur as a result of v4.0b
patch OSF400-405045.  To date this performance regression has been reported only
on the Noritake platform and on the single-ended KZPBA adapter used on the
Rawhide platform.

This patch also implements HSZ70 support for those system that have the
hardware installed.

PROBLEM:  (MCPM11KK6)	 (Patch ID: OSF410-405058-1)
********
This patch provides support for the fuser utility. This utility displays a list 
of processes that are holding references to a file on the file system that
cannot be unmounted. This utility can also be used to terminate a process so 
the file system can be unmounted.


FILE(s):

/usr/sbin/audit_tool            	subset OSFBASE410
CHECKSUM: 29601    168     RCSfile: audit_tool.c    RCS: 1.1.30.2
/sys/BINARY/arch_alpha.mod		subset OSFHWBIN410
CHECKSUM: 34040    442 
/sys/BINARY/arch_alphapmap.mod		subset OSFHWBIN410
CHECKSUM: 62847    181
/sys/BINARY/cam.mod                     subset OSFHWBIN410
CHECKSUM: 53174    416 
/sys/BINARY/cam_disk.mod        	subset OSFHWBIN410
CHECKSUM: 58279    291
/usr/sys/include/io/cam/cam_disk.h      subset OSFBINCOM410
CHECKSUM: 05627     27     RCSfile: cam_disk.h      RCS: 1.1.62.2
/sys/BINARY/cam_isp1020.mod       	subset OSFHWBIN410
CHECKSUM: 23196     98
/sys/BINARY/cam_sim.mod      		subset OSFHWBIN410
CHECKSUM: 03476    192
/usr/bin/lastcomm               	subset OSFBASE410
CHECKSUM: 07525     24     RCSfile: lastcomm.c      RCS: 4.2.20.2
/usr/sys/include/io/cam/qlogic/isp1020.h  subset OSFBINCOM410
CHECKSUM: 59913     43     RCSfile: isp1020.h       RCS: 1.1.80.3
/usr/sys/include/io/cam/ccfg.h          subset OSFBINCOM410
CHECKSUM: 26623     11     RCSfile: ccfg.h   	    RCS: 1.1.21.2
/usr/sys/include/sys/fcntl.h		subset OSFBINCOM410 
CHECKSUM: 17491     10     RCSfile: fcntl.h         RCS: 4.2.46.3
/usr/sys/include/sys/fcntl1.h		subset OSFBINCOM410 
CHECKSUM: 18748      3     RCSfile: fcntl1.h        RCS: 1.1.2.2
/usr/sys/include/io/cam/sim.h         	subset OSFBINCOM410
CHECKSUM: 62806     35     RCSfile: sim.h    	    RCS: 1.1.61.2
/sys/BINARY/ether.mod   	        subset OSFBIN410
CHECKSUM: 14908    133
/sys/BINARY/ffm_fs.mod          	subset OSFBIN410
CHECKSUM: 02865     24
/sys/BINARY/inet.mod  		        subset OSFBIN410
CHECKSUM: 44940    283
/sys/BINARY/loop.mod            	subset OSFBIN410
CHECKSUM: 27060     15
/sys/BINARY/nfs.mod             	subset OSFBIN410
CHECKSUM: 52471    424
/usr/sys/include/ufs/fs_proto.h		subset OSFBINCOM410 
CHECKSUM: 39564     12     RCSfile: fs_proto.h     RCS: 1.1.30.2
/usr/sys/include/ufs/inode.h		subset OSFBINCOM410 
CHECKSUM: 49905     13     RCSfile: inode.h        RCS: 4.3.39.2
/usr/sys/include/sys/siginfo.h          subset OSFBINCOM410
CHECKSUM: 65468     12     RCSfile: siginfo.h      RCS: 1.1.32.2
/usr/sys/include/sys/signal.h           subset OSFBINCOM410
CHECKSUM: 47393     25     RCSfile: signal.h       RCS: 4.3.29.4
/usr/sys/include/sys/time.h             subset OSFBINCOM410
CHECKSUM: 08607      9     RCSfile: time.h         RCS: 4.4.46.2
/usr/sys/kern/lockinfo.c                subset OSFBINCOM410
CHECKSUM: 55913     96     RCSfile: lockinfo.c	   RCS: 1.1.346.2
/sys/BINARY/presto.mod			subset OSFBIN410
CHECKSUM: 32549    148
/sys/BINARY/procfs.mod		        subset OSFBIN410
CHECKSUM: 14471    184 
/sys/BINARY/re_xcr.mod                  subset OSFHWBIN410
CHECKSUM: 58541     66
/sys/BINARY/socket.mod  	        subset OSFBIN410
CHECKSUM: 02540      3
/sys/BINARY/std_kern.mod                subset OSFBIN410
CHECKSUM: 47064    1098
/sys/BINARY/ufs.mod   		        subset OSFBIN410
CHECKSUM: 00723    325
/sbin/ufs_fsck          		subset OSFBASE410
CHECKSUM: 65429    472
/usr/sbin/ufs_fsck     			subset OSFBASE410
CHECKSUM: 09825    104
/sys/BINARY/vfs.mod			subset OSFBIN410
CHECKSUM: 04260    416
/usr/sys/vfs/vfs_conf.c			subset OSFBINCOM410
CHECKSUM: 46207     11  i  RCSfile: vfs_conf.c	    RCS: 4.2.52.3
/sys/BINARY/vm.mod              	subset OSFBIN410
CHECKSUM: 64566    425
/usr/sbin/ifconfig             		subset OSFCLINET410
CHECKSUM: 51561     40
/usr/sys/include/netinet/tcp_var.h      subset OSFBINCOM410
CHECKSUM: 55999     14     RCSfile: tcp_var.h       RCS: 4.2.42.2
/usr/sys/include/netinet/tcp_timer.h    subset OSFBINCOM410
CHECKSUM: 35982      8     RCSfile: tcp_timer.h     RCS: 4.2.29.2
/usr/sys/include/netinet/ip_var.h       subset OSFBINCOM410
CHECKSUM: 03575     10     RCSfile: ip_var.h        RCS: 4.4.28.2
/usr/sys/include/netinet/proto_inet.h   subset OSFBINCOM410
CHECKSUM: 37937     10     RCSfile: proto_inet.h    RCS: 4.3.45.2
/usr/sys/include/netinet/in_pcb.h
CHECKSUM: 57265     11 
/usr/sys/include/net/if.h               subset OSFBINCOM410
CHECKSUM: 46497     43     RCSfile: if.h            RCS: 4.3.91.2
/usr/sys/include/sys/malloc.h           subset OSFBINCOM410
CHECKSUM: 46851     18     RCSfile: malloc.h        RCS: 1.1.58.2
/usr/sys/include/sys/socketvar.h        subset OSFBINCOM410
CHECKSUM: 62432     14     RCSfile: socketvar.h     RCS: 4.2.54.2
/usr/sys/include/sys/user.h             subset OSFBINCOM410
CHECKSUM: 20092     24     RCSfile: user.h          RCS: 4.3.76.2
