PROBLEM: (HPXQ43C4D, TKTR52185, QAR 46016) (Patch ID: OSF375-055) ******** This patch fixes some hangs that may occur after the message "syncing disks..." is printed when the system panics. When these hangs occur, the completion of the "syncing disks..." message - the word "failed" or "done" does not get printed, and the system does not take a dump. In addition to fixing these known hangs, a timout mechanism is added to the "syncing disks" logic that will improve the reliability of getting a dump by using the system clock to break out of the "syncing disks" path and take a dump if no progress is being made on reducing the number of buffers to be flushed. The numbers printed periodically between the "syncing disks..." and "done" messages are the number of buffers left to flush. This patch also makes it more likely that AdvFS buffers will be flushed to disk during the "syncing disks..." processing after a system panic. There is still no guarantee that writes in progress at the time of a panic will be completed. PROBLEM: (QAR 48680) (Patch ID: OSF375-360070-2) ******** This patch enables the latest Informix KAIO functionality. The patch should be installed by Informix customers using the Informix 7.20.UC4 release. The Informix defect number 40041 regarding KAIO is fully addressed by this patch. The patch is required when this message appears, followed by a core dump with the SIGABRT signal: Internal AIO consistency error: No fork for group completion. Aborting. PROBLEM: (HPXQ87202, QAR 49448, QAR 49474, QAR 49475, QAR 49553 ******** (Patch ID: OSF375-360076-1) This patch fixes a problem in which the the lastcomm accounting command doesn't print the "S" flag at appropriate times. This patch also improves the performance of lastcomm. The problem was that the kernel did not properly update the accounting field that prints the "S" flag. The "S" flag should be printed for each command that is run with an effective user id of 0. Commands that are set-user-id to root, will print the "S" flag. Also, commands that are executed by root, but are not set-user-id, will print the "S" flag. Therefore, when "S" is printed from lastcomm for a certain command, it means that the user had root privileges at some time during the execution of the command. The algorithm used by lastcomm has been enhanced to improve its performance. PROBLEM: (MCPM94D74, QAR 49067) (Patch ID: OSF375-360085) ******** Fixes system crash when setting the date for SMP systems. A representative stack trace follows: panic("resettodr: cpu not master") ["../../../../src/kernel/bsd/subr_prf.c":753 ,] resettodr() ["../../../../src/kernel/arch/alpha/clock.c":322,] setthetime() ["../../../../src/kernel/bsd/kern_time.c":543,] settimeofday() ["../../../../src/kernel/bsd/kern_time.c":499,] PROBLEM: (MGO102628,MGO102687,QAR 51439) (Patch ID: OSF375-365050) ******* When debugging multithreaded applications with Ladebug, debugging sessions may hang due to a bug in procfs (i.e., /proc filesystem). A simple way to reproduce the problem is to set a breakpoint in separate threads, run the application, change the thread focus to a thread other than the one which took the breakpoint, and to single-step. Under these circumstances, the debugger does not return to the debugger prompt and the debugging session effectively hangs. At this point, ps output simply indicates that the debugger and the debuggee are sleeping interruptibly. However, when a SIGKILL is sent to the debuggee, the affected threads o in the debugged process enter an uninterruptible sleep ('U' state in the ps listing). The traced process is now unkillable. PROBLEM: (QAR 50697,MGO102332,FNO100130) (Patch ID: OSF375-360087) ******** This patch fixes a number of problems relating to signals and POSIX 1003.1b timers in multithreaded programs running on multiprocessor systems. These problems can result in missed timer-expiration signals and system crashes. These issues involve synchronizing timer creation, timer deletion, and timer reset within multithreaded programs. Two distinct crashes are typical of the problems. Here's a sample of the first crash, a signal panic: panic (cpu 0): psig: catch not set With the following stack trace: > 0 boot 1 panic 2 psig 3 syscall 4 _Xsyscall A sample of the second crash is shown in the following example: from vmcore.3 : . . . simple_lock: time limit exceeded . . . pc of caller: 0xfffffc000024a5a4 lock address: 0xfffffc003d93b210 current lock state: 0x000000000043af85 (cpu=0,pc=0xfffffc000043af84,busy) . . . panic (cpu 2): simple_lock: time limit exceeded While a stack trace would show: kernel stack of CPU 0 > 0 boot 1 panic 2 event_timeout 3 simple_lock_miss 4 netisr_timeout 5 softclock_scan 6 lwc_schedule 7 thread_preempt 8 boot 9 panic 10 cpu_ip_intr 11 _XentInt 12 swap_ipl_preempt_check 13 wanTimerSysTick . . . kernel stack of CPU 1 > 0 stop_secondary_cpu ... 1 panic : 2 cpu_ip_intr : THIS PART OF THE KERNEL STACK 3 _XentInt : IS VERY TYPICAL FOR THIS CLASS 4 sigq_enqueue_tail : OF CRASHES. 5 psignal_internal : 6 psx4_tod_expire_sig ..: 7 psignal_lwc 8 lwc_schedule 9 do_preemption 10 simple_unlock_preempt 11 sigwaitprim 12 syscall 13 _Xsyscall . . . kernel stack of CPU 2 > 0 stop_secondary_cpu 1 panic 2 event_timeout 3 xcpu_puts 4 printf 5 panic 6 simple_lock_fault 7 simple_lock_time_violation 8 psx4_set_todtimer 9 syscall 10 _Xsyscall . . . kernel stack of CPU 3 > 0 stop_secondary_cpu 1 panic 2 cpu_ip_intr 3 _XentInt 4 swap_ipl_preempt_check 5 netisr_thread 6 wanTimerTick . . . This patch closes MP race conditions for multithreaded use of POSIX timers and signals. PROBLEM: (GOZ100707,MCPM777CC,QAR 47889,48876) (Patch ID: OSF375-370048) ******** This patch fixes a problem that occurs on AlphaServer 8200 and 8400 systems when a processor fails to restart after a user halts the system by entering "Control-P Control-P" and then typing "continue" on the console. This patch requires running firmware version 4.8-6 or later. This patch also fixes a problem where the pset_info and psradm commands fail to correctly report that a CPU is shut down. PROBLEM: (QAR 50693, QAR 49421) (Patch ID: OSF375-350372) ******** This patch corrects a problem with the exec() system function. A shell script that has "#! " as the first line of the script, invokes the program but does not set the effective user id for the execution of the program. PROBLEM: (HPAQ31FP3,MCPM40M9Q,ZPOB42573) (Patch ID: OSF375-069) ******** Fixes a panic that prints "delete_pv_entry: mapping not in pv_list". A typical stack trace is: 5 panic("delete_pv_entry: mapping not in pv_list") 6 delete_pv_entry() [src/kernel/arch/alpha/pmap.c] 7 pmap_enter() [src/kernel/arch/alpha/pmap.c] 8 kmem_stack_alloc() [src/kernel/vm/vm_kmap.c] 9 stack_alloc() [src/kernel/kern/thread.c] 10 thread_create_internal() [src/kernel/kern/thread.c] 11 procdup() [src/kernel/vm/vm_unix.c] 12 newproc() [src/kernel/bsd/kern_fork.c] 13 fork1() [src/kernel/bsd/kern_fork.c] 14 fork() [src/kernel/bsd/kern_fork.c] 15 syscall() [src/kernel/arch/alpha/syscall_trap.c] 16 _Xsyscall() [src/kernel/arch/alpha/locore.s] PROBLEM: (QAR 42473) (Patch ID: OSF375-069) ******** Fixes a panic that prints "pmap_dup: level3 PTE not valid". A typical stack trace is: 1 panic("pmap_dup: level3 PTE not valid") 2 pmap_dup() [src/kernel/arch/alpha/pmap.c] 3 vm_dup_va() [src/kernel/vm/vm_kern.c] 4 alloc_context() [src/kernel/io/dec/ws/interg.c] 5 interg_ioctl() [src/kernel/io/dec/ws/interg.c] 6 wsioctl() [src/kernel/io/dec/ws/ws_driver.c] 7 spec_ioctl() [src/kernel/vfs/spec_vnops.c] 8 vn_ioctl() [src/kernel/vfs/vfs_vnops.c] 9 ioctl_base() [src/kernel/bsd/sys_generic.c] 10 ioctl() [src/kernel/bsd/sys_generic.c] 11 syscall() [src/kernel/arch/alpha/syscall_trap.c] 12 _Xsyscall() [src/kernel/arch/alpha/locore.s] PROBLEM: (QAR 51581) (Patch ID: OSF375-069) ******** Fixes a panic that prints "kernel memory fault". A typical stack trace is: 1 panic("kernel memory fault") 2 trap() [src/kernel/arch/alpha/trap.c] 3 _XentMM() [src/kernel/arch/alpha/locore.s] 4 bcopy() [src/kernel/arch/alpha/fastcopy.s] 5 volkiocopyin() [src/kernel/lsm/dec/kiosubr.c] 6 volsio_stabilize() [src/kernel/lsm/common/stable.c] 7 vol_mv_write_start() [src/kernel/lsm/common/mvio.c] 8 volkiostart() [src/kernel/lsm/common/kiostart.c] 9 volstrategy() [src/kernel/lsm/dec/voldev.c] 10 physio() [src/kernel/ufs/ufs_physio.c] 11 physiock() [src/kernel/lsm/dec/Space.c] 12 volrdwr() [src/kernel/lsm/dec/voldev.c] 13 volwrite() [src/kernel/lsm/dec/voldev.c] 14 spec_write() [src/kernel/vfs/spec_vnops.c] 15 msfsspec_write() [src/kernel/msfs/osf/msfs_vnops.c] 16 vn_write() [src/kernel/vfs/vfs_vnops.c] 17 rwuio() [src/kernel/bsd/sys_generic.c] 18 write() [src/kernel/bsd/sys_generic.c] 19 syscall() [src/kernel/arch/alpha/syscall_trap.c] 20 _Xsyscall() [src/kernel/arch/alpha/locore.s] PROBLEM: (USG-04712) (Patch ID: OSF375-360101) ******** The patch fixes the corruption of core files produced by applications with 15 or more threads. The corrupted core file will show nonsensical or incomplete stack traces beyond the fifteenth thread. The register and local variable state of threads can also show incorrect values. PROBLEM: (Patch ID: OSF375-350438) ******** This patch fixes a problem in which panics will occur if an attempt is made to run a shell script residing on any filesystem mounted with the "noexec" option. The panic message is "kernel memory fault" and the kernel stack trace obtained from the resulting dump is of the following form: 0 boot 1 panic ("kernel memory fault") 2 trap 3 exec_setuid 4 common_exec 5 execve 6 syscall 7 _Xsyscall PROBLEM: (QAR 47628, QAR 45627, QAR 45069) (Patch ID: OSF375-365070) ******** This patch fixes an I/O queue corruption problem that occurs during normal shut down of SMP systems with AdvFS. PROBLEM: (ZPOB54022) (Patch ID: OSF375-365071) ******** This patch fixes a problem that may occur after a system panics. The system may hang when trying to do a crash dump. The problem is due to the system getting into a boot/panic loop. The following is an example of a typical stack trace: 1 panic("event_timeout: panic request") 2 event_timeout()["/src/kernel/arch/alpha/cpu.c":1005] 3 simple_lock_miss()["/src/kernel/arch/alpha/lockprim.s":1244] 4 re_flush()["/src/kernel/io/dec/eisa/re_driver.c":1220"] 5 drvr_flush()["/src/kernel/io/common/driver_support.c":2115"] 6 boot()["/src/kernel/arch/alpha/machdep.c":2525] 7 panic("event_timeout: panic request") 8 event_timeout()["/src/kernel/arch/alpha/cpu.c":1005"] 9 simple_lock_miss()["/src/kernel/arch/alpha/lockprim.s":1244] 10 re_flush()["/src/kernel/io/dec/eisa/re_driver.c":2115] 11 drvr_flush()[/src/kernel/io/common/driver_support.c":2115"] 12 boot()["/src/kernel/arch/alpha/machdep.c":2525] 13 panic("event_timeout: panic request") 14 event_timeout()["/src/kernel/arch/alpha/cpu.c":1005"] 15 simple_lock_miss()["/src/kernel/arch/alpha/lockprim.s":1244] 16 re_flush()["/src/kernel/io/dec/eisa/re_driver.c":2115] 17 drvr_flush()[/src/kernel/io/common/driver_support.c":2115"] 18 boot()["/src/kernel/arch/alpha/machdep.c":2525] PROBLEM: (MCSM80GC5) (Patch ID: OSF375-350448) ******** This patch fixes a problem that occurs when starting up a system that is running the auditing subsystem and the performance manager. The system panics with the following error message: kernel memory fault A sample stack trace is shown in the following example: 0 thread_block() 1 thread_preempt() 2 boot() 3 panic(s = 0xfffffc000060b280 = "kernel memory fault") 4 trap() 5 _XentMM() 6 syscall() 7 _Xsyscall() PROBLEM: (MCPM94D74, QAR 49067) (Patch ID: OSF375-119) ******** This patch fixes a system crash when setting the date for SMP systems. A representative stack trace follows: panic("resettodr: cpu not master") ["../../../../src/kernel/bsd/subr_prf.c":753 ,] resettodr() ["../../../../src/kernel/arch/alpha/clock.c":322,] setthetime() ["../../../../src/kernel/bsd/kern_time.c":543,] settimeofday() ["../../../../src/kernel/bsd/kern_time.c":499,] PROBLEM: (MGO103243) (Patch ID: OSF375-120) ******** This patch fixes a kernel memory fault in the u_anon subsystem. The stack trace on the failing machine may be similar to the following example (the panic may also come from else where in the u_anon subsystem): _XentMM() a_anon_getpage() u_anon_fault() u_map_fault() vm_fault() trap() _XentMM() PROBLEM: (MGO103242) (Patch ID: OSF375-135) ******** This patch fixes a "simple lock timelimit exceeded" panic from the procfs subsystem. PROBLEM: (CLD EVT102471, QAR 45083) (Patch ID: OSF375-150) ******** This patch corrects a kernel memory fault panic in routine pmap_pt_access(). A typical stack trace follows: > 0 stop_secondary_cpu(do_lwc = 0) ["../../../../src/kernel/arch/alpha/cpu.c": 1 panic(s = 0xfffffc00006b4578 = "event_timeout: panic request") ["../../../ 2 event_timeout(func = 0xfffffc000027df90, arg = 0xfffffc00008892e8, timeout 3 xcpu_puts(s = 0xfffffc000070ea00, prfbufp = 0xfffffc00008892e8) ["../../.. 4 printf(va_alist = -4398039748776) ["../../../../src/kernel/bsd/subr_prf.c" 5 panic(s = 0xfffffc00006b70e0 = "kernel memory fault") ["../../../../src/ke 6 trap() ["../../../../src/kernel/arch/alpha/trap.c":1457, 0xfffffc00004ea37 7 _XentMM(0x4, 0xfffffc00004fdc6c, 0xfffffc00006fea00, 0xfffffc0001520040, 0 8 pmap_pt_access(map = 0x400010002, v = 14123853069314699368, pte1p = 0xffff 9 pmap_clrmod_fow(phys = 18446739675775960960) ["../../../../src/kernel/arch 10 ubc_msync(0x0, 0xfffffc0009b87e00, 0x700000040, 0xfffffc0009b87e08, 0xffff 11 u_vp_msync(0x700000040, 0xfffffc0009b87e08, 0xfffffc0009b87e48, 0xfffffc00 12 u_map_control(0xfffffc00006f7ce0, 0xfffffc000677b500, 0xfffffc0000fbce40, 13 msync(0xfffffc0000fbce40, 0xfffffc00065f78c0, 0xfffffc0000000001, 0x0, 0xf 14 syscall(0x1, 0x0, 0x4c1ef31517bdc, 0x12007dca4, 0xd9) ["../../../../src/ke 15 _Xsyscall(0x8, 0x120080098, 0x14001ca20, 0x222000, 0x10000) ["../../../../ PROBLEM: (CLD UVO105826) (Patch ID: OSF375-151) ******** This patch fixes problems with missing/lost signals that can cause applications to hang. In particular, the DECss7 product may experience severe problems. The problem happens primarily with POSIX signals. PROBLEM: (QAR 59926) (Patch ID: OSF375-211) ******** This patch removes extraneous debug code. PROBLEM: (QAR 57579) (Patch ID: OSF375-215) ******** Asynchronous I/O can fail when the number of aio requests is allowed to exceed 64K. PROBLEM: (QAR 61638) (Patch ID: OSF375-238) ******** This patch fixes a problem with the way the ps utility collected CPU usage information. One effect of the problem was that processes run with nice values of 18 or greater had contention problems based on the incorrect CPU values.