PROBLEM: (BCGMC1JRS UVO106265) (Patch ID: OSF440-011) ******** This patch fixes a problem where process accounting data was not written to the accounting file when it was on an NFS-mounted file system. This problem occurred on Dataless Management Services (DMS) client systems. To correct this problem, this patch must be installed on the DMS client. It does not need to be installed on the DMS server. This corrects a "simple_lock: time limit exceeded" panic in softclock_scan(). PROBLEM: (HPAQ30BCD) (Patch ID: OSF440-012) ******** This patch fixes a kernel memory fault from socket code. The kernel memory fault results from failing to get a lock on a list of threads which have requested resources on a socket. The stack will contain: _XentMM simple_lock select_wakeup sowakeup soisconnected PROBLEM: (BRO101278) (Patch ID: OSF440-015) ******** This is to correct a problem where a signal is delivered, but not responded to by the target process. PROBLEM: (BCPMC1GPQ) (Patch ID: OSF440-003) ******** This is to fix a panic of "get_color_bucket: empty buckets" when the sysconfig attribute "private-cache-percent" is non-zero. PROBLEM: (None) (Patch ID: OSF440-061) ******** Deleted files still occupy filesystem space until the last reference on that file gets closed. PROBLEM: (QAR 65033, QAR 61856, QAR 64040, SSRT0563U, HPAQC08NV) (Patch ID: OSF440-032) ******** A potential security vulnerability has been discovered where under certain circumstances users may gain unauthorized access. Compaq has corrected this potential vulnerability. PROBLEM: (QAR 62614) (Patch ID: OSF440-033) ******** This patch fixes a problem with the mount command where it sometimes kills other processes. This randomly occurs if the file where mount stores its pid, /var/run/mountd.pid, is out-of-date. PROBLEM: (BCGM50N91) (Patch ID: OSF440-120) ******** This patch fixes a problem where process accounting data was not written to the accounting file and the following message was displayed when the accounting file was on an NFS-mounted file system: NFS3 write error 13 on host This problem occurred on Dataless Management Services (DMS) client systems. PROBLEM: (QAR 73131) (Patch ID: OSF440-123) ******** Occasionally, 3rd-party drivers fail to configure when the first device configured is not zero. Additionally, some drivers support a maximum number of devices and a constantly increasing base controller number, caused by reloads, may cause the driver maximum to be exceeded. This can also cause loadable drivers to fail to configure. A loadble driver that is loaded/configured, unloaded/unconfigured, then re-loaded/re-configured gets increasing controller number values on each re-load. Most loadable drivers prefer (or require) the controller numbers to begin at zero and increase as the number of matching devices are found on a system. PROBLEM: (QAR 72971 CLD MGO104088) (Patch ID: OSF440-128) ******** Mount falls back to V2 when a portmap call for the NFS V3 port fails. This logic is incorrect; a portmap timeout doesn't indicate a lack of V3 support. PROBLEM: (QAR 72129, QAR 73203, CLD HPAQ500L1) (Patch ID: OSF440-132) ******** This problem fixes an nfs/ufs/vm deadlock. While serving a client, the system running ASE/DT as an NFS server can hang with deadlock. PROBLEM: (QAR 72626, CLD BCPM50LZC) (Patch ID: OSF440-133) ******** This patch fixes a problem in which the system may panic with the error message "kernel memory fault". An example panic stack trace is: 0 stop_secondary_cpu 1 panic 2 event_timeout 3 xcpu_puts 4 printf 5 panic 6 trap 7 _XentMM 8 remque 9 in_pcbdetach 10 tcp_close 11 tcp_drop 12 table 13 syscall 14 _Xsyscall PROBLEM: (73146) (Patch ID: OSF440-136) ******** This patch fixes the following KZPCC Raid controller problems: - The disklabel command fails when configuring partitions with non-zero offset - The disklabel -wr command fail with error message; "unknown device type". - Driver logged errors are not reset on subsequent access attempts, thus producing erronous results. - The iostat command does not display nor report the correct information for this device type. It also can produce a "simple lock timeout" panic on a multi-processor system. - Non-generic kernels fail to recognize logical units on boot. - A custom kernel build fails to recognize multiple controllers and their associated drivers - A system hang or deadlock condition caused by the controller not returning command responses due to the lack of resources. The driver can not process responses that it receives to free up the resources. - A kernel crash during SWCC reconfiguration and rescan operations. SWCC does not receive the expected results from the addition and deletion of logical units. - The sizer -r command fails to report the correct information for this device type. - The inability to generate crash dump information on this device type. - A "kernel memory fault" system panic that can occur when system is under a certain level of stress. - A system panic when creating and deleting a high number (1000's) of logical units. - Unable to install or boot from any ri devices that are not on the first unit on the first controller. PROBLEM: (MGO104022) (Patch ID: OSF440-142) ******** This patch fixes a problem where applications using the fcntl() system calls may appear to hang. PROBLEM: (MGO09365A,BCGM41MGB) (Patch ID: OSF440-143) ******** This patch fixes "simple_lock: time limit exceeded" panics. PROBLEM: (QAR 63384) (Patch ID: OSF440-148) ******** This patch fixes a problem in which fork() is sometimes unable to optain swap space and a problem in which the restriction on core file sizes doesn't work as expected. PROBLEM: (STLB42227) (Patch ID: OSF440-152) ******** This patch fixes a problem where the system can panic with the console message, "bs_bf_htop: invalid handle\n N1 = 0". The stack trace of the panicing thread typically looks like: panic advfs_sad bs_bf_htop msfs_getattr pacl_vnperm paclaccess sp_vnaccess msfs_access msfs_lookup namei PROBLEM: (HPAQ40343, HPAQ5062G, UVO20042) (Patch ID: OSF440-155) ******** This patch fixes a problem with heavy I/O loads on UFS filesystems that can result in poor response time; the system could appear to be "paused". In many cases, the system appears to "pause" after an update had executed (a sync is occurring). PROBLEM: (CLD BCSM30WLD ,QARS 69170 70101) (Patch ID: OSF440-039) ******** This patch fixes a problem that causes system panics when thread_swappable is called with the current_thread as the target thread, when the thread is about to be swapped out. PROBLEM: (BCGM40GGH, 71213) (Patch ID: OSF440-067) ******** This patch fixes a problem where the map entry indexing scheme does not handle the case when a bucket is emptied due to several unmaps. When the last entry in a bucket is deleted, the bucket head may point to the map itself. When this happens, subsequent address space lookup and deletion will fail, resulting in the following panic: "pmap_release_page: page not found" PROBLEM: (QAR 66356) (Patch ID: OSF440-081) ******** This patch fixes a problem in which certain invalid kernel address ranges may get ignored.This can result in invalid kernel memory accesses to be left unnoticed. PROBLEM: (QARS 71524 66356) (Patch ID: OSF440-085) ******** This patch fixes a problem that causes the Tru64 UNIX Version 5.0 update install procedure to exit with core dumps and /sbin/loader failures on a system. PROBLEM: (BRO101307 & BCSM11QV2 ,QAR 70038) (Patch ID: OSF440-095) ******** This patch fixes a problem in the module core() that can cause a panic with the message: vrele: bad ref count. The stack trace may look like the following example: 0 stop_secondary_cpu() 1 panic("event_timeout: panic request") 2 event_timeout() 3 xcpu_puts() 4 printf() 5 panic("vrele: bad ref count") 6 vrele() The problem occurs if a set UID, or GID, program attempts to dump core in a directory that already contains a symbolic link with the name "core", and if the link points to a non-existent path. PROBLEM: (HPAQ50FLC, QAR 71826, QAR 71891, QAR 68458) (Patch ID: OSF440-099) ******** 1) Panic in the kernel with the following error message: simple_lock: time limit exceeded Stack trace is as follows: panic simple_lock_fault simple_lock_time_violation pmap_ssm_enter u_ssm_fault u_map_fault vm_fault ... 2) A panic occurs when booting kernel interactively and setting the memlimit. The panic error message is as follows: kernel memory fault PROBLEM: (QAR 56967) (Patch ID: OSF440-104) ******** This patch fixes a problem with kdbx in which it creates a core in the root directory when recovering from a system crash. After a system crash, and a subsequent reboot, a core file is found under the root directory, /. Using the file command (which must be run by superuser, due to the protection on /core) will show that the file was created by kdbx. PROBLEM: (None) (Patch ID: OSF440-138) ******** This patch removes a Granularity Hint Regions (a.k.a., GH Chunks) restriction which may be encountered on AlphaServer DS20 and ES40 systems running the Digital UNIX V4.0F release. This restriction can reduce performance for certain data base applications. See the Patch Summary and Release Notes document for further information. PROBLEM: (QAR 73146) (Patch ID: OSF440-164) ******** This patch fixes several system hangs/crashes that could occur when the driver finds it necessary to re-initialize the KZPCC controller. (The driver contains code to do this re-initialization in case the controller stops responding to I/O requests for any reason.) PROBLEM: (MGO104025) (Patch ID: OSF440-144) ******** This patch fixes a system hang condition. All NFS related services may deadlock.