PROBLEM: (QAR 60885, 58783, 59316, 59652, 59659, 59727) (Patch ID: OSF425-485) ******** This patch restores proper functionality of the /usr/sbin/newfs command, which is used to create a new UFS file system. The patch fixes several problems and is recommended as an update to the existing version of newfs on all systems. PROBLEM: (QAR 64136) (Patch ID: OSF425-635) ******** This patch fixes a problem with the newfs command. Prior to this patch, when the newfs -N command was run on a mounted file system, it returned an error message similar to the following: newfs: /dev/rrz0c: is marked in the disklabel as in use by: 4.2BSD The command now completes succesfully and returns the correct partition information. PROBLEM: (HPAQ2157C) (Patch ID: OSF425-189) ******** This patch fixes a problem in the streams code which could have resulted in data corruption. PROBLEM: (Patch ID: OSF425-165) ******** When printing a large file using DIGITAL UNIX LAT, through a terminal server to a slow printer with a small print buffer (ex. an LA75), the last page or so of the file may not get printed. No errors are reported. Before the line discipline streams module (ldtty) closes, it sleeps for 30 seconds, waiting for the write queue to drain. In this situation, the sleep time needs to be longer. There is a kernel global variable, ldtty_drain_tmo, that specifies this time. This variable can now be patched using dbx. # dbx -k /vmunix (dbx) print ldtty_drain_tmo 30 (dbx) patch ldtty_drain_tmo=60 60 (dbx) quit # Some experimentation may be necessary to find the correct value for a specific customer environment. PROBLEM: (QAR 52115) (Patch ID: OSF425-091) ******** An application running System V using psuedoterminals may hang if it opens the the slave side before the master is open. If the slave side of a System V master psuedoterminal is opened before it is unlocked on the master side via unlockpt(), the calling process will block forever on the open() even after the unlockpt() has been issued and the lock flag lifted from the device. Once the out of sequence race condition occurs, the slave device cannot be opened again by any process until the original hung process is terminated. PROBLEM: (QAR 59061,QAR 60044) (Patch ID: OSF425-222) ******** The ASDU netbeui server (nbelink) will not close a connection. It will hang in dlcb_close awaiting a STREAMS event. Subsequently, new connections will not be able to connect to nbelink. This fix corrects a problem introduced by the STREAMS fix to CLD MCGM80LHH/QAR GM80LHH/QAR 55462. PROBLEM: (QAR 57417,CLD MCGM80LHH,CLD MCGM91B24) (Patch ID: OSF425-222) ******** This patch fixes a problem that occurs on an SMP system when running STREAMS. The system panics with the following error message: "kernel memory fault" A sample stack trace is shown as follows: 0 boot() ["../../../../src/kernel/arch/alpha/machdep.c":2484,] 1 panic(s = 0xfffffc0000687e40 = "kernel memory fault") 2 trap() ["../../../../src/kernel/arch/alpha/trap.c":1525,] 3 _XentMM() ["../../../../src/kernel/arch/alpha/locore.s":1424,] 4 simple_lock_D() ["../../../../src/kernel/arch/alpha/lockprim.s":749,] 5 ptm_wsrv() ["../../../../src/kernel/tty/pty.c":2569,] 6 sq_wrapper() ["../../../../src/kernel/streams/str_runq.c":138,] 7 csq_lateral() ["../../../../src/kernel/streams/str_synch.c":992,] 8 runq_run() ["../../../../src/kernel/streams/str_runq.c":109,] 9 netisr_thread() ["../../../../src/kernel/net/netisr.c":863,] PROBLEM: (QAR 57417,CLD MCGM91B24) (Patch ID: OSF425-222) ******** This patch fixes a problem that occurs on an SMP system when running STREAMS. The system panics with the following error message: "kernel memory fault" A sample stack trace is shown as follows: 0 boot() ["../../../../src/kernel/arch/alpha/machdep.c":1763,] 1 panic(s = 0xfffffc0000586480 = "kernel memory fault") 2 trap() ["../../../../src/kernel/arch/alpha/trap.c":1243, 0xfffffc000047c614 3 _XentMM() ["../../../../src/kernel/arch/alpha/locore.s":1307,] 4 ldtty_wsrv() ["../../../../src/kernel/tty/ldtty.c":749,] 5 sq_wrapper() ["../../../../src/kernel/streams/str_runq.c":] 6 csq_lateral() ["../../../../src/kernel/streams/str_synch.c":977,] 7 runq_run() ["../../../../src/kernel/streams/str_runq.c":108,] 8 netisr_thread() ["../../../../src/kernel/net/netisr.c"] PROBLEM: (QAR 57417,CLD MCGM80LHH,CLD MCGM91B24) (Patch ID: OSF425-156) ******** This patch fixes a problem that occurs on an SMP system when running STREAMS. The system panics with the following error message: "kernel memory fault" A sample stack trace is shown as follows: 0 boot() ["../../../../src/kernel/arch/alpha/machdep.c":2484,] 1 panic(s = 0xfffffc0000687e40 = "kernel memory fault") 2 trap() ["../../../../src/kernel/arch/alpha/trap.c":1525,] 3 _XentMM() ["../../../../src/kernel/arch/alpha/locore.s":1424,] 4 simple_lock_D() ["../../../../src/kernel/arch/alpha/lockprim.s":749,] 5 ptm_wsrv() ["../../../../src/kernel/tty/pty.c":2569,] 6 sq_wrapper() ["../../../../src/kernel/streams/str_runq.c":138,] 7 csq_lateral() ["../../../../src/kernel/streams/str_synch.c":992,] 8 runq_run() ["../../../../src/kernel/streams/str_runq.c":109,] 9 netisr_thread() ["../../../../src/kernel/net/netisr.c":863,] PROBLEM: (QAR 59061) (Patch ID: OSF425-405202) ******** The ASDU netbeui server (nbelink) will not close a connection. It will hang in dlcb_close awaiting a STREAMS event. Subsequently, new connections will not be able to connect to nbelink. This fix corrects a problem introduced by the STREAMS fix to CLD MCGM80LHH/QAR 55462. PROBLEM: (ADP-06754) (Patch ID: OSF425-392) ******** A call to the select() system call may hang or incorrectly indicate that there is a message waiting from a terminal when there is nothing there. PROBLEM: (QAR 63014, QAR 62791) (Patch ID: OSF425-403) ******** This patch fixes a problem in which the system may panic with the following error message "kernel memory fault". An example panic stack trace might look like: > 0 boot 1 panic 2 trap 3 _XentMM 4 rmvq 5 pts_wput 6 csq_lateral 7 puthere 8 ldtty_bsd43_ioctl 9 ldtty_ioctl 10 ldtty_wput 11 csq_lateral 12 puthere 13 osr_str 14 osr_run 15 pse_ioctl 16 spec_ioctl 17 vn_ioctl 18 ioctl_base 19 ioctl 20 syscall 21 _Xsyscall PROBLEM: (QAR 60582 QAR 62161) (Patch ID: OSF425-405432) ******** This patch fixes a problem in which the system panics with one of the following error messages: simple_lock: uninitialized lock simple_lock_terminate: lock busy The stack traces will look similar to the following: simple_lock: uninitialized lock pc of caller: 0xfffffc00004deecc lock address: 0xfffffc0009d83ca8 lock class name: unknown_simple_lock current lock state: 0x0000000000000000 (cpu=0,pc=0x0,free) simple locks held lock fffffc00008c3980, data c400014d004deec5 panic (cpu 0): simple_lock: uninitialized lock simple_lock_terminate: lock busy pc of caller: 0xfffffc0000489034 lock address: 0xfffffc000a6e9cb8 lock info addr: 0xfffffc00009db370 lock class name: sqh_s.sqh_lock current lock state: 0xc40301370048ae75 (cpu=3,pc=0xfffffc000048ae74,busy) panic (cpu 0): simple_lock_terminate: lock busy PROBLEM: (TKTRB0985) (Patch ID: OSF425-410246) ******** This patch fixes a kernel problem, where proper locking/reference count management was not being performed. This could result in a panic with the stack trace: 5 panic(s = 0xfffffc0000777888 = "lock_terminate: lock held") 6 lock_terminate 7 pgdelete 8 pgrp_unref 9 pgrm 10 proc_teardown 11 waitf 12 wait4 13 syscall 14 _Xsyscall PROBLEM: (QAR 52525,QAR 46833) (Patch ID: OSF425-064) ******** This patch fixes a problem in which a system hang or core dump occurs when one program inadvertently overwrites the contents of another program. For example, a program, test1, is running and another program, test2, is copied ("cp") onto test1, overwriting the contents of test1. The result is a system hang or a core dump. An example of the problem follows: On one window start running ./test1, while on another: # cp test2 test1 The result is shown here: # ./test1 . . . Test2 looping -- 2819 Test2 looping -- 281a Test2 looping -- 281b Memory fault - core dumped # ls -l core -rw------- 1 root system 360448 May 22 18:46 core An example with the patch shows: On one window start running ./test1, while on another: # cp test2 test1 cp: test1: Text file busy # cp test2 test1 cp: test1: Text file busy The result is shown here: # ./test1 . . . Test2 looping -- 2819 Test2 looping -- 281a Test2 looping -- 281b # ls -l total 50 -rwxr-xr-x 1 root system 24576 May 20 20:05 test1 -rw-r--r-- 1 root system 121 May 20 20:03 test1.c -rwxr-xr-x 1 root system 24576 May 20 20:05 test2 -rw-r--r-- 1 root system 121 May 20 20:03 test2.c PROBLEM: (CLD FNO100139) (Patch ID: OSF425-066) ******** When a directory path on an NFS server is deleted, any process attempting to access the missing path will cause NFS stale file handle messages to be printed on the server's console. This patch will greatly reduce the number of these messages. PROBLEM: (FNO100126, UTO101198, MGO102729, UVO105463, MGO102993, TKTB91678, ******** QAR 43407) (Patch ID: OSF425-080) This patch fixes a panic with the panic string "spec_badop called", that can sometimes occur when an fpathconf system call is issued for a file in AdvFS filesystem. The panic has following stack trace: panic (s = "spec_badop called") spec_badop fpathconf syscall _Xsyscall PROBLEM: (QAR 57806) (Patch ID: OSF425-120) ******** If the system has a missing or corrupt /etc/sysconfigtab file, or is being used with the "N" boot flag for 23-second fastboot, the system will crash very early with: trap: invalid memory read access from kernel mode faulting virtual address: 0x0000000000000000 pc of faulting instruction: 0xfffffc0000233f84 ra contents at time of fault: 0xfffffc0000233f74 sp contents at time of fault: 0x0000000020016a88 panic (cpu 0): kernel memory fault DUMP: No primary swap, no explicit dumpdev. Nowhere to put header, giving up. PROBLEM: (QAR 57707) (Patch ID: OSF425-121) ******** This patch fixes a problem in which the uswitch(2) system call does not work when an application tries to reset the USW_NULLP option. When this option is set, /dev/zero is mapped for read-only references at address 0, allowing subsequent user NULL pointer read references to return to zero. If the option is reset (turned off), however, the mapping is not removed, and the task's VM map's minimum virtual address is left at zero, rather that at VM_MIN_ADDRESS (0x10000). The problem may manifest itself in failures of the libaio library code. The libaio libary code maps a page in low memory, which it expects to be, at a minimum, VM_MIN_ADDRESS. However, with the task's minimum virtual address incorrectly left set to 0, the kernel returns an aio mapping address of 0. The libaio code, however, considers an address of 0 as an indication that the the mapping has failed. PROBLEM: (Patch ID:OSF425-146) ******** This problem can be identified by examining the crash_data file from a kernel crash dump. Several important pieces of information, including the panic string will not be present. PROBLEM: (DEKQA0200) (Patch ID: OSF425-148) ******** A potential security vulnerability has been discovered, where under certain circumstances, system integrity may be compromised. This may be in the form of improper file or privilege management. DIGITAL has corrected this potential vulnerability. PROBLEM: (SSRT0521U) (Patch ID: OSF425-160) ******** A potential security vulnerability has been discovered, where under certain circumstances, system integrity may be compromised. This may be in the form of improper file or privilege management. DIGITAL has corrected this potential vulnerability. PROBLEM: (QAR 58368) (Patch ID: OSF425-161 ) ******** This patch corrects a potential problem with graphics drivers that could potentially affect any EV56-based system. The problem manifests itself as as corruption of the images displayed by the drivers, such as desktop or taskbar icons and buttons. The problem may occur when the underlying chip hardware supports a new set of byte-granular instructions but the graphics adapter does not. PROBLEM: (EVT102135, HPAQ50J6Z, SQO100374, MCPM50UKH, EVT102245, ******** KAOB6KRMX, QAR 52779, QAR 52525 ) (Patch ID: OSF425-170) This is a mandatory patch for the following systems and conditions: . Systems that use program debuggers such as TotalView, Ladebug, dbx, or gdb. . Systems that use the /proc file system in any other way (for example, the System V Environment ps command). . Systems that experience panics and hangs in the /proc file system. The most common panic string is "kernel memory fault"; also seen are "simple_lock time limit exceeded" panics. In all cases, a routine with the string "procfs_" will appear in the kernel stack trace. Hangs usually involve either the debugger or debugged process or both entering the unkillable "U" state, as seen from the ps command. The hangs may be either quiescent or compute bound. Other symptoms involve "" processes be left behind after a debugging session is terminated. This patch is particularly important for debugging in a multithreaded environment on multiprocessor systems. The greater the concurrency of the program being debugged, and the greater the number of processors, the more likely problems are to occur. PROBLEM: (ISO100331) (Patch ID: OSF425-153) ******** A mulithreaded program that calls an exec() function can panic the system with a kernel memory fault. A typical stack trace looks like this: 0 boot() 1 panic("kernel memory fault") 2 trap() 3 _XentMM() 4 nxm_upcall() 5 trap() 6 _Xsyscall() The critical feature of the stack trace is the presence of the nxm_upcall() function prior to the kernel memory fault. The crash dump will show that the thread is in process of processing an thread-block notification system trap. PROBLEM: (QAR 46424) (Patch ID: OSF425-178) ******** 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. 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: (FNO100126, UTO101198, MGO102729, UVO105463, MGO102993, TKTB91678, ******** QAR 43407) (Patch ID: OSF425-405120) This patch fixes a panic with the panic string "spec_badop called", that can sometimes occur when an fpathconf system call is issued for a file in AdvFS for a file in an AdvFS filesystem. The panic has following stack trace: panic (s = "spec_badop called") spec_badop fpathconf syscall _Xsyscall PROBLEM: (QAR 57707) (Patch ID: OSF425-400461) ******** This patch fixes a problem in which the uswitch(2) system call does not work when an application tries to reset the USW_NULLP option. When this option is set, /dev/zero is mapped for read-only references at address 0, allowing subsequent user NULL pointer read references to return a zero. If the option is reset (turned off), however, the mapping is not removed, and the task's VM map's minimum virtual address is left at zero, rather than at VM_MIN_ADDRESS (0x10000). The problem may manifest itself in failures of the libaio library code. The libaio libary code maps a page in low memory, which it expects to be, at a minimum, VM_MIN_ADDRESS. However, with the task's minimum virtual address incorrectly left set to 0, the kernel returns an aio mapping address of 0. The libaio code, however, considers an address of 0 as an indication that the mapping has failed. PROBLEM: (QAR 45510,QAR 52698) (Patch ID: OSF425-400451) ******** This patch fixes a problem with the ufs_fsck. ufs_fsck would mishandle certain dir corruptions, recursively asking the user if they want to fix it. For example: Corrupt the filesystem using fsdb. #fsdb -w /dev/rz3g >4:dir=45 >:q # Note: 4:dir=45 will change the inode number of the fourth directory entry to 45. Run ufs_fsck with -o option. #ufs_fsck -o /dev/rz3g ** /dev/rrz3g ** Last Mounted on /mnt ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames DIRECTORY CORRUPTED I=2 OWNER=root MODE=40755 SIZE=512 MTIME=Dec 10 11:21 1997 DIR= SALVAGE? [yn] n Directory corruption not fixed, cannot not handle multiple errors. DIRECTORY SCAN CONTINUE? [yn] 1d) Internal description ufs_fsck would mishandle certain dir corruptions, recursively asking the user if they want to fix it. PROBLEM: (QAR 46500,57146) (Patch ID: OSF425-172) ******** This patch fixes a problem with the nfsd daemon. Although the maximum number of threads that nfsd can run is 128, the nfsd daemon will not start when the sum of UDP threads and TCP threads equals 128. PROBLEM: (QAR 57454, QAR 53780, QAR 54825) (Patch ID: OSF425-188) ******** This patch improves performance on low-memory (32MB) systems. PROBLEM: (CLD MCPM911C6,CLD MCPM911CF,CLD USG-05807) (Patch ID: OSF425-192) ******** This Patch provides two new procfs ioctls (PIOCUSAGE and PIOCTUSAGE) to collect task and thread wait time statistics. PROBLEM: (MCPM30JWW/QAR 59301, 58412) (Patch ID: OSF425-196) ******** This patch corrects a hang condition with applications that use network sockets. How to recognize this problem: If you run a program that opens many sockets and sends a lot of data (like 100+ megabits per second with megabytes in network buffers) then send a Control -C to the application, the networking on the system slows down and may lock up or hang. You cannot ping the system and if it contains multiple interfaces, none of them will respond to ping. Otherwise the system appears fine. Other symptoms: netstat ifconfig XXX up/down does not hang, but does no good ifconfig XXX unplumb hangs. PROBLEM: (MXOB30447 QAR 60006) (Patch ID: OSF425-213) ******** As an aide to debugging kernel memory corruption, this fix extends the KMEM_DEBUG_PROTECT option of kmem_debug to allow the protection of 8192-byte bucket elements while they are on the kmembucket free list. PROBLEM: (QAR 60285, MCGM91LZQ, UVO105302, EVT102394) (Patch ID: OSF425-223) ******** This patch fixes a problem where the umount of a filesystem will fail with "mount device busy", but no processes are accessing files in the filesystem. PROBLEM: (QAR 58257,48719,49229,52020) (Patch ID: OSF425-229) ******** This patch fixes a problem with the ufs_fsck program in which filesystem corruption may occur on a running system when the root filesystem is mounted writable. PROBLEM: (UVO105930/QAR 59429) (Patch ID: OSF425-231) ******** This patch is MANDATORY to install. This patch fixes a kernel memory fault in the networking code with the following stack trace: panic trap _XentMM ip_output ip_forward gw_forwardscreen ip_forwardscreen ip_dooptions ipintr netisr_thread PROBLEM: (QAR 56327,59459) (Patch ID: OSF425-236) ******** This patch fixes a panic in the virtual memory management system. The system displays the following error message: trap: invalid memory read access from kernel mode The stack trace is as follows: 0 boot 1 panic 2 trap 3 _XentMM 4 vm_pageout_scan 5 vm_pageout_loop PROBLEM: (QAR 58558,60143) (Patch ID: OSF425-242) ******** This patch fixes a problem that produces a core dump when running the quotacheck -a command. The following panic string is displayed: Segmentation fault at strcmp PROBLEM: (QAR 60536,MGO103458) (Patch ID: OSF425-248) ******** This patch fixes a kernel memory fault panic. This patch is mandatory for all multiprocessor machines. The patch fixes a potential memory corruption of the akl_pagelist. PROBLEM: (QAR 59295) (Patch ID: OSF425-202 ) ******** When running a multi-threaded program that creates both process contention scope (PCS) and system contention scope (SCS) threads, the scheduling policy and/or priority of a terminating SCS thread can be transferred to a PCS thread resulting in unexpected performance variations or degradations. This can be observed using the ps command (e.g., ps -m -O SCHED). PROBLEM: (CLD UTO101199,HPAQ30ETE,QAR 51485,52365) (Patch ID: OSF425-061) ******** This patch corrects a problem with an NFS V3 mounted AdvFS file system where under heavy I/O load, data being written to a file may be lost. Additionally, because file stats are not being saved, the file modification time may revert to a previous value. PROBLEM: (MCGMC1645) (Patch ID: OSF425-405207) ******** This patch fixes a kernel memory fault panic in purge_fs_locks. This problem is normally only seen on ASE or TruCluster systems. A sample stack trace may look like: 0 stop_secondary_cpu() 1 panic("event_timeout: panic request") 2 event_timeout() 3 xcpu_puts() 4 printf() 5 panic("kernel memory fault") 6 trap() 7 _XentMM() 8 purge_fs_locks() 9 fcntl() 10 syscall() 11 _Xsyscall() PROBLEM: (QAR 59319) (Patch ID: OSF425-405238) ******** This patch fixed several problems with vfs file locking that could cause a crash including the file lock adjust logic, delete sleep lock logic, dead file lock logic, check/change granted logic, and insert file lock logic. PROBLEM: (BRO101068/TKTR90901/QAR 55619) (Patch ID: OSF425-252) ******** This patch is MANDATORY to install. Fixes kernel memory faults in networking code. The stack trace will look like this: panic trap _XentMM ip_output ip_forward gw_forwardscreen ip_forwardscreen ipintr netisr_thread PROBLEM: (MGO103468) (Patch ID: OSF425-284) ******** This patch fixes a "mount device busy" problem that occurs when a user can not overwrite the file "core". This prevents the filesystem from being umount'ed. PROBLEM: (FNO100138) (Patch ID: OSF425-176) ******** This patch fixes a 'recursion count overflow' panic that occurs on DIGITAL UNIX. Representative Stack trace: panic ("lock_set_recursive: recursion count overflow") src/kernel/bsd/subr_prf.c :791 lock_fault() src/kernel/kern/lock.c : 2003 lock_set_recursive() src/kernel/kern/lock.c : 1444 makenfs3node() src/kernel/nfs/nfs_subr.c : 1722 nfs3_lookup() src/kernel/nfs/nfs3_vnodeops.c : 2157 namei() src/kernel/vfs/vfs_lookup.c : 593 stat1() src/kernel/vfs/vfs_syscalls.c : 2801 stat() src/kernel/vfs/vfs_syscalls.c : 2769 PROBLEM: (QAR 59255) (Patch ID: OSF425-405330) ******** This patch corrects a problem that would randomly cause kloadsrv(8) to crash and improperly load/unload modules. PROBLEM: (EVT102538, EVT102513, QAR 60321) (Patch ID: OSF425-230) ******** This patch fixes a problem that occurs with applications based on POSIX message queues. During certain high activity periods, processes may hang when trying to access the message queue. A sample stack trace is as follows: 0 thread_block 1 mpsleep 2 psx4_csem_sleep_wakeup 3 syscall 4 _Xsyscall PROBLEM: (QAR 56172, QAR 55808, QAR 66453) (Patch ID: OSF425-253) ******** This patch fixes the following problems: 1. Process hangs caused by file references on raw devices accesses not being held. The patch uses locks on references and the unreferences so the file will not be prematurely closed. 2. A "kernel memory fault" system panic caused by AIO not cleaning up test headers when processes exit. This can cause signals to be sent to incorrect processes and/or system crashes. An example of a system panic stack trace is as follows: 1 panic() 2 event_timeout() 3 xcpu_puts() 4 printf() 5 panic() 6 trap() 7 _XentMM() 8 sigq_enqueue_tail() 9 psignal_internal() 11 aio_transfer_done() 12 syscall() 13 _Xsyscall() PROBLEM: (QAR 59562, QAR 60399) (Patch ID: OSF425-256) ******** This patch fixes a problem with the vmstat -M command. vmstat -M shows an invalid byte count associated with the FREE malloc type. PROBLEM: (UVO105963/QAR 60496) (Patch ID: OSF425-258) ******** This patch fixes a network socket problem that causes the XAPI agents to hang when using MAILbus400 2.0A with Digital Unix 4.0D. PROBLEM: (QAR 59011, QAR 59858) (Patch ID: OSF425-260) ******** This patch fixes a problem in thread.c that produced "thread_halt" panics under testing loads. Stack traces similar to the following were produced: 1 panic () 2 event_timeout() 3 xcpu_puts() 4 printf() 5 panic() 6 thread_halt() 7 task_halt_or_terminate_threads() 8 task_halt() 9 sigexit() 10 psig() 11 nxm_idle 12 _Xsyscall() PROBLEM: (QAR 60175) (Patch ID: OSF425-265) ******** This patch corrects a problem where a flag, TF_PSUSP, was not being cleared. PROBLEM: (QAR 59849, QAR 58696) (Patch ID: OSF425-272) ******** This patch fixes a problem when a processor is commanded to stop during a heavy load but does not actually halt. PROBLEM: (MGO103472) (Patch ID: OSF425-273) ******** This corrects a performance problem with posix timers. PROBLEM: (HPAQ41QK2) (Patch ID: OSF425-277) ******** A problem in the msgsnd() routine can result in a kernel memory fault panic if the message size is zero. The following is a representative stack trace: 1 panic 2 trap 3 _XentMM 4 free_common 5 free 6 msgsnd 7 syscall 8 _Xsyscall PROBLEM: (QAR 59878, QAR 53422) (Patch ID: OSF425-308) ******** This patch fixes a problem within LMF. The LMF user license list (OSF-BASE or OSF-USR) was not being decremented when a logout occurred. This occurs on systems with C2 security enabled and the system setup as a DCE Security server. PROBLEM: (CLD DEKB10974,QAR 62152) (Patch ID: OSF425-328) ******** This patch avoids a "kernel memory fault" panic from sigsgdisp(). The problem has only been seen when shutting down an Oracle database. A sample stack trace is shown in the following example: 5 panic("kernel memory fault") ["../../../../src/kernel/bsd/subr_prf.c":753] 6 trap() ["../../../../src/kernel/arch/alpha/trap.c":1539] 7 _XentMM() ["../../../../src/kernel/arch/alpha/locore.s":1424] 8 sigsgdisp() ["../../../../src/kernel/bsd/kern_sig.c":1471] 9 sigaction() ["../../../../src/kernel/bsd/kern_sig.c":1706] PROBLEM: (CA8B54472) (Patch ID: OSF425-339) ******** This patch fixes a socket memory leak seen in the sonewsocknolock() routine. PROBLEM: (QAR 58800, QAR 59115, QAR 58440) (Patch ID: OSF425-340) ******** This patch fixes a problem with the "vmstat -M" command. This command displays negative values for memory usage by type and AdvFS buffer usage. PROBLEM: (MGO103468) (Patch ID: OSF425-396) ******** This patch fixes various problems caused when a set UID/GID program dumped core. The problems included system panics and "mount device busy" errors when trying to umount the filesystem. A typical stack trace for the panic thread would have the routine core() in it. PROBLEM: (BCGM70W61, UVO105916) (Patch ID: OSF425-416) ******** This patch fixes a problem when a setuid program exec's and the message "privileges disabled because of outstanding IPC access to task". PROBLEM: (QAR 59367) (Patch ID: OSF425-289) ******** This patch adds automatic detection of a cdfs file system for the mount(8) command. PROBLEM: (QAR 59863, QAR 59323) (Patch ID: OSF425-405371) ******** This patch fixes a problem that was caused by both floating point and integer overflow exceptions setting the si_code member in the siginfo structure to FPE_FLTOVF. Integer overflow exceptions should set the si_code member to FPE_INTOVF, as documented in siginfo(5). PROBLEM: (QAR 62356) (Patch ID: OSF425-405404) ******** This patch fixes a problem in the kernel that caused dynamically loaded PCI/ISA drivers to crash the syttem with the following panic: kernel memory fault The problem would occur only when a device was loaded after it had been previously (and successfully)loaded and unloaded. A sample stack trace for an ISA driver is: 0 boot 1 panic 2 trap 3 _XentMM 4 strcmp 5 get device 6 isa_driver_configure 7 configure_driver ...and the trap: trap: invalid memory read access from kernel mode faulting virtual address: 0xfffffffffffffffe pc of faulting instruction: 0xfffffc00003bdf54 ra contents at time of fault: 0xfffffc00003dbad0 sp contents at time of fault: 0xffffffff881764e0 A sample stack trace for a PCI driver is: 0 boot 1 panic 2 trap 3 _XentMM 4 strcmp 5 get_device 6 pci_driver_configure 7 configure_driver ...and the trap: trap: invalid memory read access from kernel mode faulting virtual address: 0xfffffffffffffffc pc of faulting instruction: 0xfffffc00003af944 ra contents at time of fault: 0xfffffc00003cd4c0 sp contents at time of fault: 0xffffffff821f2870 PROBLEM: (QAR 56793) (Patch ID: OSF425-302) ******** This patch corrects a potential problem in the handling of a ieee_get_state_at_signal(3) C-library call. PROBLEM: (SSRT0537U) (Patch ID: OSF425-306) ******** A potential security vulnerability has been discovered, where under certain circumstances, system integrity may be compromised. This may be in the form of improper file or privilege management. Digital has corrected this potential vulnerability. PROBLEM: (HGOQ40195) (Patch ID: OSF425-319) ******** This patch fixes a system panic caused by a multithreaded process with profiling turned on. The system panics with the following message: "lock_terminate: lock held" An example stack trace is: 5 panic src/kernel/bsd/subr_prf.c : 796 6 lock_terminate src/kernel/kern/lock.c : 544 7 proc_delete src/kernel/bsd/kern_exit.c : 1955 8 task_deallocate src/kernel/kern/task.c : 598 9 waitf src/kernel/bsd/kern_exit.c : 1668 10 wait4 src/kernel/bsd/kern_exit.c : 1456 11 syscall src/kernel/arch/alpha/syscall_trap.c : 615 12 _Xsyscall src/kernel/arch/alpha/locore.s : 1409 PROBLEM: (QAR 61938, QAR 58566) (Patch ID: OSF425-341) ******** This patch fixes a problem in which a recursive panic occurs during certain lockmode violations. The stack trace is listed below: 1 lock_write() 2 handler_id_verify() 3 handler_disable() 4 mchan_disable_interrupts() 5 Mchan_shutdown() 6 drvr_shutdown() PROBLEM: (QAR 58232, QAR 51839) (Patch ID: OSF425-352) ******** This patch fixes a problem with the CPU auto_action console environment variable. If the auto_action console environment variable is set to BOOT or RESTART, when the CPU is to be stopped, the processor immediately boots and the user can not observe that the CPU had halted. PROBLEM: (QAR 51955, QAR 59873) (Patch ID: OSF425-417) ******** This patch fixes a problem that occurs on systems with more than 256 MB of memory in which the write performance of the dumpsys file is very slow. PROBLEM: (TKTR61501) (Patch ID: OSF425-405362) ******** This patch fixes a system panic "rtfree 2". This problem can be encountered on multi-cpu systems and has the following stack trace: boot panic rtfree ip_output tcp_respond tcp_timers tcp_usrreq tcp_slowtimo pfslowtimo pftimeout_thread PROBLEM: (SSRT0536U) (Patch ID: OSF425-282) ******** A potential security vulnerability has been discovered, where under certain circumstances, system integrity may be compromised. This may be in the form of improper file or privilege management. Digital has corrected this potential vulnerability. PROBLEM: (ISO100398, STLB35453) (Patch ID: OSF425-285) ******** A problem in the networking code responsible for allocation of ephemeral port numbers could result in a user allocating port zero if the system variable ipport_userreserved has been set to 65535. This can result in indeterminate results ranging from a system hang to a kernel memory fault panic. PROBLEM: (TKTR61501/QAR 60709) (Patch ID: OSF425-334) ******** This patch fixes two Kernel Memory Faults in Digital Unix Path MTU discovery code. A typical stack trace will look like this: 0 thread_block 1 thread_preempt 2 boot 3 panic 4 rtfree 5 ip_forward 6 gw_forwardscreen 7 ip_forwardscreen 8 ip_dooptions 9 ipintr 10 netisr_thread PROBLEM: (UVO105982/MGO103521/QAR 60902) (Patch ID: OSF425-335) ******** This patch fixes a TCP/IP performance problem in the tcp_reass() function. How to recognize this problem: Profiling the kernel indicates that the tcp_reass() function is consuming all the CPU time. Here is an example using the prof(1) utility sorted in descending order by total time spent in each procedure. Each sample covers 16.00 byte(s) for 4.1e-05% of 547.8574 seconds. %time seconds cum % cum sec procedure (file) 41.8 228.7463 41.8 228.75 tcp_reass () 6.2 33.8050 47.9 262.55 simple_lock () 4.1 22.3743 52.0 284.93 seq_search () 2.9 15.8696 54.9 300.80 pmap_copy_page () 2.2 12.0934 57.1 312.89 nofault_bcopy () 2.1 11.4539 59.2 324.34 simple_unlock () 1.7 9.4755 60.9 333.82 pmap_zero_page () 1.4 7.6839 62.3 341.50 cache_lookup () 1.3 6.8637 63.6 348.37 syscall () 0.8 4.2692 64.4 352.63 hardclock () 0.7 4.0988 65.1 356.73 _XentInt () 0.7 3.6025 65.8 360.34 _OtsMove () 0.6 3.4876 66.4 363.82 malloc () 0.6 3.4701 67.0 367.29 free () 0.6 3.0403 67.6 370.33 tcp_input () PROBLEM: (HPAQ60SQH) (Patch ID: OSF425-345) ******** This patch fixes a problem in which the system can panic with "kernel memory fault". A typical stack trace shows: boot panic trap _XentMM lock_holder socket_send ip_mforward ipintr netisr_thread This patch fixes a problem in which the system can panic with "lock_write: 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 _Xsyscall PROBLEM: (TKTR61501) (Patch ID: OSF425-372) ******** This patch fixes a system panic "rtfree 2". This problem can be encountered on multi-cpu systems and has the following stack trace: boot panic rtfree ip_output tcp_respond tcp_timers tcp_usrreq tcp_slowtimo pfslowtimo pftimeout_thread PROBLEM: (SSRT0559U) (Patch ID: OSF425-389) ******** A potential security vulnerability has been discovered, where under certain circumstances, system integrity may be compromised. This may be in the form of improper file or privilege management. Digital has corrected this potential vulnerability. PROBLEM: (QAR 62611) (Patch ID: OSF425-357) ******** This patch corrects a potential boot panic problem by limiting the size of the bufcache. PROBLEM: (QAR 62831,QAR 62627) (Patch ID: OSF425-367) ******** This patch fixes a virtual memory problem in which an uninitialized pointer in u_dev_protect() causes a kernel memory fault to occur. Here's the stack trace: ---------------------- > 0 boot(0x0, 0x0, 0xfffffc0000777ab0, 0xd, 0x0) ["../../../../src/kernel/arch/alpha/machdep.c":1795, 0xfffffc000045ed5c] 1 panic(s = 0xfffffc0000777ab0 = "kernel memory fault") ["../../../../src/kernel/bsd/subr_prf.c":757, 0xfffffc000041ce84] 2 trap() ["../../../../src/kernel/arch/alpha/trap.c":1243, 0xfffffc000046d934] 3 _XentMM(0x0, 0xfffffc0000366380, 0xfffffc0000888740, 0x0, 0x190) ["../../../../src/kernel/arch/alpha/locore.s":1307, 0xfffffc000045be24] 4 u_dev_protect(0xfffffc000b3a4b40, 0xfffffc0000000000, 0xfffffc0000000001, 0xffffffff00000003, 0xffffffff00000020) ["../../../../src/kernel/vm/u_mape_dev.c":602, 0xfffffc000036637c] 5 u_map_protect(0xfffffc000b3a4b40, 0xfffffc000bf30900, 0x38000, 0x3, 0xffffffff8bd178b8) ["../../ ../../src/kernel/vm/vm_umap.c":1378, 0xfffffc000037a35c] 6 vm_map_protect(0x38000, 0x3, 0xffffffff8bd178b8, 0xffffffff8bd17768, 0xfffffc000037d024) ["../../../../src/kernel/vm/vm_map.c":1295, 0xfffffc000036f3f4] 7 vm_protect(0xffffffff8bd178b8, 0xffffffff8bd17768, 0xfffffc000037d024, 0xfffffc000bf30900, 0xfffffc000040d050) ["../../../../src/kernel/vm/vm_user.c":206, 0xfffffc000037d020] 8 mprotect(0xfffffc000304e210, 0xffffffff8bd17758, 0xffffffff8bd178b8, 0x1, 0x0) ["../../../../src crash-data.1 (61%)/kernel/bsd/kern_mman.c":879, 0xfffffc000040d04c] 9 syscall(0x3ffc0093530, 0x1, 0x1, 0x0, 0x4a) ["../../../../src/kernel/arch/alpha/syscall_trap.c":527, 0xfffffc000046c72c] 10 _Xsyscall(0x8, 0x3ff801588d8, 0x140008120, 0x24000, 0x14000) ["../../../../src/kernel/arch/alpha/locore.s":1094, 0xfffffc000045bc14] End Trace for machine_slot[paniccpu].cpu_panic_thread: PROBLEM: (QAR 59847) (Patch ID: OSF425-347) ******** This patch prevents a kernel malloc leak when changing the protection of a System V shared memory region that uses gh-chunks. PROBLEM: (QAR 61738) (Patch ID: OSF425-329) ******** This patch fixes a problem that caused the system to panic with the string "kernel memory fault". PROBLEM: (QAR 62353, QAR 61253) (Patch ID: OSF425-351) ******** This patch fixes a problem with NFS conversion of a file's vnode number to a file handle number. When a SUN client accessed files on a DIGITAL UNIX server, the file id was truncated improperly during the conversion, generating EOVERFLOW errors. As a result, a NFS client was receiving EOVERFLOW errors. PROBLEM: (QAR 60865) (Patch ID: OSF425-346) ******** The bufpages calculation fails to take granularity hints into account. On systems that pre-allocate large percentages of physical memory to granularity hints, the bufcache calculation allocates an inordinately large amount of physical memory for the buffer cache in relation to the actual memory being used by the operating system. PROBLEM: (QAR 59246, QAR 59884) (Patch ID: OSF425-405426) ******** This patch fixes a problem in which the sysconfig command produces an error when a subsystem name of 15 characters is used. The following error message is displayed: framework error : copying memory to / from kernel PROBLEM: (BCPM70RSB, MGO103953) (Patch ID: OSF425-413) ******** This patch fixes the following problems that occurs on SMP platforms: 1) This patch fixes a problem that occurs on SMP platforms in which a "wired/held/busy page" panic is seen in ssm_anon_free(). A representative stack trace is as follows: panic("ssm_anon_free: wired/held/busy page") src/kernel/bsd/subr_prf.c : 834 ssm_anon_free src/kernel/vm/u_mape_ssm.c : 424 u_ssm_oop_deallocate src/kernel/vm/u_mape_ssm.c : 521 vm_map_entry_delete src/kernel/vm/vm_map.c : 1677 u_map_delete src/kernel/vm/vm_umap.c : 1468 shmdt src/kernel/bsd/svipc_shm.c : 970 syscall src/kernel/arch/alpha/syscall_trap.c : 615 _Xsyscall src/kernel/arch/alpha/locore.s : 1409 2) A system panic with the panic string "pmap_ssm_destroy: wired pages". A representative stack trace is as follows: 5 panic 6 pmap_ssm_destroy 7 u_ssm_oop_deallocate 8 shmctl 9 syscall 10 _Xsyscall PROBLEM: (HPAQ51CP0) (Patch ID: OSF425-411) ******** This patch fixes a problem where a user application may receive an EIO error back from an fsync() call. PROBLEM: (QAR 55421, QAR 55783) (Patch ID: OSF425-365) ******** This patch fixes the following two problems that occur on an NFS file server using a Network Appliance server: o New files may not be listed in directory reads. For example, when the ls command is used not all the files may be listed. o When a directory listing is requested from a Network Appliance server, more data than was requested may be returned and the extra data is lost by the Digital UNIX client. The problem can be seen when using the ls command; not all the files on the server are listed. PROBLEM: (BCPM80CMQ) (Patch ID: OSF425-415) ******** This fixes a kernel memory fault panic in cansignal(). An example stack trace follows: panic() trap() _XentMM() cansignal() sigsend1() sigsend1() sigsendset() syscall() _Xsyscall() PROBLEM: (QAR 60378) (Patch ID: OSF425-298) ******** This patch fixes a problem with memory being wasted by Mach IPC kernel message routines because they were assigned fixed sizes of memory (large or small, depending on the routine). Now, the memory allocation for the IPC routines has been changed to allocate only the memory each routine requires. PROBLEM: (QAR 62959, QAR 62942) (Patch ID: OSF425-386) ******** This patch fixes a problem with user stack pointers not being saved properly in kernel crash dumps for running threads. PROBLEM: (CLD: ISV-06344 QAR: 58600) (Patch ID: OSF425-331) ******** This patch fixes a problem where a network hang can occur because the network isr thread is not running at realtime priority. As a result, some of the realtime deamons or user programs may preempt the netisr thread and hang network activity. PROBLEM: (QAR 57323) (Patch ID: OSF425-287) ******** This patch corrects a problem seen with DECthreads tests that use fork(2). The problem is a race condition in the anonymous memory code that handles COW but releases the anon lock before calling pmap_enter(). PROBLEM: (HPAQ205WQ/QAR 58962) (Patch ID: OSF425-293) ******** This patch prevents a system panic from m_copym(). A privileged program or user that uses raw ip sockets can crash the system by passing an invalid ip header from ip_output(). The stack trace looks like this: panic() m_copym() ip_output() rip_output() raw_usrreq() rip_usrreq() sosend() PROBLEM: (QAR 589554, QAR 56943) (Patch ID: OSF425-261) ******** This patch fixes a problem with the mmmap(), mmrw(), and kernacc() routines, which returned incorrect ENXIO failures when attempting to read high-memory CLUSTER_USAGE_PAL memory. When the failure occurred, the following error message was displayed: errno 6, no such device or address unable to get all of memory PROBLEM: (QAR 59621) (Patch ID: OSF425-364) ******** This patch fixes a problem with the vmstat -P command, which was incorrectly formatting output. PROBLEM: (CLD ISO100435) (Patch ID: OSF425-381) ******** sem_wait() doesn't get interrupted by a SIGCHLD signal if the program is compiled/linked -pthread. PROBLEM: (QAR 59773, QAR 55941, QAR 56416, HPAQ205WK) (Patch ID: OSF425-267) ******** 1) A problem that produced a deadlock between process threads. Typically, the deadlock caused the msfs_getpage routine to wait forever for a lock to be released. Here are examples of stack traces: 0 thread_block() 1 lock_read() 2 msfs_getpage() 3 u_vp_fault() 4 u_map_fault() 5 vm_fault() 6 trap() 7 _XentMM() Stack trace of a thread: 0 thread_block() 1 lock_read() 2 ufs_fsync_int() 3 ufs_fsync() 4 fsync() 5 syscall() 6 _Xsyscall() Stack trace where the thread is servicing a ufs_write request that calls ufs_rwip and requests a page that needs to be faulted in: 0 thread_block() 1 lock_read() 2 u_map_fault() 3 vm_fault() 4 trap() 5 _XentMM() Stack trace of a thread: 0 thread_block() 1 ubc_clean_free() 2 ubc_msync() 3 u_vp_msync() 4 u_map_control() 5 msync() 6 syscall() 7 _Xsyscall() 2) A problem that panics the system with the following error messages: pmap_remove_range: page wired -or- pmap_change_wiring: not valid va PROBLEM: (CLDs BRO101153, BCGM40N88, QAR 59145) (Patch ID: OSF425-398) ******** A flaw in NFS client operation can result in a KMF panic with a stack trace such as: 1 panic(s = 0xfffffc00005d5420 = "kernel memory fault" 2 trap() 3 _XentMM 4 ubc_flush_dirty 5 mntflushbuf 6 nfs_sync 7 sync 8 syscall 9 _Xsyscall PROBLEM: (SQO100495) (Patch ID: OSF425-324) ******** This corrects a simple lock timeout problem in several vm_page routines. PROBLEM: (HPAQ5152N) (Patch ID: OSF425-408) ******** This patch fixes a routing corruption that could been seen as a kernel memory fault or a corruption within the 128 byte kernel memory bucket. An example stack trace is as follows: 10 panic src/kernel/bsd/subr_prf.c : 834 11 afault_trap src/kernel/arch/alpha/trap.c : 2408 12 _XentUna src/kernel/arch/alpha/locore.s : 1767 13 free_trim src/kernel/bsd/kern_malloc.c : 1501 14 free src/kernel/bsd/kern_malloc.c : 1554 15 direct_map_dealloc src/kernel/arch/alpha/hal/dma_direct_map.c : 587 16 dma_map_dealloc src/kernel/io/dec/pci/pcia.c : 4886 17 dma_map_unload src/kernel/io/dec/pci/pcia.c : 4839 18 spo_map_unload_ccb src/kernel/io/cam/spo/simport_dme.c : 1456 19 spo_remove_queue_entry src/kernel/io/cam/spo/simport.c : 2870 20 spo_process_rsp src/kernel/io/cam/spo/simport.c : 3707 21 pzaintr src/kernel/io/cam/spo/sim_pza.c : 1274 22 intr_dispatch_post src/kernel/arch/alpha/hal/shared_intr.c : 247 23 _XentInt src/kernel/arch/alpha/locore.s : 1220 24 vm_page_tester src/kernel/vm/vm_resident.c : 2011 PROBLEM: (QAR 59953, QAR 59419) (Patch ID: OSF425-249) ******** This patch fixes a problem that occurs on AdvFS systems. The system will panic with the following error message: malloc_overflow: guard space corruption A sample stack trace is as follows: 6 panic() 7 malloc_debug() 8 free() 9 _ms_free() 10 free_dmntbl_setname() 11 msfs_real_syscall() 12 msfs_syscall() 13 syscall() 14 _Xsyscall() PROBLEM: (QAR 61224) (Patch ID: OSF425-296) ******** This patch fixes a problem with AdvFS, which produced the following error while attempting to migrate a sparse file: E_CANT_MIGRATE_HOLE The AdvFS migration code can now migrate a hole to the volume that contains the first real extent following the hole. PROBLEM: (QAR 60888, QAR 61768, QAR 58064) (Patch ID: OSF425-320) ******** This patch fixes the following problems in the AdvFS system: o The log file corruption caused panics during recovery and failures and display one of the following messages: ftx_fail: lgr_read failure -or- ftx_fail: dirty page not allowed Sample stack trace is listed below: 28 panic() 29 advfs_sad() 30 ftx_fail_2() 31 ftx_fail() 32 fs_create_file() 6 advfs_sad() 7 _ms_free() 8 ftx_fail_2() 9 ftx_recovery_pass() o kernel memory fault Sample stack trace is listed below: 0 boot() 1 panic() 2 trap() 3 _XentMM() 4 add_cache() 5 load_x_cache() 6 sbm_find_space() 7 alloc_from_bitmap() 8 alloc_from_one_disk() 9 stg_alloc_from_one_disk() 10 stg_alloc_from_svc_class() 11 alloc_append_stg() 12 alloc_stg() 13 add_stg() 14 stg_add_stg_no_cow() 15 stg_add_stg() 16 rbf_add_overlapping_stg() 17 fs_write_add_stg() 18 fs_write() 19 msfs_write() 20 vn_write() 21 rwuio() 22 write() 23 syscall() 24 _Xsyscall() o The error message: "can't set a bit twice". Sample stack trace is listed below: 0 panic("alloc_bits_page: can't set a bit twice!") 1 advfs_sad() 2 CANT_SET_TWICE() 3 sbm_set_pg_bits() 4 init_sbm() o The error message: "can't clear a bit twice". Sample stack trace is listed below: 0 panic(ADVFS INTERNAL ERROR: dealloc_bits_page: can't clear a bit twice!\n") 1 advfs_sad() 2 CANT_CLEAR_TWICE() 3 dealloc_bits_page() PROBLEM: (QAR 60725) (Patch ID: OSF425-360) ******** This patch fixes a problem in the AdvFS logging code. The way locking was implemented was causing degraded performance. PROBLEM: (BCSM51Q5C) (Patch ID: OSF425-418) ******** This patch corrects an I/O subsystem performance bottleneck. A system which experiences periodic system slowdowns may need this patch. PROBLEM: (UVO106018, QAR 61185) (Patch ID: OSF425-362) ******** This patch fixes a operating system hang condition. The hang condition exists due to processes deadlocking in the Advfs code. PROBLEM: (QAR 61441) (Patch ID: OSF425-410) ******** This patch fixes a problem with AdvFS performance. The patch provides a performance improvement to the msync system call when it is called for an AdvFS mmapped file. AdvFS msync processing is changed to only flush file dirty pages in the mmapped address range passed to the msync system call. Prior to this change, advFS would flush all dirty pages for the file. PROBLEM: (QAR 61665) (Patch ID: OSF425-405328) ******** This patch corrects a small accounting problem where the measured time for a process was an integral rather than mean value. The calculation was changed to reflect this discrepancy. This change also had to be reflected in the acctcom and acctcms commands. PROBLEM: (QAR 62531) (Patch ID: OSF425-368) ******** This patch fixes a virtual memory problem that may cause a system to panic with one of the following messages: "pmap_begin_mutex_region timeout" or "simple_lock timeout". PROBLEM: (QAR 59926) (Patch ID: OSF425-336) ******** This patch removes extraneous debug code. PROBLEM: (QAR 62045) (Patch ID: OSF425-337) ******** This patch fixes a problem in which the system can panic with the message "kernel memory fault". The stack trace is as follows: 5 panic src/kernel/bsd/subr_prf.c : 753 6 trap src/kernel/arch/alpha/trap.c : 1539 7 _XentMM src/kernel/arch/alpha/locore.s : 1424 8 pmap_seg_tbsync src/kernel/arch/alpha/pmap.c : 4996 9 pmap_clear_reference src/kernel/arch/alpha/pmap.c : 3873 10 ubc_page_stealer src/kernel/vfs/vfs_ubc.c : 1681 11 vm_pageout_loop src/kernel/vm/vm_pagelru.c : 680 12 vm_pageout src/kernel/vm/vm_pagelru.c : 1265 PROBLEM: ( CLD BCPM51QFJ, QAR 63009 ) (Patch ID: OSF425-379) ******** This patch resolves systems from hanging during boot. Disabling CRD interrupts during boot caused PAL to NOT deliver the interrupt to the OS and therefore NOT clear the error, so a infinite recursion interrupt hang results. PROBLEM: (QAR 63897, QAR 63678) (Patch ID: OSF425-405459) ******** This patch fixes a problem with the memory file system (mfs) that caused systems to hang when they attempted to dynamically allocate a cdfs file system. The problem first seemed to be an issue with systems that had been update installed. PROBLEM: (EW9B92660) (Patch ID: OSF425-405491) ******** This patch fixes a route problem when you apply different subnet masks to the same Internet Class network address. PROBLEM: (CLDs HPAQ200SX, MCPM415SF, HPAQ914NT QAR 45528) (Patch ID: OSF425-405579) ******** This patch corrects an NFS client problem where a KMF panic can result from incorrect locking. A typical stack trace would be: 0 boot() ["../../../../src/kernel/arch/alpha/machdep.c":1889 1 panic(s = 0xfffffc00005fcf68 = "kernel memory fault") 2 trap 3 _XentMM 4 atomic_decl 5 clntktcp_freesock 6 clfree 7 rfscall 8 rfs3call 9 nfs3_getattr_otw 10 nfs3getattr 11 nfs3_getattr . . . PROBLEM: (CLDs BCGM40VQ6, MGO104026, QAR 51061) (Patch ID: OSF425-405590) ******** This patch fixes a problem where an NFS client process may hang in the uninterruptable state. Specifically, compilation builds may hang during the ld phase (linking). PROBLEM: (GOZ100546, GOZ100949, QAR 51038) (Patch ID: OSF425-409) ******** This patch fixes a problem where NFS does not update mtime and atime for special files and named pipes. PROBLEM: (QAR 63229, QAR 63836) (Patch ID: OSF425-424) ******** This patch fixes a situation in which an NFS server system experiences system hang and a "malloc_mem_alloc: no space in map" message is written to the console. The problem is that when the NFS server receives a duplicate request for an operation that is in progress, a memory leak causes the system to hang. PROBLEM: (QAR 62832) (Patch ID: OSF425-425) ******** This patch is a re-fix of the NFS loopoback mounted file system hang problem that was fixed two years ago. The tunable parameter ubc_nfsloopback has been removed and the code restructured to eliminate any problems with NFS loopback mounted file systems as well as increase NFS performance. This patch also fixes performance and hang/panic problems with the UBC when filling the UBC with a small number of large files. The panic problems usually look like simple lock timeouts which results from a task waiting on the UBC LRU lock while ubc_page_alloc() excessively scans the LRU list for a usable page. PROBLEM: (QAR 63741, BCSM80FG6) (Patch ID: OSF425-441) ******** This patch fixes a problem where a file system is busy when trying to unmount it. PROBLEM: (QAR 62917 62920 57926 64226) (Patch ID: OSF425-448) ******** This patch fixes the problem where in the dump of a forced crash, the trace of the thread that was active at the time of the crash contains incorrect information. The emulator produces incorrect results for the PERR and the literal versions of some of the MAX/MIN instructions in the MVI extension. PROBLEM: (QAR 59329) (Patch ID: OSF425-455) ******** This patch fixes a problem in which the fork() system call failed to save the floating point state in forking multithreaded programs. The new behavior saves the floating point state to the pcb and then calls copyout() to copy it to the forking thread's out-of-line state. PROBLEM: (CLD HPAQ8177M, QAR 63556) (Patch ID: OSF425-463) ******** This patch fixes a problem in which the msleep() syscall was not marked as a cancellation point. If a process was waiting for an msem_lock, and a signal was delivered to that process, the process would not be interrupted. This problem occurred only if your C programs were complied using the -pthread switch. PROBLEM: (Patch ID: OSF425-465) ******** This patch provides functionality to allow the detection of unlinked referenced files. A deleted file occupies filesystem space until the last reference to the file is closed. This patch enhances the fuser utility to identify the process responsible for holding a reference on an unlinked file so that the filesystem space occupied by the deleted file can be reclaimed. PROBLEM: (BCPM9124T, QAR 65217) (Patch ID: OSF425-467) ******** This patch fixes a problem that can cause an NFS client application to hang, or causes a "lock already owned by thread" panic when lockmode=4. The problem occurs when the application tries to rename a sub-directory to its parent. A stack trace of a hung NFS client application, or the panicing process, may look like: 0 thread_block() 1 lock_write() 0 thread_block() 1 lock_write() 2 nfs3_rename() 3 rename() 4 syscall() 5 _Xsyscall() PROBLEM: (QAR 65598) (Patch ID: OSF425-469) ******** This patch fixes a problem in which the kernel misses profiling samples for multithreaded applications that are implemented to use system contention scope (SCS) threads. PROBLEM: (MGO103843,MGO103768) (Patch ID: OSF425-475) ******** This patch corrects performance related problems. A system running low on free memory or showing heavy pagein activity will need this patch. PROBLEM: (QAR 63936, QAR 65766, QAR 65767) (Patch ID: OSF425-476) ******** This patch fixes several problems in the kernel. 1) A panic with the message vm_unwire: page is not wired 2) A panic with the message kernel_object_bad: bad operation 3) A system hang due to deadlock between the swapin thread and ps both accessing the same task. PROBLEM: (MCGM305SB, QAR 65113) (Patch ID: OSF425-486) ******** This patch fixes a problem where init hangs due to multiple downgrades of a write lock. PROBLEM: (MGO103843,MGO103768) (Patch ID: OSF425-488) ******** This patch corrects performance related problems. A system running low on free memory will need this patch. PROBLEM: (QAR 65232, BCSMA1H45) (Patch ID: OSF425-490) ******** This patch fixes a panic which has the following error message: tb_shoot ack timeout This panic seems to occur only on multi-processor 4100 machines. PROBLEM: (QAR 54441,QAR 60576) (Patch ID: OSF425-491) ******** This patch fixes a problem in which a kernel client rpc has a socket leak when an error is encountered and binding fails. The problem may manifest itself if there is heavy traffic over a transport such as NFS. PROBLEM: (QAR 65396 58440 58800) (Patch ID: OSF425-494) ******** The output from the "vmstat -M" command does not correctly match the bucket numbers with the bucket indices. PROBLEM: (QAR 65519, QAR 64231, QAR 63229, QAR 64738, QAR 64995, UVO106095, TKTR92349) (Patch ID: OSF425-497) ******** This patch fixes a problem in NFS. NFS was experiencing a hang because the NFS server had a memory leak. PROBLEM: (QAR 66499) (Patch ID: OSF425-505) ******** This patch fixes a system hang. The system hang is a result of an infinite loop when out-of-band networking data is followed by any number of bytes and a process is doing a MESSAGE PEEK with a user buffer larger than the number of out-of-band bytes. PROBLEM: (QAR 66747) (Patch ID: OSF425-506) ******** A potential security vulnerability has been discovered, where under certain circumstances system integrity may be compromised. This may be in the form of improper file or privilege management. Compaq has corrected this potential vulnerability. PROBLEM: (QAR 67897, QAR 64723, CLD BCSM91ZZJ) (Patch ID: OSF425-518) ******** This patch fixes a problem where processes hang due to flow control being turned off to a device (ie. printer). When this happens processes block indefinitely in the lock_read() call. PROBLEM: (QAR 68123, QAR 67795) (Patch ID: OSF425-521) ******** This patch fixes a problem where the system crashes with the following error message: lw_remove: light weight wiring(s) found PROBLEM: (BCGM20L71) (Patch ID: OSF425-541) ******** This patch fixes a dealock that can occur when a thread is in sigwaitprim(), and a second signal in the sigwait set is being delievered. An example stack from of the sigwait thread is: simple_lock_time_violation() mpsleep() sigwaitprim() syscall() _Xsyscall() And the delievering threads stack would be: psignal_internal() kill() syscall() _Xsyscall() PROBLEM: (CLD USG-08108) (Patch ID: OSF425-546) ******** This patch fixes a problem which revealed a problem in the subsystem configuration bootstrap process. Under some circumstances a status field might not get initialized correctly and cause entries in /etc/sysconfigtab to be ignored and not set correctly. PROBLEM: (BRO101307 & BCSM11QV2) (Patch ID: OSF425-549) ******** 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: (CLD UVO106265 QAR 67541) (Patch ID: OSF425-551) ******** This corrects a "simple_lock: time limit exceeded" panic. An example of a partial stack trace showing the relevant enties: panic() simple_lock_fault() simple_lock_time_violation() . . . softclock_scan() hardclock() _XentInt() . . . syscall() _Xsyscall() PROBLEM: (FNO100208) (Patch ID: OSF425-552) ******** This patch fixes a problem with poor performance of NFS/UDP over a GigaBit Ethernet network interface (DEGPA). It allows client side RPC freeing of client handles with busy buffers. PROBLEM: (QAR 68542) (Patch ID: OSF425-557) ******** This patch fixes a panic which has the following error message: simple_lock: time limit exceeded A sample stack traces are listed below: 0 thread_block 1 voliod_loop 2 volkiostart 3 volstrategy 4 spec_strategy 5 call_disk 6 bs_startio 7 bs_q_blocking 8 bs_q_list 9 logflush_cont 10 bs_logflush_start 11 lgr_flush_start 12 msfs_mntflushbuf 13 mntflushbuf 14 boot 15 panic 16 simple_lock_fault 17 simple_lock_time_violation 18 pmap_dup 19 vm_dup_va 20 volkiomem_iter 21 volkiocopyout 22 volsio_unstabilize 23 vol_mv_wrback_done 24 voliod_iohandle 25 voliod_loop 0 boot 1 panic 2 event_timeout 3 pmap_begin_mutex_region_wait1 4 pmap_remove_all 5 pmap_page_protect 6 k_mem_free_anon 7 k_mem_unmap 8 k_map_delete 9 kmem_stack_free 10 stack_free 11 thread_deallocate 12 reaper_thread 0 stop_secondary_cpu 1 panic 2 cpu_ip_intr 3 _XentInt 4 lwc_schedule 5 stop_secondary_cpu 6 panic 7 event_timeout 8 xcpu_puts 9 printf 10 simple_lock_fault 11 simple_lock_time_violation 12 pmap_clear_reference 13 vm_page_deactivate 14 vm_pagelru_approximation 15 vm_pageout PROBLEM: (SSRT0583Q) (Patch ID: OSF425-558) ******** A potential security vulnerability has been discovered, where under certain circumstances, system integrity may be compromised. This may be in the form of improper file or privilege management. Compaq has corrected this potential vulnerability. PROBLEM: (BCSMC0476) (Patch ID: OSF425-560) ******** This patch fixes a problem where resets are seen due to proxy packets getting into the ipintrcacheaddr cache. PROBLEM: (67968) (Patch ID: OSF425-565) ******** This patch is for AOL systems running Inktomi code. It provides enabling hooks for Inktomi caching server code. PROBLEM: (CLD ALC-08248, QAR 69130) (Patch ID: OSF425-567) ******** This patch fixes resolves a performance problem associated with page coloring for real time applications (rt_preempt_opt=1). There is a new tuneable, "vm_page_color_private", which is modified in the "vm" section of the sysconfigtab file. The default value for this variable is "0", so to enable this feature the variable must be set to "1". PROBLEM: (QARS 64229 64563) (Patch ID: OSF425-569) ******** This patch fixes a rare problem in the NFS subsystem in which a "kernel memory fault" panic will be seen originating from the free() routine either when the NFS server daemon (nfsd) is processing a request or is shut down. The stack trace of the panicing process is as follows: 1 panic("kernel memory fault") 2 trap() 3 _XentMM() 4 free() 5 rfsfreexprt() 6 nfs_svc() 7 nfssvc() 8 syscall() 9 _Xsyscall() PROBLEM: (BRO101278) (Patch ID: OSF425-577) ******** This is to correct a problem where a signal is delievered, but not responded to by the target process. PROBLEM: (BCPMC1GPQ) (Patch ID: OSF425-578) ******** This is to fix a panic of "get_color_bucket: empty buckets" when the sysconfig attribute "private-cache-percent" is non-zero. PROBLEM: (EALC9003) (Patch ID: OSF425-585) ******** This patch enhances the behavior of the mlockall() system call. mlockall() will now make a process unswappable. PROBLEM: (CLD HPAQA024N, CLD BCSM21XNM, QAR 65702, QAR 58547, QAR 64794, QAR 60919) (Patch ID: OSF425-594) ******** This patch fixes a problem in which a system may panic with the following panic string "lock_pvh timeout". Representative stacktraces are shown below: Stacktrace 1: panic("lock_pvh timeout") src/kernel/bsd/subr_prf.c":796 lock_pvh_wait() src/kernel/arch/alpha/atomic_ops.s":698 pmap_zero_page() src/kernel/arch/alpha/pmap.c":4417 vm_page_zeroer() src/kernel/vm/vm_resident.c":1982 idle_thread() src/kernel/kern/sched_prim.c":3467 Stacktrace 2: panic("lock_pvh timeout") src/kernel/bsd/subr_prf.c":796 lock_pvh_wait src/kernel/arch/alpha/atomic_ops.s : 698 pmap_zero_page src/kernel/arch/alpha/pmap.c : 4417 vm_zeroed_pg_alloc src/kernel/vm/vm_resident.c : 1374 vm_anon_page_alloc src/kernel/vm/vm_anonpage.c : 129 anon_pagezero_alloc src/kernel/vm/vm_anon.c : 462 u_anon_faultpage src/kernel/vm/u_mape_anon.c : 1087 u_anon_fault src/kernel/vm/u_mape_anon.c : 980 u_anon_lockop src/kernel/vm/u_mape_anon.c : 2184 u_map_lockvas src/kernel/vm/vm_umap.c : 1324 c_map_wire src/kernel/vm/vm_cmap.c : 145 vm_map_pageable_orig src/kernel/vm/vm_map.c : 1549 vm_map_pageable src/kernel/vm/vm_map.c : 1521 task_threads src/kernel/kern/task.c : 1112 _Xtask_threads mach/mach_server.c : 292 mach_server mach/mach_server.c : 6451 mach_msg src/kernel/kern/ipc_basics.c : 442 msg_rpc_trap src/kernel/kern/ipc_basics.c : 1437 _Xsyscall src/kernel/arch/alpha/locore.s : 1582 PROBLEM: (QAR 65580) (Patch ID: OSF425-595) ******** This patch fixes a prior regression that prevented full crash dumps from working properly. PROBLEM: (none.) (Patch ID: OSF425-601) ******** If a 3rd-party device driver is installed and after a kernel build, one of the following errors is emitted: loading vmunix.sys undefined: dma_get_num_val_sgentrys loading vmunix.sys undefined: dma_get_sgentry_reset() loading vmunix.sys undefined: dma_get_num_val_sgentrys dma_get_sgentry_reset() Then the driver was built on a V4.0F or later release, and this patch will provide the necessary (DMA) functions for a successful kernel build. PROBLEM: (QAR 60416) (Patch ID: OSF425-240) ******** This patch fixes a problem in mountd where lines in the /etc/exports file could be no longer than 1023 characters. With this patch, a trailing backslash character in the /etc/exports file allows continuations beyond 1023 characters. PROBLEM: (QAR 65033, QAR 61856, QAR 64040, SSRT0563U) (Patch ID: OSF425-405500) ******** This patch fixes a problem in mountd. The NFS server allows read/write access to clients not on the exports list and other clients to be incorrectly denied access. PROBLEM: (QAR 62614) (Patch ID: OSF425-447) ******** This patch fixes a problem with the mount command where it sometimes kills other processes. This randomly occurs if the file where mountd stores its pid, /var/run/mountd.pid, is out-of-date. PROBLEM: (QAR 54840, QAR 60476, QAR 58938) (Patch ID: OSF425-547) ******** This patch fixes a problem in AdvFS where a complex lock in the ddl_wait_for_active_entry() routine would cause the thread to hang and possibly blocking other threads. If the system is set with lockmode = 4, a system panic would occur. PROBLEM: (Patch ID: OSF425-166) ******** This patch provides a bugfix to avoid a panic that might result when running a mixed filesystem behind the HSZ70 Raid controller on the KZPSA-BB Fast10 Wide Differential adapter in cluster environments under DIGITAL UNIX V4.0D, in conjunction with Version A11 KZPSA firmware or greater. PROBLEM: (QAR 52608) (Patch ID: OSF425-400458) ******** This patch fixes a problem that occurs on AlphaServer 4100 systems. If no devices are attached to the KZPSA disk controller, the system may panic when attempting to perform I/O. This patch provides a workaround to the problem by suppressing the sending of the "verify-adapter-sanity" command until a device has been attached to the disk controller. PROBLEM: (Patch ID: OSF425-185) ******** This patch provides a set of workarounds for Qlogic firmware bugs. These bugs were encountered when using the HSZ70 Raid Array Controller on the KZPBA-CB wide differential UltraSCSI adapter in a dual-node cluster environment. o Better handle sensitive error recovery sequences during HSZ70 controller failover o Handles Command Error (a mailbox error code 0x4005) without resorting to chip reinit/bus reset. o Additional workarounds for version 5.53 target-mode firmware bugs. Complete support for cluster environments also requires that the Qlogic adapter firmware version and HSZ70 Raid Array controller firmware version is at least at the level as documented in the HSZ70 Raid Controller Platform Kit. All modifications included in this patch are compatible with existing versions of Qlogic firmware. PROBLEM: (QAR 58007,59236) (Patch ID: OSF425-198) ******** This patch fixes a panic with the following error message: trap: invalid memory write access from kernel mode A sample stack trace is as follows: 1 panic() 2 trap() 3 _XentMM() 4 enqueue_tail() 5 ccmn_send_ccb3() 6 cdisk_send_ccb() 7 cdisk_strategy() 8 hwc_iomap_strategy() 9 spec_strategy() 10 call_disk() 11 bs_startio() 12 bs_q_blocking() 13 bs_q_list() 14 logflush_cont() PROBLEM: (QAR 59059) (Patch ID: OSF425-216) ******** This patch fixes a problem that occurs when KZPSA and KZTSA hardware resources needed to do I/O are unavailable causing a large number of events to be logged. The system can become sluggish and sometimes crash. This problem is seen on 8400 and 4100 systems with limited hardware scatter-gather memory resources. PROBLEM: (QAR 47111 QAR 58034 QAR 60575) (Patch ID: OSF425-318) ******** The first problem occurs when a failed (hardware or driver failure) KZPSA adapter panics the kernel. You will observe this problem when the failed adapter generates a miscellaneous error continuously, eventually causing a kernel panic with messages similar to the following: KZPSA adapter misc error, asr=0x4, afar=0x4a03f158, afpr=0x20311 pzaintr: KZPSA adapter misc error, asr=0x4, afar=0x4a03f158, afpr=0x20311 This patch causes the system to check for a failed device before allocating dma resources, preventing the panic. The second problem is that the SIMPORT code returns I/O with a CAM status of "NO HBA" when a miscellaneous adapter error occurs. This CAM status is incorrect since the adapter is re-initialized. The correct CAM status for such as condition is "CAM BUSY". The "NO HBA" status is only returned when the adapter can not recover from the error (The re-initialization failed). PROBLEM: (QAR 62104) (Patch ID: OSF425-397) ******** This patch corrects a problem that can result in a kernel memory fault during heavy SCSI I/O, particularly on a small-memory system. The crash dump stack may look similar to the following: 0 boot src/kernel/arch/alpha/machdep.c : 2294 1 panic src/kernel/bsd/subr_prf.c : 1225 2 trap src/kernel/arch/alpha/trap.c : 1824 3 _XentMM src/kernel/arch/alpha/locore.s : 2074 4 malloc_internal src/kernel/bsd/kern_malloc.c : 1452 5 malloc src/kernel/bsd/kern_malloc.c : 1235 6 pmap_create src/kernel/arch/alpha/pmap.c : 2107 7 vm_map_fork src/kernel/vm/vm_map.c : 2510 8 task_create src/kernel/kern/task.c : 545 9 procdup src/kernel/vm/vm_unix.c : 764 10 newproc src/kernel/bsd/kern_fork.c : 812 11 fork1 src/kernel/bsd/kern_fork.c : 642 12 fork src/kernel/bsd/kern_fork.c : 567 13 syscall src/kernel/arch/alpha/syscall_trap.c : 670 14 _Xsyscall src/kernel/arch/alpha/locore.s : 1779 PROBLEM: (QAR 58916 QAR 59120 QAR 59123 QAR 60351) (Patch ID: OSF425-378) (QAR 60785 QAR 60892 QAR 61364 QAR 61715) (Patch ID: OSF425-378) (QAR 62206 QAR 62635) (Patch ID: OSF425-378) ******** This patch fixes the following problems that may occur when using QLogic adapters: o Fixes "simple_lock: time limit exceeded" panics. o Fixes a problem in which adapter errors are reported as disk errors. o Fixes a problem in which a processor may appear to hang for long periods of time when doing large, non-aligned, non-block, multiple o Fixes a problem in which random memory corruption problems may occur when a device error is encountered and the device does not have an entry in the DDR database. PROBLEM: (QAR 56716, QAR 64562) (Patch ID: OSF425-474) ******** This patch fixes a panic that occurs when KZPSA resources aren't available to re-enable a channel or a device after a bus reset. The panic string is listed below: panic("(spo_process_rsp) ran out of memory!") PROBLEM: (QAR 65242, QAR 65075, MGO103822) (Patch ID: OSF425-477) ******** This patch fixes a panic which has the following error message: lw_remove: light weight wiring(s) found PROBLEM: (CLD MGO103853, CLD MGO103295, CLD MGO103959) (Patch ID: OSF425-522) ******** This patch fixes a kmf problem when the type of SCSI device dynamically changes. A typical stack trace: panic trap _XentMM malloc(size = 64) falloc accept1 oaccept syscall _Xsyscall PROBLEM: (QAR 69128, QAR 68747) (Patch ID: OSF425-563) ******** The patch fixes a panic when booting with TCR 1.5 software. When system tries to initialize the ASE Availability Manager during boot, it gets a kernel memory fault. PROBLEM: (None) (Patch ID: OSF425-579) ******** This patch provides the DEGPA-SA Gigabit Ethernet support. PROBLEM: (BCGMC1JRS) (Patch ID: OSF425-588) ******** 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 occured on Dataless Management Services (DMS) client systems. To correct this problem, this patch must be installed on the DMS clients. It does not need to be installed on the DMS server. PROBLEM: (CLD HPAQC08NV) (Patch ID: OSF425-592) ******** If a customer has multiple "A" records in his DNS database for an NFS client of a Digital UNIX NFS server, the order in which the records are returned determines whether an NFS mount will succeed or get "Permission denied". PROBLEM: (ISO100472) (Patch ID: OSF425-517) ******** This fixes a panic with the following panic string: "pgmv: session leader attempted setpgrp" PROBLEM: ( QAR 69251) (Patch ID: OSF425-582) ******** With version 52, Ladebug has begun to employ a "user thread hold" mechanism. This patch fixes problems in DECthreads, when using this mechanism, which might result in missed breakpoints and watchpoints, as well as causing application hangs. PROBLEM: ( CLD HPAQ21HQ9) (Patch ID: OSF425-582) ******** This patch fixes a DECthreads problem in which an invalid scheduling priority bugcheck in encountered. This is caused by incorrect referencing of scheduling data structures inside DECthreads. PROBLEM: ( QAR 69364) (Patch ID: OSF425-582) ******** This patch fixes a problem in DECthreads manager thread logic. The manager thread is being scheduled to run in response to a system event (nxm action, timer queue expiration, etc.) but is not recognizing the event as the reason it was scheduled to run. The manager thread then goes back to sleep, only to wake up again in response to the still unserviced system event. An infinite loop results. PROBLEM: (HPAQ41J00, QAR 64037) (Patch ID: OSF425-410219) ******** This patch fixes a problem where a system panic will occur when accessing an ISO9660 format CDROM when the CDROM was mounted using the command: mount -r -t cdfs -o noversion /dev/rz4c /cdrom The panic string is "Unaligned kernel space access from kernel mode". A typical stack trace of the crash is: 6 panic(s = "Unaligned kernel space access from kernel mode") 7 afault_trap 8 _XentUna 9 cdfs_isodir_to_idir 10 cdfs_readisodir_int 11 cdfs_readisodir 12 cdnodeget 13 cdfs_lookup 14 namei 15 stat1 16 stat 17 syscall 18 _Xsyscall PROBLEM (QAR 64688) (Patch ID: OSF425-537) This patch fixes kernel memory fault system panic in routine spec_relcaim. A sample stack trace is as follows: 0 stop_secondary_cpu() 1 panic() 2 event_timeout() 3 xcpu_puts() 4 printf() 5 panic() 6 trap() 7 _XentMM() 8 spec_reclaim() 9 vgone() PROBLEM (QAR 66544) (Patch ID: OSF425-537) This patch fixes a problem with executing the "file" command against a lat (BSD) special device in which the "file" process will hang. The system needs to be rebooted in order to remove the hung process. PROBLEM (QAR 67757) (Patch ID: OSF425-537) This patch fixes a problem on multiCPU systems where hangs can occur in the revoke system call when multiple threads attempt to call "revoke" at the same time. A sample stack trace is as follows: 0 thread_block() 1 clearalias() 2 revoke() 3 syscall() 4 _Xsyscall() PROBLEM: (HPAQC032X/QAR 66952) (Patch ID: OSF425-556) ******** This patch fixes an kernel memory fault caused by a streams SMP race condition. This kernel memory fault will have stack traces that may include STREAMS components or kmembucket corruption. PROBLEM: (BCGM703PQ,BCPM70WFJ,HPAQ920JJ,BCGMC0NZ8,HPAQA225S,BCGM210JL, HPAQ20Z8V) (Patch ID: OSF425-586) ******** This patch fixes a problem where several processes accessing the same AdvFS file can hang with the following stack trace: thread_block ubc_lookup page_lookup bs_refpg_int bs_refpg fs_read msfs_read vn_read rwuio read syscall _Xsyscall PROBLEM: (None) (Patch ID: OSF425-667) ******** This patch provides support for the DAPCA HE622 and the DAPBA HE155 ATM adapters. PROBLEM: (DEKB20145, UTO101928) (Patch ID: OSF425-611) ******** This patch fixes a kernel memory fault and an SMP race condition with the AltaVista Firewall 98 server on a multi-cpu system. The stack trace will contain: _XentMM ip_outputscreen screen_getnext screen_control PROBLEM: (JHB100062/QAR 69563) (Patch ID: OSF425-612) ******** This patch fixes a problem when a default IP address and a cluster virtual IP address get interchanged after a network restart. The default interface address is used by all outgoing traffic and the alias address is only usable for the incoming packets. PROBLEM: (QAR 46648 QAR 70765) (Patch ID: OSF425-619) ******** This patch fixes a system hang in which there is a large number of pending ioctl's on the streams queue. PROBLEM: (BCGM31BPT) (Patch ID: OSF425-621) ******** This patch fixes a problem on systems running screend where TCP/IP fragments are being dropped. PROBLEM: (CLD MGO104106, CLD HPAQ40QCM) (Patch ID: OSF425-633) ******** Typical stack trace for the assert panic is: panic assert_wait_mesg xpt_ccb_alloc htm_immed_async isp_process_response_queue For the blocked thread, there will be at least one thread waiting forever with a stack trace of: thread_block mpsleep isp_enable_lun htm_enable_lun handle_immediate sim_action xpt_sim_func xpt_action tmv2_complete_disable tmv2_accept_cbf xpt_callback_thread PROBLEM: (CLD BCSM30WLD ,QARS 69170 70101) (Patch ID: OSF425-636) ******** 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: (QAR 63408, QAR 66263) (Patch ID: OSF425-653) ******** This patch fixes a problem with DLPI. It is not possible to configure dlpi's maximum link parameters. Therefore max_links and max_macs parameters have been made configurable using sysconfig. PROBLEM: (BCGM40GGH, 71213) (Patch ID: OSF425-656) ******** 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 70269, 70640) (Patch ID: OSF425-658) ******** This patch fixes a restart detection problem with the proplistd daemon. Prior to this fix, when mounting a relocated ASE NFS service with property lists, clients did not detect that the proplistd RPC port number had changed. Clients continued to use the proplistd RPC port number of the old ASE cluster member. PROBLEM: (QAR 66356) (Patch ID: OSF425-661) ******** 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: OSF425-665) ******** This patch fixes a problem that causes the update install procedure to exit with core dumps and /sbin/loader failures on a system. PROBLEM: (QAR 71062, QAR 71532) (Patch ID: OSF425-666) ******** This patch fixes a problem with CDFS. Data corruption occurs when reading beyond the end of a partition. PROBLEM: (QAR 68625) (Patch ID: OSF425-670) ******** UFS file systems being checked by fsck may have conditions that cause a dirscan() to end in a segmentation fault. This patch adds a check to dirscan() that will return STOP if this condition exists.This return will be detected by fsck and the user will be queried for action to be taken. PROBLEM: (CLD BCPM50LZC) (Patch ID: OSF425-673) ******** 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: (HPAQ50FLC, QAR 71826, QAR 71891, QAR 68458) (Patch ID: ) ******** This patch fixes a panic in the kernel. The panic has the following error message: simple_lock: time limit exceeded The sample stack trace is as follows: panic simple_lock_fault simple_lock_time_violation pmap_ssm_enter u_ssm_fault u_map_fault vm_fault ... PROBLEM: (HPAQ40343, HPAQ5062G, UVO20042) (Patch ID: OSF425-679) ******** 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). Refer to the "Patch Summary and Release Notes" document for further information on the I/O Throttling/ Smooth Sync Patch. PROBLEM: (QAR 65643) (Patch ID: OSF425-690) ******** This patch improves UFS performance by no longer prematurely writing single pages. PROBLEM: (BRO101338 BRO101359) (Patch ID: OSF425-691) ******** This patch fixes system crashes seen on ASE or Cluster systems when changing the network interfaces. The stack is not informative and the panic may be "trap: illegal instruction," or "kernel memory fault." PROBLEM: (BCGM50N91) (Patch ID: OSF425-699) ******** 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 64443, QAR 64472, QAR 64473, QAR 67374) (Patch ID: OSF425-702) ******** This patch fixes and enhances the quotacheck and fsck commands. 1) Add a -t option on quotacheck so that either AdvFS or UFS type devices may be selected for -a processing. 2) fsck and quotacheck will no longer try to attempt parallel processing of partitions on the same device or filesets in the same domain. 3) unique pass numbers are now being processed in numerical order during separate passes. This applies to both fsck and quotacheck 4) If an explicit AdvFS fileset is specified (without -a option) now always perform the quota check even if there is no /etc/fstab entry with quotauser and/or quotagroup specified. 5) Skip any file systems which are not currently mounted on their mount points. 6) Skip any /etc/fstab specified file system which are not mounted on their specified mount point. 7) A quotacheck command line can not have more than 64 arguments, if it does an error will be generated. Refer to the "Patch Summary and Release Notes" document for updates to the quotacheck(8), fsck(8), and fstab(4) man pages. PROBLEM: (QAR 72971 CLD MGO104088) (Patch ID: OSF425-706) ******** 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, CLD HPAQ500L1) (Patch ID: OSF425-712) ******** 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: (BCGM300N2) (Patch ID: OSF425-717) ******** This patch disables the printing of the error message: contig_malloc: failed to allocate memory within addrlimit This was only printed during bootup within a very large memory configuration, when using the genvmunix kernel. PROBLEM: (QAR 63384) (Patch ID: OSF425-723) ******** 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: () (Patch ID: OSF425-730) ******** This patch provides the driver and related kernel support for the Powerstorm 4D10T (ELSA Gloria Synergy) graphics card (SN-PBXGK-BB). PROBLEM: (STLB42227) (Patch ID: OSF425-731) ******** 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: (QAR 65319 QAR 64835 QAR 64830) (Patch ID: OSF425-617) ******** This patch removes the restriction of the maximum number of threads allowed system-wide. The variable 'maxuthreads' provides a per uid thread limit and this is adequate for ensuring that users cannot create an unreasonable number of threads. PROBLEM: (QAR 69147) (Patch ID: OSF425-617) ******** This patch fixes a ystem panic, with panic string: "simple_lock_terminate: lock busy" This could occur when running a multi-threaded task with lockmode 4 set. PROBLEM: (QAR 65945) (Patch ID: OSF425-617) ******** This patch fixesa system panic, with panic string: "lock_terminate: lock held" This could occur from a failure of the system to unlock in a particular error condition. PROBLEM: (QAR 56967) (Patch ID: OSF425-672) ******** 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: (QAR 61627) (Patch ID: OSF425-686) ******** This patch ensures all AdvFS root fileset buffers are flushed on shutdown. Fixed 'simple lock held' error on shutdown with AdvFS root and lockmode = 4. PROBLEM: (QAR 69261, QAR 69769) (Patch ID: OSF425-687) ******** This patch fixes a UFS panic with the following error message: malloc_check_checksum: memory pool corruption A sample stack trace follows: 1 panic 2 event_timeout 3 xcpu_puts 4 printf 5 panic 6 malloc_check_checksum 7 free_trim 8 free 9 str_timeout 10 softclock_scan 11 hardclock 12 _XentInt 13 swap_ipl_preempt_check 14 nxm_idle PROBLEM: (QAR 72410) (Patch ID: OSF425-734) ******** This patch fixes the database application core dumps when using truss/trace tools by remembering that COW has been setup on a shared pte and process it correctly when a subsequent write access is made to the page. PROBLEM: (QARS 65261 68308 68047) (Patch ID: OSF425-736) ******** This patch fixes a problem with NFS locking when lockmode is set to 4. The system can panic with "lock_write: hierarchy violation" or "lock_write: simple lock owned". An example stack trace will look like the following: 1 panic() 2 lock_fault() 3 lock_write() 4 ubc_bufalloc() 5 ufs_rwblk() 6 ufs_writepages() 7 ufs_putpage() 8 ubc_flush_dirty() 9 mntflushbuf() 10 boot() 11 panic() 12 lock_fault( 13 lock_write() 14 bs_real_invalidate_pages() 15 msfs_reclaim() 16 vclean() 17 vgone() 18 getnewvnode() 19 makenfsnode() 20 nfsrootvp() 21 nfs_mount() 22 mount1() 23 mount() 24 syscall(0 25 _Xsyscall() PROBLEM: (QAR 72764) (Patch ID: OSF425-738) ******** This patch fixes a problem in which system may memory fault if TCR/ASE server no longer had access to the cdrom device. PROBLEM: (QAR 58781, QAR 64371) (Patch ID: OSF425-740) ******** This patch forces the kernel malloc code to print failure messages only when kmem_debug is enabled and also corrects some other minor kmem_debug problems. PROBLEM: (QAR 72420) (Patch ID: OSF425-741) ******** This patch fixes a class scheduler problem seen when scheduling PIDS. The PID class scheduling heuristics have been changed such that a child does not inherit its parents class scheduling policy. PROBLEM: (QAR 73356) (Patch ID: OSF425-743) ******** This patch fixes a system hang problem due to a bug in the nfs write gathering code. The code does not fully synch all writes. PROBLEM: (QAR 70152, QAR 72017, CLD MG0104072) (Patch ID: OSF425-746) ******** This patch fixes a problem with the KZPSA driver. A timer is not being canceled causing a panic with the following error message: xpt_callback: callback on freed CC The sample stack trace is listed below: 4 boot 5 panic 6 xpt_callback 7 spo_process_ccb 8 spo_process_rsp 9 pzaintr 10 intr_dispatch_post 11 _XentInt 12 idle_thread PROBLEM: (QAR 70220) (Patch ID: OSF425-749) ******** Use of mmap can sometimes result in data corruption. PROBLEM: (QAR 73589) (Patch ID: OSF425-754) ******** Because of a problem involving signal delivery, multithreaded applications can exhibit very poor performance or may even hang. PROBLEM: (QARS 64531, 68748) (Patch ID: OSF425-756) ******** This patch improves nfs performance by avoiding an undesired cache invalidation that can have a big impact on NFS performance with huge files. PROBLEM: (CLD EVT102855, QAR 73939) (Patch ID: OSF425-764) ******** This patch fixes a problem where RCP commands issued from a Sun Solaris system to Compaq Tru64 UNIX may sometimes fail incorrectly with the error message "Connection reset by peer." PROBLEM: (ALC-08332) (Patch ID: OSF425-765) ******** This fixes a "simple_lock: hierarchy violation" panic from sigq_abort(). PROBLEM: (CLD STLQ74833) (Patch ID: OSF425-766) ******** This patch fixes a problem where a socket connection was not closing correctly in certain situations. This caused CPU0 in a mutli-cpu system to hang in the socket close routines. Here is an example stack trace of the hung CPU: > 0 simple_unlock() 1 lock_done() 2 sounlock() 3 soclose() 4 soo_close() 5 closef() 6 close() PROBLEM: (BCPM81CNT/BCPM80N9B) (Patch ID: OSF425-770) ******** This patch fixes a kernel memory fault caused when a network application walked an inpq array. The problem occured on an ASE configuration that was running user scripts configuring the network interfaces. The stack looked like this: 0 thread_block 1 thread_preempt 2 boot 3 panic 4 trap 5 _XentMM 6 table 7 syscall 8 _Xsyscall PROBLEM: (BRO101338 BRO101359) (Patch ID: OSF425-771) ******** This patch fixes system crashes seen on ASE or Cluster systems when changing the network interfaces. The stack is not informative and the panic may be "trap: illegal instruction," or "kernel memory fault." PROBLEM: (QAR 67188, QAR 67164) (Patch ID: OSF425-773) ******** The patch fixes two problems which are: 1) Locking/unlocking of a segmented shared memory region causes the system to panic with the following message: (cpu 0): vm_page_ssm_unwire. 2) The segmented shared memory does not handle simultaneous shared memory locks and unlock causing the system to panic with the following message: ssm_anon_free: wired/held/busy page PROBLEM: (CLD BCGM60T9M) (Patch ID: OSF425-776) ******** This patch fixes a problem of the fverify -n flag creating directores. PROBLEM: (MGO44815A) ******** This patch fixes a problem with soclose() that caused permanent looping on exit while aborting pending connections at a TCP/IP listener socket. The thread in the loop condition will typically have this stack trace: simple_unlock lock_write solock soclose soo_close closef exit PROBLEM: (QAR 73885) ******** This patch fixes a problem in realtime preemption support where a thread may be suspended due to an uninterruptible sleep. Processes will hang while retaining their system resources, causing a slowdown in system throughput. PROBLEM: (QARs 73347, 73916) (Patch ID: OSF425-787) ******** This patch updates the lfa ATM driver to V1.0.16 and fixes the following two ATM driver problems: - Filesystems mounted using NFS over an ATM connection which uses either the Compaq HE622 or HE155 ATM adapters can experience soft hangs. When this happens, a file transfer operation will not complete (typically a write from the client to the server) or an unmount operation will hang. The rest of the system is still operational. - Under certain configurations, the ATM adapter can hang. When this occurs, the ATM subsystem cannot be successfully shut down and then restarted. Following an "atmconfig down driver=lfa<#>" command, the driver and ATM stack enters an unrecoverable state where no further operations are allowed. The state remains "GOING DOWN" (as reported by the command "atmconfig status driver=lfa<#>") until the next system boot. PROBLEM: (QAR 74449) (Patch ID: OSF425-790) ******** The patch fixes a problem with virtual memory. When running the Oracle database, Oracle can not detach from a shared memory segment. PROBLEM: (QAR 74057, QAR 65727) (Patch ID: OSF425-792) ******** This patch fixes single-step support in a debugger, such as Ladebug, for instructions that trap or fault. The way single-stepping is implemented, it assumes the instruction being stepped over completes. If it traps or faults, the single step does not happen and the breakpoint(s) are left in. The image then becomes corrupted. This patch fixes all cases where an isntruction does not complete, removes the breakpoint(s) as necessary, and fixes up the exception frame. PROBLEM: (QAR 68687) (Patch ID: OSF425-798) ******** This patch fixes an incorrect calculation for memory-usage-by-type when kmem_debug is set. This can be seen in the output of the "vmstat -M" command when a negative value is displayed for a given type. PROBLEM: (QAR 74308 QAR 73808) (Patch ID: OSF425-799) ******** The wrong EEI status is returned when a tape device reports ASC/ ASCQ 0x2903 after Bus D has been detected. The correct EEI status for the this condition is EEI_DEVPATH_RESET; the status being returned is EEI_DEVHARD_FAILURE. PROBLEM: (CLD CFS.69611) (Patch ID: OSF425-804) ******** This patch fixes a problem when all nodes in a cluster can panic at the same time with a simple_lock timeout panic. PROBLEM: (CLD GOZ72114A, CLD BCGMA10Z6, CLD BCGMA0X3C, CLD BCGMA1GFC, CLD BCGMB06HF, CLD DSATB0SF1, CLD DSATB0X2F, CLD HPAQB0X3N, CLD EVT75135A) (Patch ID: OSF425-810) ******** This patch fixes a problem on configurations having multiple Qlogic 1020/1040 based SCSI controllers (such as KZPBA) and multiple CPUs. The symptom of the problem is a performance degradation up to having ss_perform_timeouts being logged against the KZPBA scsi devices. In some extreme cases, the symptoms can be so severe that it makes make it appear as if the system was hung. Tape units have had a number of problems with vdump, tar, and nsrd related to the command timeouts. PROBLEM: (QAR 73901) (Patch ID: OSF425-812) ******** This patch fixes a TCP performance problem if the TCP window scale option is turned off when using the HIPPI interface. PROBLEM: (MGO80471A) (Patch ID: OSF425-815) ******** Structures as currently defined in cam_rci can cause an unaligned access fault in kernel when shared tapes are utilized. PROBLEM: (CLD UVO30139, CLD BCGM90S8G, CLD DMO90586B, CLD MGO63356A, CLD ZUO101627, CLD BCGM90FV0, CLD BCGM91KD1, CLD MGO57622A, CLD HPAQA1R8D, CLD VNO40593A, CLD UVO106437, CLD SQO100587, CLD UVO106521) (Patch ID: OSF425-817) ******** This patch fixes a problem where tmv2_notify_cbf messages are reported and flood the error log when running in a clustered environment with KZPSA adapters. PROBLEM: (QAR 73967 QAR 73853) (Patch ID: OSF425-822) ******** This patch fixes a problem in which the system can crash with a kernel memory fault and the following stack trace: 10 panic(s = "kernel memory fault") 11 trap() 12 _XentMM) 13 strncpy() 14 ccmn_errlog3() 15 cdisk_devt_to_trans() 16 cdisk_io_barrier() 17 drd_do_iob() 18 drd_iob_thread() PROBLEM: (QAR 74776 QAR 75082 FNO81417A) (Patch ID: OSF425-830) ******** This patch is an upgrade to the Gigabit ethernet driver version 1.0.12 to fix various performance problems. PROBLEM: (HPAQ70DBD) (Patch ID: OSF425-833) ******** This patch fixes a problem where the system can panic with the panic string "secsize_resid < d_reclen" when accessing a defective cdrom. The stack trace of the panicing thread will be similar to: 0 boot 1 panic 2 cdfs_readdir 3 getdirentries 4 syscall 5 _Xsyscall PROBLEM: (MGO104025 QAR 75210) (Patch ID: OSF425-834) ******** This patch fixes a system hang condition. All NFS related services may deadlock. PROBLEM: ('QAR 73124, QAR 71118') (Patch ID: OSF425-836) ******** This patch fixes a problem where partitioned turbolasers return incorrect cpu data for cpus that are not in the partition. PROBLEM: (TKTB90028, TKTBA0054) (Patch ID: OSF425-837) ******** This patch fixes a problem where on systems with a Powerstorm 4D10T (ELSA Gloria Synergy) graphics board, the graphics were not reset to console mode (the blue screen) when the halt button was pressed. PROBLEM: (QAR 74959) (Patch ID: OSF425-843) ******** This patch fixes a problem where ubc_msync() may not flush out all the pages in requested range. PROBLEM: (BCGM90Z90) (Patch ID: OSF425-845) ******** This patch fixes a problem where timeouts are not canceled on I/O requests causing the I/O block to be freed inappropriately. PROBLEM: (QAR 75381) (Patch ID: OSF425-853) ******** This patch consists of changes necessary for AV firewall 98 to pass ICSA certification. PROBLEM: (BCSMA1923/75276) (Patch ID: OSF425-854) ******** This patch fixes var adm messages from truncation on larger configurations by raising the default size (4096) of 'msgbuf_size' to 8192. PROBLEM: (QAR 73764, QAR 59328) (Patch ID: OSF425-750) ******** This patch fixes a problem with the parameter checking code of the fcntl system call. As a result, incorrectly coded fcntl() parameters in user programs no longer panic the system. PROBLEM: (QAR 67156,QAR 61985,QAR 66890) (Patch ID: OSF425-775) ******** This patch fixes the AdvFS race between extending and reading subextent maps and avoids the panic occured in advfs bs_get_bf_xtnt_map code (qar 61985). This patch also fixes the race with removing storage causing kernel memory fault (qar 66890). QAR 61985:Panic occurred in advfs bs_get_bf_xtnt_map code. stack trace: ----------- (dbx) t > 0 boot(0x400000000, 0x4, 0xfffffc00007a7330, 0x0, 0x4) ["../../../../src/kernel/arch/alpha/machdep.c":2350, 0xfffffc0000590d74] 1 panic(s = 0xfffffc00006f0748) ["../../../../src/kernel/bsd/subr_prf.c":1163, 0xfffffc00002883f4] 2 hardclock(pc = 0xfffffc000052e7c8, ps = (unallocated - symbol optimized aw ay)) ["../../../../src/kernel/bsd/kern_clock.c":1163, 0xfffffc000025a3f0] 3 _XentInt(0x2, 0xfffffc000052e7c8, 0xfffffc00006d5af0, 0xfffffc00081a4000, 0xc00000cd0052f94a) ["../../../../src/kernel/arch/alpha/locore.s":1487, 0xfffffc000058d0f4] 4 vdealloc() ["../../../../src/kernel/vfs/vfs_subr.c":1374, 0xfffffc000052e7c4] 5 vrele(vp = 0x1d9) ["../../../../src/kernel/vfs/vfs_subr.c":2370, 0xfffffc000052f984] 6 mntbusybuf(mountp = 0xfffffc0002c83540) ["../../../../src/kernel/vfs/vfs_bio.c":1509, 0xfffffc0000527ab4] 7 boot(0x0, 0xfffffc0009920700, 0xfffffc0000000000, 0x2c0000002c, 0x32) ["../../../../src/kernel/arch/alpha/machdep.c":2305, 0xfffffc0000590c7c] 8 panic(s = 0xfffffc000076c050) ["../../../../src/kernel/bsd/subr_prf.c":1248, 0xfffffc00002885e4] 9 trap(a0 = (...), a1 = (...), a2 = (...), code = 0xfffffc00003fcfb4, exc_fr ame = 0xffffffff8cfe3 538) ["../../../../src/kernel/arch/alpha/trap.c":1877, 0xfffffc0000598af8] 10 _XentMM(0x0, 0xfffffc00003fcfb4, 0xfffffc00006d5af0, 0xffffffff8096e008, 0 x1) ["../../../../src/kernel/arch/alpha/locore.s":2091, 0xfffffc000058d594] 11 bs_get_bf_xtnt_map(0xffffffff8cfe37a8, 0xfffffc00021f4008, 0xfffffc0001fbf c08, 0xfffffc00021f40 20, 0x1) ["../../../../src/kernel/msfs/bs/bs_params.c":578, 0xfffffc00003fcfb0] 12 msfs_real_syscall(0xfffffc00021f4008, 0xfffffc0009e16a80, 0x0, 0x0, 0x0) ["../../../../src/kernel/msfs/bs/bs_misc.c":2809, 0xfffffc00003f8bfc] 13 msfs_syscall(0x0, 0x0, 0x0, 0x41, 0xfffffc00005962f0) ["../../../../src/kernel/msfs/osf/msfs_syscalls.c":145, 0xfffffc00002d103c] 14 syscall(0x20, 0xfffffc000023e8a1, 0x1, 0x13e2e3588136e, 0x0) ["../../../../src/kernel/arch/alpha/syscall_trap.c":718, 0xfffffc00005962ec ] 15 _Xsyscall(0x8, 0x3ff8123da08, 0x3ffc05cbe00, 0x60003, 0x11fff7190) ["../../../../src/kernel/arch/alpha/locore.s":1796, 0xfffffc000058d354] QAR 66890:"invalid memory read access" in imm_page_to_sub_xtnt_map(): stack trace: ----------- 5 panic(0xfffffc0000ae6300, 0xfffffc0000775698, 0x0, 0x46, 0x29211) ["../../../../src/kernel/bsd/ subr_prf.c":804, 0xfffffc000028a498] 6 trap(a0 = (...), a1 = (...), a2 = (...), code = 0xfffffffeae0bf490, exc_ frame = 0xfffffffeae0bf 388) ["../../../../src/kernel/arch/alpha/trap.c":1747, 0xfffffc0000576644] 7 _XentMM(0x0, 0xfffffc00003eb6c4, 0xfffffc00007cb0e0, 0x5cb0, 0xfffffc00d8 6ec908) ["../../../../ src/kernel/arch/alpha/locore.s":1736, 0xfffffc000056aed4] 8 imm_page_to_sub_xtnt_map(0x0, 0xfffffc00003eb6c4, 0xfffffc00007cb0e0, 0x5 cb0, 0xfffffc00d86ec90 8) ["../../../../src/kernel/msfs/bs/bs_inmem_map.c":2290, 0xfffffc00003eb6c0] 9 x_page_to_blk(0xfffffffeae0bf548, 0x5cb0, 0xfffffffe00c5d3f0, 0x800100000 001, 0x100000010) [".. /../../../src/kernel/msfs/bs/bs_stg.c":6113, 0xfffffc000040497c] 10 x_page_to_blkmap(0x2000, 0x0, 0xfffffffe00e259a4, 0x0, 0x0) ["../../../../src/kernel/msfs/bs/bs _stg.c":5836, 0xfffffc0000404718] 11 x_page_mapped(0x0, 0x2, 0xfffffc000000003d, 0x1, 0xfffffffeae0bf568) ["../../../../src/kernel/m sfs/bs/bs_stg.c":6189, 0xfffffc0000404a9c] 12 bs_frag_has_stg(bfSetH = struct { setH = 0x5cb0 dmnH = 0x0 }, fragId = struct { frag = 0x2e587 type = BF_FRAG_6K }) ["../../../../src/kernel/msfs/bs/bs_bitfile_sets.c":2166, 0xfffffc00003c7a8 0] 13 msfs_getattr(vp = 0x1, vap = 0xfffffffeae0bf648) ["../../../../src/kernel/msfs/osf/msfs_vnops.c ":1475, 0xfffffc000043d8cc] 14 pacl_vnperm(0x367c099f000ebbfa, 0x8003000ebbfa, 0x0, 0x2000, 0x0) ["../../../../src/kernel/sec/ sec_acl.c":614, 0xfffffc000024f2a8] 15 paclaccess(0x0, 0xfffffc00d234fc80, 0xfffffc000024f1bc, 0xfffffc00a2ef880 0, 0x1) ["../../../../ src/kernel/sec/sec_acl.c":906, 0xfffffc000024f7c4] 16 sp_vnaccess(0xfffffc000024f1bc, 0xfffffc00a2ef8800, 0x1, 0x1, 0xfffffc000 043d308) ["../../../.. /src/kernel/sec/sec_acl.c":579, 0xfffffc000024f1b8] 17 msfs_access(vp = 0xfffffc00a2ef8800, cred = 0xfffffc007f201c00) ["../../../../src/kernel/msfs/o sf/msfs_vnops.c":1251, 0xfffffc000043d304] 18 vn_open(0xfffffc000051a83c, 0xfffffffeae0bf8f0, 0xfffffc0000000003, 0xfff ffffeae0bf840, 0xfffff ffeae0bf838) ["../../../../src/kernel/vfs/vfs_vnops.c":614, 0xfffffc00005271b4 ] 19 copen(0x0, 0x3, 0xfffffc00d1f3b880, 0xfffffc008bc2d220, 0xfffffffeae0bf8e 0) ["../../../../src/k ernel/vfs/vfs_syscalls.c":2420, 0xfffffc000051a900] 20 open(0xfffffc00d1f3b880, 0xfffffc008bc2d220, 0xfffffffeae0bf8e0, 0x12, 0x fffffc0000573d28) PROBLEM: (71007, 73965) (PATCH ID: OSF425-780) ******** This patch fixes a problem in which `ufs_fsck` can get blocked while attempting to flush nfs buffers for a service that has become suspended. PROBLEM: (QAR 74109 69359,cld alc-08485) ******** This patch fixes a problem in which the scheduler made its choice of threads when dispatching from the idle state. The first thread woken is put into the processor next_thread field as the next thread to run. If multiple threads a woken, this could cause a priority inversion since the first one awoken may not have the highest priority. PROBLEM: (QAR 51449, QAR 70650) (Patch ID: OSF425-797) ******** This patch fixes a panic in AdvFS which can have the following error messages: panic (cpu 1): bs_cow_pg: pin clone err -OR- panic (cpu 1): bs_cow_pg: cannot get blkMap PROBLEM: ('QAR 73644') (Patch ID: OSF425-816) ******** This patch fixes a problem with making a msfs_putpage() call. The length argument may get its upper bits truncated which will result in an incorrect length calculation. PROBLEM: (DEKQC0005, STLNC4615) (Patch ID: OSF425-862) ******** This patch fixes a problem where systems with the DUV40DAS0005-19991007 patch kit installed would run low on kernel memory after process accounting had been running for a while. PROBLEM: (QAR 57405) (Patch ID: OSF425-145) ******** This patch fixes a problem in a cluster configuration with the fta FDDI driver. The console message seen for this problem is: hw_sg_load: load request too big, pages alloced 1 required 2 PROBLEM: (MGO103292) (Patch ID: OSF425-148) ******** This patch fixes a kernel memory fault caused by the fta FDDI driver. The stack trace looks like this: PROBLEM: (CLD MCPM40MKM, QAR 52790) (Patch ID: OSF425-179) ******** This patch fixes a problem that may occur on systems with a FDDI controller. During system boot, the system may panic with a message similar to the following: fta0 DEC DEFPA FDDI Module, Hardware Revision 0 trap: invalid memory read access from kernel mode FVA: 0x0000000000000000 PC: 0xfffffc0000507628 RA: 0xfffffc0000503ed0 sp: 0xffffffffa5bc32f8 panic (cpu 8): kernel memory fault DUMP: No primary swap, no explicit dumpdev. Nowhere to put header, giving up. PROBLEM: (MXOB30447) (Patch ID: OSF425-212) ******** This patch corrects a problem with the FDDI fta driver. In systems that have heavy FDDI traffic, it is possible for the FDDI fta driver to think it received a bad packet. A message will appear in the /var/adm/messages file similar to the following: vmunix: fta0: Invalid length: DA: ef-be-ad-de-ef-be => SA: ad-de-ef-be-ad-de In this example, kmem_debug was turned on with kmem checksum. The kmembucket that was being read by the driver was corrupted BEFORE the read was posted. You may see different values on your system. PROBLEM: (QAR 72787) (Patch ID: OSF425-688) ******** This patch fixes a kernel memory fault caused by a mishandling of multicast addresses on the FDDI interface. The following stack represents this problem: panic afault_trap _XentUna write_io_port fta_transition_state PROBLEM: (NONE) (Patch ID: OSF425-856) ******** This patch involves virtual mac addressing. PROBLEM: (QAR 49683,QAR 47674) (Patch ID: OSF425-068) ******** This patch fixes a problem in which a system may crash if multiple bad blocks on a SCSI device are encountered simultaneously. The stack trace is as follows: 0 boot() 1 panic() 2 trap() 3 _XentMM() 4 cdisk_bbr_done() 5 cdisk_bbr_write() 6 cdisk_bbr_reassign_done() 7 cdisk_bbr_work() 8 cdisk_bbr_comp() 9 as_finish() 10 xpt_callback_thread() PROBLEM: (BCGM80NCB) (Patch ID: OSF425-394) ******** This patch fixes a problem in the cam driver. A disk failure can cause the driver to spend too much time retrying interleaved Test Unit Ready and Start Unit commands. As a result, the logging of the hard error caused by the disk failure is delayed. PROBLEM: (QAR 64377) (Patch ID: OSF425-442) ******** This patch fixes the erroneous "SAR Stats" implementation of CAM statistics. The original CAM stat's macros calculated inappropriate time deltas because they were not measured on a per-io basis, and the times did not account for overlapping i/o. PROBLEM: (CLD TKTR12275 CLD TKTR21726) (Patch ID: OSF425-584) ******** A typical stack trace is: 5 panic "ccmn_rem_ccb3: ccb not on any list") 6 ccmn_rem_ccb3 7 cdisk_complete 8 xpt_callback_thread PROBLEM: ((CLD MGO103941M, CLD MGO103897) (Patch ID: OSF425-739) ******** On a very busy SCSI device an I/O can indefinitly stall and never complete. PROBLEM: (BCGM10J56, BCGM4180B, BCGM41HLM, MGO36744A, 7XRB90123) (PATCH ID: OSF425-872) ******** This patch fixes the following 3 problems: 1.)When a SCSI I/O command results in a bus reset, which causes the command to be re-issued, the system sometimes can not recover and ends up in a tight loop of bus resets. 2.) After a recovery operation is performed, the read disk capacity sizing of the disk sometime fails to match the original value, which causes the recovery to fail. 3.) A BBR (bad block replacement) informational message received from an HSZ is mistakenly classified as an error. PROBLEM: (TKTR71181) (PATCH ID: OSF425-846) ******** This fixes simple_lock timeouts holding the ubc_lru_lock too long. PROBLEM: (QAR 76145 and 76180) (PATCH ID: OSF425-861) ******** This patch fixes a problem where programs that read, analyze and monitor disk statistics (such as "collect") will occasionally display incorrect results. This is especially seen when calculating quantities related to the percentage of time a disk is "busy" servicing I/O requests. PROBLEM: (74926, 75142) (PATCH ID: OSF425-865) ******** This patch fixes a problem in which the interaction between mfs file systems and smoothsync causes procprod to read stale data. PROBLEM: (71242, 73860) (PATCH ID: OSF425-866) ******** This patch fixes a problem in which the system can panic with a kernel memory fault during an installation with an HSZ70 or HSZ80 connected to the system. PROBLEM: (SQO43343A, EVT33786A, HPAQC1MDN, TKTBC0056) (PATCH ID: OSF425-867) ******** This fixes a kernel memory fault when accessing the vm_map_index hash table. An example stack trace: panic() trap() _XentMM() u_map_delete() vm_map_delete() munmap() syscall() _Xsyscall() PROBLEM: (MGO90721A) (PATCH ID: OSF425-868) ******** This patch fixes a problem with simple_lock: time limit exceeded panic seen on SMP systems with the namei.nch_lockinfo lock. A typical entry in the /var/adm/messages file would be: simple_lock: time limit exceeded pc of caller: 0xfffffc00004445d8 lock address: 0xfffffc0000eb50e8 lock info addr: 0xfffffc0000772be0 lock class name: namei.nch_lockinfo current lock state: 0x800000be00443b45 (cpu=0,pc=0xfffffc0000443b44,busy) PROBLEM: (13096) (PATCH ID: OSF425-873) ******** In the per-VP scheduling state that is shared between the kernel and the DECthreads library scheduler, the compiler generates ldq/stq pairs for a 32-bit data object that neighbors another 32-bit variable. This patch fixes the stq that causes a word tear that corrupts the per-VP floating point flag field called nxm_fp_owned. The affected data structures are defined in . PROBLEM: (BCPMB215Q) (PATCH ID: OSF425-875) ******** This patch fixes a kernel memory fault in VMAC code if_addnewaddr(). The fault will occur from ifconfig(8) and the stack will include: _XentMM bcmp if_addnewaddr ifioctl soo_ioctl ioctl_base ioctl syscall PROBLEM: (HPAQC15V8) (PATCH ID: OSF425-876) ******** This fixes a kernel memory fault in procfs_get_s5_dir(). PROBLEM: (HPAQB1FTS) (PATCH ID: OSF425-877) ******** This patch fixes a system panic with panic string: "psig: catch not set" An example stack trace is as follows: panic() psig() mach_checksig() PROBLEM: (MGO84898A) (PATCH ID: OSF425-878) ******** This corrects a kernel memory fault caused by rw3vp_cache passing a bad address to _OtsZero(). An example stack trace: panic() trap() _XentMM() _OtsZero() rw3vp_cache PROBLEM: (76461, 75539) (PATCH ID: OSF425-898) ******** This patch fixes a problem in which an application can hang because of an undelivered signal. PROBLEM: (BCGM10RFF, 77112) (PATCH ID: OSF425-904) ******** This patch fixes a problem where if the size of a message queue was increased, writers to the queue that were blocked would not wake up for processing. The msgctl(2) and msgsnd(2) system calls now test if the message queue size has increased and if there are writers waiting to get unblocked, then wakeup the writers and let them proceed. PROBLEM: (HPAQ10DTH, UVO55282) (PATCH ID: OSF425-907) ******** This patch provides the latest driver for the PowerStorm 4D10T (ELSA GLoria Synergy, SN-PBXGK-BB) graphics card. This version of the driver fixes a problem where the card might fail to operate correctly after a reboot. PROBLEM: (UVO74098) (PATCH ID: OSF425-915) ******** This patch adds a fix to VMAC functionality when used with NETRain. PROBLEM: (EVT91336A) (PATCH ID: OSF425-917) ******** This patch fixes a problem where the following can occur during a system panic: - system calls interrupts - mpsleep() returns an EINTR error when the panicstr is non-NULL - an indefinite looping at a very high priority PROBLEM: (HPAQ20N23) (PATCH ID: OSF425-921) ******** This patch corrects a problem with the incorrect ordering of network interfaces which was resulting in network partitions. PROBLEM: (77506, 77655) (PATCH ID: OSF425-922) ******** This patch fixes a number of problems in the driver shutdown path. All the problems would result in a kernel memory fault panic but that panic might not manifest itself until the driver was restarted. This patch also enhances the driver by making the following changes: - The deferred interrupt processing path (attribute minimal_isr set to 1) has been modified to perform much better. This method of handling interrupts is now the default. - The time between when an adapter receives a frame and when it generates an interrupt to the host system has been shortened from 768 to 100 microseconds. This reduces the receive processing latency. - The model number string which prints out when the adapter is configured will display the -UA or -FA extension, reflecting the type of media used by the adapter. PROBLEM: (TKTR90018) (PATCH ID: OSF425-928) ******** This patch fixes a "lock_terminate: lock held" panic when deleting a process group. An example stack trace: panic("lock_terminate: lock held") lock_terminate() pgdelete() pgrp_unref() pgrm() proc_teardown() waitf() wait4() syscall() _Xsyscall() PROBLEM: (HPAQ20V27) (PATCH ID: OSF425-929) ******** This fixes an "unaligned kernel space access from kernel mode" panic when doing a malloc from kmembucket[26], 896 byte bucket. The faulting virtual address will be the lock signature for thread_deallocate(). PROBLEM: (BRO96818B) (PATCH ID: OSF425-930) ******** This fixes a kernel memory fault in u_anon_faultpage() when it access the backing object for the anonymous page. An example stack trace: panic() trap() _XentMM() u_anon_faultpage() u_anon_fault() u_map_fault() vm_fault() trap() _XentMM() PROBLEM: (74651, 75705) (PATCH ID: OSF425-934) ******** This patch fixes a problem where a root user was not allowed to check file access on behalf of a user without completely becoming the user. The functionality is needed by the ASU (Advanced Server for UNIX) product. PROBLEM: (HPAQ30SQ8) (PATCH ID: OSF425-935) ******** This patch fixes a panic in in_pcbfree() when ASE fails over NFS applications that use listener sockets. The stack trace will look like the following: panic in_pcbfree tcp_input ipintr netisr_thread PROBLEM: (ISO100518) (PATCH ID: OSF425-944) ******** This patch fixes a kernel memory fault panic seen under certain circumstances when a process or thread was setting its priority. A typical stack trace would be: > 0 boot src/kernel/arch/alpha/machdep.c : 1890 1 panic src/kernel/bsd/subr_prf.c : 834 2 trap src/kernel/arch/alpha/trap.c : 1659 3 _XentMM src/kernel/arch/alpha/locore.s : 1645 4 nxm_manager_boost src/kernel/kern/syscall_subr.c : 2503 5 trap src/kernel/arch/alpha/trap.c : 2132 6 _Xsyscall src/kernel/arch/alpha/locore.s : 1537 PROBLEM: (58325) (PATCH ID: OSF425-948) ******** This patch fixes UFS metadata update performance by adding a mount option, "delayed", for UFS to convert synchronous metadata writes into delayed metadata writes. The File System is often used as a cache for transitory data such as in web servers. Applications such as Squid web proxy server will get a significant performance boost by enabling this option. Restoring from tape is another application that can be benefitted from this. PROBLEM: (TKTR30001) (PATCH ID: OSF425-949) ******** This patch fixes a race condition in the UBC code where a lookup is done on a page being invalidated (freed). The lookup continued to access the data structure after it was freed, and depending on who uses the data structure next, this causes the lookup to think that the invalidation did not complete and wait. PROBLEM: (HPAQA20BT) (PATCH ID: OSF425-951) ******** This patch fixes a problem found to be a race condition involving signals and threads that happens only on multiprocessor systems. A typical stack trace could be: 5 stop_secondary_cpu 6 panic 7 event_timeout 8 simple_lock_miss 9 common_exec 10 execve 11 syscall PROBLEM: (MGO27465A) (PATCH ID: OSF425-957) ******** This patch fixes a problem when the type of SCSI device dynamically changes, which can result in a kernel memory fault or memory corruption panic. The sense inquiry buffer size is allocated too small. A typical stack trace: > 0 stop_secondary_cpu src/kernel/arch/alpha/cpu.c : 608 1 panic src/kernel/bsd/subr_prf.c : 751 2 event_timeout src/kernel/arch/alpha/cpu.c : 1183 3 xcpu_puts src/kernel/bsd/subr_prf.c : 895 4 printf src/kernel/bsd/subr_prf.c : 423 5 panic src/kernel/bsd/subr_prf.c : 804 6 closef src/kernel/bsd/kern_descrip.c : 1973 7 exit src/kernel/bsd/kern_exit.c : 1021 8 rexit src/kernel/bsd/kern_exit.c : 822 9 syscall src/kernel/arch/alpha/syscall_trap.c : 627 10 _Xsyscall src/kernel/arch/alpha/locore.s : 1505 Panic "closef: f_count not 1" due to corruption of 'file' structure PROBLEM: (TKTBC0035, 78015) (PATCH ID: OSF425-958) ******** This patch fixes a problem where the operating system only looks in slot 0 for the primary CPU when in console mode. This can be seen when examining the binary.errlog with the DECevent utility. On a EV6 CPU system, DECevent displays the text in an incorrect format that translates to an EV5 CPU. PROBLEM: (74277, 74545) (PATCH ID: OSF425-962) ******** This patch fixes a problem in which operations on NFS files can hang indefinately. PROBLEM: (71353, 73768) (PATCH ID: OSF425-910) ******** This patch fixes a problem in AdvFS where putpage_lk/pg_busy deadlock causes hangs in the system. The stack traces are listed below: 0 thread_block 1 ubc_invalidate 2 bs_real_invalidate_pages 3 stg_remove_stg_start 4 bf_setup_truncation 5 msfs_setattr 6 vtruncate 7 ftruncate 8 syscall 9 _Xsyscall 0 thread_block 1 lock_wait 2 lock_read 3 msfs_putpage 4 ubc_memory_purge 5 vm_pageout PROBLEM: (UVO04205, 73635) (PATCH ID: OSF425-996) ******** This patch corrects a problem when a network interface is configured using a CIDR bitmask and lies in a certain address range; it could be unreachable by users on the local system and remote systems that choose not to use the routing table, but simply transmit on an interface. PROBLEM: (MGO93619A, BCGM11QN6) (PATCH ID: OSF425-1025) ******** This patch fixes a system panic on a large system configuration. The system will panic with the following panic string: "simple lock time limit exceeded" The lock class will always be: vm_object.ob_lock and the lock will be busy in ubc_written_kluster. An example from the messages file of a system with the problem follows: simple_lock: time limit exceeded pc of caller: 0xfffffc000046f424 lock address: 0xfffffc036bb9f2c8 lock info addr: 0xfffffc0000c1eea0 lock class name: vm_object.ob_lock current lock state: 0xd00000ea004745d9 (cpu=0,pc=0xfffffc00004745d8,busy) panic (cpu 5): simple_lock: time limit exceeded The pc of the current lock state is ubc_written_kluster: (dbx) 0xfffffc00004745d8/i [ubc_written_kluster:4534, 0xfffffc00004745d8] bsr r26, simple_lock (line 1215) PROBLEM: (67762, 74793, HPAQ112FQ) (PATCH ID: OSF425-979) ******** This patch fixes reply values for NFS writes which were causing protocol violations. PROBLEM: (79461) (PATCH ID: OSF425-965) ******** This patch fixes a simple lock timeout violation. The stacktrace is as follows: panic src/kernel/bsd/subr_prf.c simple_lock_fault src/kernel/kern/lock.c simple_lock_time_violation src/kernel/kern/lock.c cam_disk_unit_atten src/kernel/io/cam/cam_disk.c cdisk_check_sense src/kernel/io/cam/cam_disk.c cdisk_complete src/kernel/io/cam/cam_disk.c as_finish src/kernel/io/cam/sim_as.c xpt_callback_thread src/kernel/io/cam/xpt.c PROBLEM: (78473) (PATCH ID: OSF425-988) ******** This patch fixes a problem with cdfs. Fatal errors occur when trying to load data from a cdfs cd-rom over nfs. PROBLEM: (MGO45830B) (PATCH ID: OSF425-967) ******** System spends excessive time in the internet checksum routine due to an invalid message length. Performance is degraded significantly. PROBLEM: (HPAQ40PZ1, BCSM412FX) (PATCH ID: OSF425-978) ******** This patch fixes 2 network problems, a panic in in_pcbfree() when NFS is implemented over TCP and a system hang with threads blocked in in_pcblock(). This patch fixes a panic in in_pcbfree() when NFS is implemented over TCP. If an NFS server stops servicing requests to clients and the server is rebooted to clear the NFS problem, the clients panic in in_pcbfree(). A typical client stack trace is: panic in_pcbfree tcp_input ipintr This patch fixes a system hang caused by threads blocking on complex locks held by netisr thread in the in_pcblookup() code. A typical stack trace for this problem will be: thread_block lock_read in_pcblookup udp_input or tcp_input ipintr netisr_thread PROBLEM: (77638, 78380) (PATCH ID: OSF425-997) ******** This patch fixes a panic in the UFS filesystem which has the following error message: blkfree: freeing free block The stack trace is listed below: 1 panic() 2 event_timeout() 3 xcpu_puts() 4 printf() 5 panic() 6 blkfree() 7 indirtrunc() 8 itrunc() 9 ufs_setattr() 10 vn_open_ftrunc() 11 vn_open() 12 copen() 13 open() 14 syscall() 15 _Xsyscall() PROBLEM: (79937, 79251, 79305, 80973) (PATCH ID: OSF425-1019) ******** This patch fixes a hang or simple_lock_state_violation/simple_lock_fault panic in biodone. This patch places mount throttle fields under the new mount_throttle_lock (locking requirements described in mount.h). These fields previously were under the mount lock. The problem is that it was possible for the mount lock to be held in a context which could be interrupted by a higher priority event, such as biodone, which could also require this lock. The solution is to protect these fields under a different lock and spl. The key pieces of the stack trace for this problem are: biodone() -- wants mount lock ... ... -- interrupt service routines ... _XentInt() -- interrupt ... vfs_unbusy() -- some routine which takes the mount lock (vfs_unbusy is not unique here) ... PROBLEM: (73112, 78765) (PATCH ID: OSF425-1007) ******** This patch fixes two panics that has the following error messages: simple_lock: time limit exceeded -and- simple_lock: lock already owned by cpu Sample stack traces are listed below: Stack trace #1 simple_lock: time limit exceeded pc of caller: 0xffffffff000adf44 lock address: 0xfffffc001879ca80 lock info addr: 0xfffffc0001404cd0 lock class name: task.lock current lock state: 0xd00000bd000ac4cd panic (cpu 0): simple_lock: time limit exceeded syncing disks... done Stack trace #2 12 panic("simple_lock: lock already owned by cpu") 13 simple_lock_fault() 14 simple_lock_state_violation() 15 thread_deallocate() 16 task_swapout() 17 task_swapout_thread() PROBLEM: (HPAQ818FH, EVT39049A) (PATCH ID: OSF425-1040) ******** This patch increases the efficiency of the tcp_timers. PROBLEM: (VNO56348A) (PATCH ID: OSF425-1094) ******** This patch fixes a problem where the Korn shell (ksh) could hang if you pasted a large number of commands to it when it was running in a terminal emulator window (such as an xterm). PROBLEM: (EVT0523123) (PATCH ID: OSF425-1086) ******** This patch fixes a memory leak when named pipes (FIFOs) are used. PROBLEM: (BCGM71Z77) (PATCH ID: OSF425-1029) ******** This patch fixes a bug where quotacheck -v will report that it has fixed some quotas. If you keep running the command, it will keep reporting the exact same fixes. For example: # quotacheck -v /disk26 *** Checking user and group quotas for BCGM71Z7#disk26 (/disk26) system fixed: inodes 2 -> 5 blocks 16 -> 32896 fixed: inodes 3 -> 0 blocks 32880 -> 0 # quotacheck -v /disk26 *** Checking user and group quotas for BCGM71Z7#disk26 (/disk26) system fixed: inodes 2 -> 5 blocks 16 -> 32896 fixed: inodes 3 -> 0 blocks 32880 -> 0 # quotacheck -v /disk26 *** Checking user and group quotas for BCGM71Z7#disk26 (/disk26) system fixed: inodes 2 -> 5 blocks 16 -> 32896 fixed: inodes 3 -> 0 blocks 32880 -> 0 PROBLEM: (EVT18628A, 59132) (PATCH ID: OSF425-1090) ******** This patch modifies advfs kernel code and several utilities. AdvFS will no longer panic with the following error: ADVFS EXCEPTION : panic cpu(0) : bad frag free list. The code is modified so that during frag allocation when advfs determines that the frag group header's free list has been corrupted, it stops using it and marks it BAD. It is then removed from the free list so no more allocations can take place AND no deallocations are performed. The verify, shfragbf and vfragpg programs are modified to report BAD frag groups. PROBLEM: (ALC-2-076) (PATCH ID: OSF425-1075) ******** This patch provides support for activating temporary atomic write data logging on all files within the mount point. The data logging is turned off when the fileset is unmounted. PROBLEM: (87559) (PATCH ID: OSF425-1105) ******** This patch fixes a "simple_unlock: lock not owned by cpu" panic in the biodone routine. In the V4.x and V5.0A pools, the mount_throttle_lock is a single global lock. This patch prevents the lock from getting re-initialized on subsequent mounts. The problem causes a system panic. The panic string will be: "simple_unlock: lock not owned by cpu" and will occur in the biodone routine. Typical stack trace: (dbx) t > 0 stop_secondary_cpu() 1 panic() 2 event_timeout() 3 xcpu_puts() 4 printf() 5 panic() 6 simple_lock_fault() 7 simple_unlock_owner_violation() 8 biodone() 9 cdisk_complete() 10 xpt_callback_thread() PROBLEM: (85940, BCSM30828) (PATCH ID: OSF425-1104) ******** This patch fixes a kernel memory fault by changing code to delete a cache reference when removing an inp from a que head. An example of the KMF stack trace would look like: 0 stop_secondary_cpu 1 panic 2 event_timeout 3 xcpu_puts 4 printf 5 panic 6 trap 7 _XentMM 8 lock_write 9 solock 10 tcp_input 11 ipintr 12 netisr_thread PROBLEM: (82489, SSRT0676U) (PATCH ID: OSF425-1074) ******** A potential security vulnerability has been discovered, where under certain circumstances, system integrity may be compromised. This may be in the form of improper file or privilege management. Compaq has corrected this potential vulnerability. PROBLEM: (70564) (PATCH ID: OSF425-1057) ******** This patch provides several fixes including: 1) Signal parent process to enable user notification of mount failure. 2) Return functionality to accept disk-type from user. 3) Exit if overlap detected and not being run interactively. 4) Don't do check_usage for -N option or mfs. 5) Move common variable declarations to header file. 6) Adjust fssize and references to it to handle larger file systems. PROBLEM: (84853) (PATCH ID: OSF425-1067) ******** CDFS media burned in 2001 shows the wrong dates. PROBLEM: (82071) (PATCH ID: OSF425-1035) ******** Kernel memory fault while using tablet instead of mouse. panic() trap() _XentMM() pgrp_ref() ttwakeup() ttyflush() tt_sysv_compat() ttioctl() aceioctl() spec_ioctl() vn_ioctl() ioctl_base() syscall() _Xsyscall() PROBLEM: (76966) (PATCH ID: OSF425-1022) ******** This patch fixes a problem with the consvar command consvar -s that allows setting a boot device to a tape device for booting from a tape. PROBLEM: (78704) (PATCH ID: OSF425-1089) ******** This patch fixes a hang in the ufs filesystem. PROBLEM: (HRYGRNTDS, JOE-08768, 68735) (PATCH ID: OSF425-1095) ******** This patch resolves problems encontered with the Ladebug and TotalView debuggers. PROBLEM: (80302, 80232) (PATCH ID: OSF425-1026) ******** This patch fixes a kernel memory fault from ufs_mount(). PROBLEM: (HGO073056) (PATCH ID: OSF425-1083) ******** This patch fixes a problem where threads can hang while renaming files on nfs mounted filesystems. This can occur when two threads are renaming files, one from directory "a" to directory "b" and the other from directory "b" to "a". A typical stack trace for a hung thread looks like: 0 thread_block 1 lock_write 2 nfs3_rename 3 rename 4 syscall PROBLEM: (ALC-2-076) (PATCH ID: OSF425-1093) ******** This patch fixes a timing window where flushing data to disk can be incomplete when a system is going down. Note this can only occur if all of these conditions are true: o More than one thread calls the reboot() system call without first going through shutdown, /sbin/reboot, or /sbin/halt (note the operating system itself does not do this, it would have to be an application program which is calling reboot()). o O_SYNC is not in use. o AdvFS data logging is not in use. PROBLEM: (GOZ24311B, 86217) (PATCH ID: OSF425-1047) ******** This patch fixes a problem in which the system may panic with the panic string "Unaligned kernel space access from kernel mode". An example panic stack trace is: 0 thread_block 1 xpt_ccb_alloc 2 ccmn_get_ccb3 3 ccmn_io_ccb_bld3 4 cdisk_strategy 5 voliostart 6 volstrategy0 7 volstrategy 8 PRvolstrategy 9 spec_strategy 10 call_disk 11 bs_startio 12 bs_bflush 13 bs_bfdmn_flush_bfrs 14 msfs_mntflushbuf 15 mntflushbuf 16 boot 17 panic 18 afault_trap 19 _XentUna 20 simple_lock 21 csq_lateral 22 runq_run 23 netisr_thread PROBLEM: (76224) (PATCH ID: OSF425-1031) ******** This patch corrects a problem where a directory entry may be attempted to be changed to "." and the code checks for this prevents it from happening. PROBLEM: (BCGM32243) (PATCH ID: OSF425-1065) ******** This fixes a "u_anon_free: page busy" panic. An example stack trace: panic("u_anon_free: page busy") u_anon_free() u_anon_unmap() u_map_delete() vm_map_remove() vm_deallocate() procfs_read() vn_read() rwuio() read() syscall()