PROBLEM: (QAR 61938, QAR 58566) (Patch ID: OSF435-425341) ******** 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: OSF435-013) ******** 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: OSF435-017) ******** 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: (QAR 56793) (Patch ID: OSF435-425302) ******** This patch corrects a potential problem in the handling of a ieee_get_state_at_signal(3) C-library call. PROBLEM: (65232) (Patch ID: OSF435-048) ******** Externally, the problem manifests itself as a "tb_shoot ack timeout" panic, although it can also result in a "simple_lock: time limit exceeded" panic. One of the CPUs in has quietly halted due to a kernel-stack-not-valid state, because a running thread on the CPU was interrupted by an IP interrupt which resulted in its stack's PTE's FOW (fault-on-write) bit being set. This is an invalid state since the next FOW (write) to the stack cannot be reported to the kernel for handling because the stack cannot be written to. Eventually another CPU will try to send another IP interrupt to the dead CPU, resulting in a "tb_shoot ack timeout", or perhaps a simple lock timeout if the dead thread was holding a lock. The panics also showed that in systems with memory holes, the upper memory regions memory containing the vm_page, pv_list_head and color buckets arrays were not being dumped. This makes debugging most VM-related bugs, most notably malloc corruption bugs, virtually impossible. PROBLEM: (SQO100495) (Patch ID: OSF435-425324) ******** This corrects a simple lock timeout problem in several vm_page routines. PROBLEM: (QAR 63741, BCSM80FG6) (Patch ID: OSF435-425441) ******** This patch fixes a problem where a file system is busy when trying to unmount it. PROBLEM: (QAR 56172, QAR 55808) (Patch ID: OSF435-010) ******** This patch corrects a problem where we need to hold file references on raw device accesses. The patch uses locks on references and the unreferences so the file won't be prematurely closed. This problem could result in process hangs. PROBLEM: (QAR 59849, QAR 58696) (Patch ID: OSF435-011) ******** This patch fixes a problem when a processor is commanded to stop during a heavy load but does not actually halt. PROBLEM: (BCGM70W61, UVO105916) (Patch ID: OSF435-014) ******** 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 62611) (Patch ID: OSF435-425357) ******** This patch corrects a potential boot panic problem by limiting the size of the bufcache. PROBLEM: (QAR 55421, QAR 55783) (Patch ID: OSF435-425365) ******** 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: (BRO101153,BCGM40N88,QAR 59145) (Patch ID: OSF435-029) ******** 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 Also: Allow automount's "intercept points" to change from symlinks to directories. Otherwise automount would have trouble exiting, and future references to the intercept points would hang. PROBLEM: (HPAQ51CP0, HPAQ41QK2) (Patch ID: OSF435-036) ******** This srequest fixes two separate problems which are: 1) This patch fixes a problem where a user application may receive an EIO error back from an fsync() call. 2) 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: (MGO103472) (Patch ID: OSF435-039) ******** This srequest fixes two separate problems which are: 1) This corrects a performance problem with posix timers. 2) 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") 6 trap() 7 _XentMM() 8 sigsgdisp() 9 sigaction() PROBLEM: (MGO103843,MGO103768) (Patch ID: OSF435-053) ******** This patch corrects performance related problems. A system running low on free memory or showing heavy pagein activity will need this patch. PROBLEM: (QAR 61665) (Patch ID: OSF435-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: (57426, 57492, 57450, ECP EALC8003, 61553, BCGM501VR, HPAQ41HC8, 62831, 61388, 62617, 62299, 51568, HPAQ60W1F, 63703, 63686) (Patch ID: OSF435-020) ******** This patch fixes several problems: This patch fixes a problem with the chfsets command. When a root user exceeded the fileset quota (which root is allowed to do), the chfsets command reported negative values for the free and available blocks in the fileset. This patch fixes a problem with the AdvFS fs_write routine, which would mishandle partial writes after detecting an error. Now when the fs_write routine detects an error, it breaks out of the write page loop and decides either to exit immediately with an error (if no bytes have been written) or to commit the partial changes to disk and return the number of successfully-written bytes. This patch provides performance improvements for writes to AdvFS files which have had Atomic Write Data Logging enabled on them. Write performance improvements are for O_SYNC opens of such files and are realized for both local and NFS access. This patch fixes a problem with messages in system logs that reported AdvFS user and group quota limits. The messages were unclear: the user could not determine from them which users or groups were reaching the quota limits. Part of the problem was the term "inode," which is not an AdvFS entity. The term was replaced in the messages with "file." This patch fixes a problem in AdvFS, which causes a system panic when a truncate operation is performed on a file. The panic is: log half full Here's the stack trace: > 0 boot() ["../../../../src/kernel/arch/alpha/machdep.c":1890, ] 1 panic(s = 0xffffffff8bc3af98 = "release_dirty_pg: log half full") ["../../../../src/kernel/bsd/sub r_prf.c":834, 0xfffffc000028c024] 2 advfs_sad() ["../../../../src/kernel/msfs/bs/bs_misc.c":556, ] 3 release_dirty_pg() ["../../../../src/kernel/msfs/bs/ms_logger.c":2005,] 4 lgr_writev_ftx() ["../../../../src/kernel/msfs/bs/ms_logger.c":1576, ] 5 log_donerec_nunpin()["../../../../src/kernel/msfs/bs/ftx_routines.c":2825, ] 6 ftx_done_urdr() ["../../../../src/kernel/msfs/bs/ftx_routines.c":1246, ] 7 ftx_done_u() ["../../../../src/kernel/msfs/bs/ftx_routines.c":1060, ] 8 bmt_link_mcells() ["../../../../src/kernel/msfs/bs/bs_bmt_util.c":3770, ] 9 odm_create_xtnt_map() ["../../../../src/kernel/msfs/bs/bs_extents.c":1707, ] 10 dealloc_stg() ["../../../../src/kernel/msfs/bs/bs_stg.c":6388, ] 11 remove_stg() ["../../../../src/kernel/msfs/bs/bs_stg.c":5897, ] 12 stg_remove_stg_start() ["../../../../src/kernel/msfs/bs/bs_stg.c":5743, ] 13 bf_setup_truncation() ["../../../../src/kernel/msfs/bs/bs_access.c":4189, ] 14 msfs_setattr() ["../../../../src/kernel/msfs/osf/msfs_vnops.c":1725, ] 15 vtruncate() ["../../../../src/kernel/vfs/vfs_syscalls.c":3488, ] 16 ftruncate() ["../../../../src/kernel/vfs/vfs_syscalls.c":3418, ] 17 syscall() ["../../../../src/kernel/arch/alpha/syscall_trap.c":627, ] 18 _Xsyscall() ["../../../../src/kernel/arch/alpha/locore.s":1409, ] This patch fixes the following problems in AdvFS: 1.) AdvFS does not return an error when a user opens a file in O_SYNC mode and power is lost on the disk drive. 2.) A locking error in the AdvFS fs_write() routine. This patch fixes a problem in AdvFS locking code which causes the following panic: kernel memory fault The stack trace is listed below: 0 boot() 1 panic() 2 trap() 3 _XentMM() 4 bs_pinpg_clone() 5 bs_pinpg_ftx() 6 rbf_pinpg() 7 alloc_mcell() 8 bmt_alloc_prim_mcell() 9 new_mcell() 10 rbf_int_create() 11 rbf_create() 12 fs_create_file() 13 msfs_mkdir() 14 mkdir() 15 syscall() 16 _Xsyscall() This patch fixes two AdvFS problems: 1. An error message was misleading when a DIGITAL UNIX Version 4 system attempted to access a file domain created by DIGITAL UNIX Version 5. 2. A state field in an AdvFS data structure was initialized, but not maintained. PROBLEM: (QAR 61441,57532) (Patch ID: OSF435-025) ******** 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. Threads which perform asynchronous I/O may modify the state of the associated buffer after the request gets enqueued onto the lazy queue. If the lazy queue gets bypassed, then it is possible for the I/O to complete before the issuing thread modifies the buffer. Once the I/O completes, the buffer could be reassigned. If the issuing thread still attempts to modify the buffer state, this can lead to a disk inconsistency and possibly a panic. PROBLEM: (QAR 66693) (Patch ID: OSF435-068) ******** This patch must be installed to allow the X.25 WAN layered product to run on DIGTAL UNIX V4.0E. PROBLEM: (Patch ID: OSF435-080) ******** This patch corrects a system performance problem on a freshly booted AlphaServer 4000 and similar systems. PROBLEM: (HPAQ5152N) (Patch ID: OSF435-006) ******** 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 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: (CLDs HPAQ200SX, MCPM415SF, HPAQ914NT QAR 45528) (Patch ID: OSF435-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: OSF435-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: (CLD HPAQ8177M, QAR 63556) (Patch ID: OSF435-425463) ******** 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: (BCPM9124T, QAR 65217) (Patch ID: OSF435-425467) ******** 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 54441,QAR 60576) (Patch ID: OSF435-425491) ******** 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 66747, SSRT0603U) (Patch ID: OSF435-425506) ******** 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: (FNO100208) (Patch ID: OSF435-425552) ******** 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: (QARS 64229 64563) (Patch ID: OSF435-425569) ******** 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: (QAR 65103, CLD MGO103808) (Patch ID: OSF435-047) ******** This patch fixes some rounding bugs in the kernel floating point exception handler and some inaccuracies in the kernel sqrt instruction emulator. The exception handler is invoked to complete some operations on IEEE special values like infinities or denormalized values. In rare cases, the handler rounded some denormalized results incorrectly. For example, 2.91e-11 (hex 2e000001) * 2.02e-28 (hex 117ffffe) should yield the denormalized value 5.877e-39 (hex 00400000) but instead it would incorrectly produce 1.175e-38 (hex 00800000). The sqrt emulator is invoked when EV6 sqrt instructions are executed on EV4 or EV5 systems. The emulator treated a sqrttsuid instruction as if it were single precision and so produced less than half the proper result bits. Also, in rare cases, there was a problem with incorrect rounding. For example, when rounding to positive infinity and taking the sqrt of the value just less than 1.0, the emulator would incorrectly return 0.5 instead of the correct answer 1.0. PROBLEM: (QAR 68123, QAR 67795) (Patch ID: OSF435-103) ******** This patch fixes a problem where the system crashes with the following error message: lw_remove: light weight wiring(s) found PROBLEM: (QAR 66337) (Patch ID: OSF435-108) ******** This patch fixes a problem that causes a panic to occur at boot time if the system has a large boot time memory requirement and only a portion of memory has been tested. Without the patch installed, the system will panic with the following message if the boot time memory requirements deplete the pool of pre-tested memory: panic: get_first_free: no free memory! The patch corrects the problem by allowing the system to use untested memory if the boot time memory requirements deplete the pool of pre-tested memory. PROBLEM: (BCGM20L71) (Patch ID: OSF435-112) ******** 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: OSF435-114) ******** 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: (CLD UVO106265 QAR 67541) (Patch ID: OSF435-120) ******** This corrects a "simple_lock: time limit exceeded" panic in softclock_scan(). 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: (QAR 68542) (Patch ID: OSF435-122) ******** 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: (CLD MGO104010) (Patch ID: OSF435-123) ******** The problem this patch fixes is that the OSF-USR LMF license never decrements when a user logs out. This problem only occurs when the default window manager is xdm instead of cde and the user logs into and out of the console terminal running xdm. It will not occur if the system is running with an unlimited OSF-USR license. The problem can be recreated as follows: o Login as root. Type the following lmf command to see the Active count for OSF-USR. # lmf list |egrep 'OSF-USR|Active' Product Status Users: Total Active OSF-USR active 4 0 # o With xdm as the default window manager, log into the console as a non-root user process. o At the previous root window, retype the lmf command to see the incremented OSF-USR Active count. # lmf list |egrep 'OSF-USR|Active' Product Status Users: Total Active OSF-USR active 4 1 # o Logout the non-root user process. o At the previous root window, retype the lmf command to see if the OSF-USR Active count failed to decrement. # lmf list |egrep 'OSF-USR|Active' Product Status Users: Total Active OSF-USR active 4 1 # o With this patch, when the non-root user logs out, the lmf command will show the properly decremented OSF-USR Active count. # lmf list |egrep 'OSF-USR|Active' Product Status Users: Total Active OSF-USR active 4 0 # PROBLEM: (QAR 66856) (Patch ID: OSF435-124) ******** This patch fixes a standards compliance issue with the sqrt instruction emulator. The sqrt emulator is invoked when EV6 sqrt instructions are executed on EV4 or EV5 systems. Without this patch, the sqrt emulator will fail to raise a signal when operating on IEEE signaling NaNs. PROBLEM: (CLD ALC-08214) (Patch ID: OSF435-140) ******** 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 daemons or user programs may preempt the netisr thread and hang network activity. PROBLEM: (SSRT0583Q) (Patch ID: OSF435-144) ******** 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: (CLD ALC-08248, QAR 69130, QAR 69348) (Patch ID: OSF435-145) ******** 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: (BRO101278) (Patch ID: OSF435-146) ******** This is to correct a problem where a signal is delievered, but not responded to by the target process. PROBLEM: (CLD ISO100435) (Patch ID: OSF435-015) ******** This patch fixes a problem in which sem_wait() does not get interrupted by a SIGCHLD signal if the program is compiled/linked -pthread. PROBLEM: (EALC9003) (Patch ID: OSF435-152) ******** This patch enhances the behavior of the mlockall() system call. mlockall() will now make a process unswappable. PROBLEM: (BCPMC1GPQ) (Patch ID: OSF435-155) ******** This is to fix a panic of "get_color_bucket: empty buckets" when the sysconfig attribute "private-cache-percent" is non-zero. PROBLEM: (QAR 65580) (Patch ID: OSF435-157) ******** This patch fixes a prior regression that prevented full crash dumps from working properly. PROBLEM: (QAR 63936, QAR 65766, QAR 65767) (Patch ID: OSF435-042) ******** 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 PROBLEM: (NONE) (Patch ID: OSF435-052) ******** 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: (QAR 65598) (Patch ID: OSF435-083) ******** 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: (QAR 59329) (Patch ID: OSF435-085) ******** 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: (QAR 66499) (Patch ID: OSF435-092) ******** 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: (GOZ100546, GOZ100949, QAR 51038) (Patch ID: OSF435-425409) ******** This patch fixes a problem where NFS does not update mtime and atime for special files and named pipes. PROBLEM: (TKTRB0985) (Patch ID: OSF435-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: (ISO100472) (Patch ID: OSF435-105) ******** This fixes a panic with the following panpaic string: "pgmv: session leader attempted setpgrp" PROBLEM: (HPAQC032X/QAR 66952) (Patch ID: OSF435-121) ******** 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: (QAR 59953, QAR 59419) (Patch ID: OSF435-425249) ******** 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: (BCGM703PQ,BCPM70WFJ,HPAQ920JJ,BCGMC0NZ8,HPAQA225S,BCGM210JL, HPAQ20Z8V) (Patch ID: OSF435-150) ******** 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: (HPAQC032X/QAR 66952) (Patch ID: OSF435-121) ******** 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: (HPAQ41J00, QAR 64037) (Patch ID: OSF435-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: OSF435-113) 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: OSF435-113) 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: OSF435-113) 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: (BCGMC1JRS) (Patch ID: OSF435-151) ******** 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: (QAR 65635) (Patch ID: OSF435-110) ******** This patch fixes a problem when a thread issues a resume request against another thread before it has actually suspended, the target thread is incorrectly suspended. At times it may suspend indefinitely. This patch implements a "pending resume" semantics. When a thread issues a resume request against another thread before it has suspended, a resume is now posted against the target thread so that when/if it does calls suspend it will simply clear the state and continue. PROBLEM: (QAR 68161) (Patch ID: OSF435-110) ******** This patch fixes a problem where the nxm_get_state() system call did not return a failure status if a target thread is not blocked at the time the call is executed. nxm_get_state() now returns KERN_NOT_RECEIVER when this condition occurs. PROBLEM: (Patch ID: OSF435-079) ******** This patch provides platform support for software interleaving on the AlphaServer 4000 family of platforms. PROBLEM: (none.) (Patch ID: OSF435-160) ******** 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: (HPAQ30BCD) (Patch ID: OSF435-163) ******** This patch fixes a kernel memory fault from socket code. The kernel memory fault results from failing to get a lock on a list of threads which have requested resources on a socket. The stack will contain: _XentMM simple_lock select_wakeup sowakeup soisconnected PROBLEM: (QAR 46648 QAR 70765>) (Patch ID: OSF435-172) ******** This patch fixes a system hang in which there is a large number of pending ioctl's on the streams queue. PROBLEM: (CLD BCSM30WLD ,QARS 69170 70101) (Patch ID: OSF435-192) ******** This patch fixes a problem that causes system panics when thread_swappable is called with the current_thread as the target thread, when the thread is about to be swapped out. PROBLEM: (BCGM40GGH, 71213) (Patch ID: OSF435-193) ******** 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: OSF435-206) ******** 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: OSF435-209) ******** 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: OSF435-213) ******** This patch fixes a problem that causes the Tru64 UNIX Version 5.0 update install procedure to exit with core dumps and /sbin/loader failures on a system. PROBLEM: (QAR 71062, QAR 71532) (Patch ID: OSF435-215) ******** This patch fixes a problem with CDFS. Data corruption occurs when reading beyond the end of a partition. PROBLEM: (BRO101307 & BCSM11QV2 ,QAR 70038) (Patch ID: OSF435-224) ******** This patch fixes a problem in the module core() that can cause a panic with the message: vrele: bad ref count. The stack trace may look like the following example: 0 stop_secondary_cpu() 1 panic("event_timeout: panic request") 2 event_timeout() 3 xcpu_puts() 4 printf() 5 panic("vrele: bad ref count") 6 vrele() The problem occurs if a set UID, or GID, program attempts to dump core in a directory that already contains a symbolic link with the name "core", and if the link points to a non-existent path. PROBLEM: (HPAQ50FLC, QAR 71826, QAR 71891, QAR 68458) (Patch ID: OSF435-228) ******** This patch fixes 2 separate problems: 1) Panic in the kernel with the following error message: simple_lock: time limit exceeded Stack trace is as follows: panic simple_lock_fault simple_lock_time_violation pmap_ssm_enter u_ssm_fault u_map_fault vm_fault ... 2) A panic occurs when booting kernel interactively and setting the memlimit. The panic error message is as follows: kernel memory fault PROBLEM: (QAR 69261, QAR 69769) (Patch ID: OSF435-240) ******** 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 65634) (Patch ID: OSF435-243) ******** This patch improves UFS performance by no longer prematurely writing single pages. PROBLEM: (BRO101338 BRO101359) (Patch ID: OSF435-244) ******** 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: OSF435-251) ******** 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: (MGO104022) (Patch ID: OSF435-252) ******** Applications using fcntl() system calls may appear to hang. PROBLEM: (MGO09365A,BCGM41MGB) (Patch ID: OSF435-253) ******** This patch fixes "simple_lock: time limit exceeded" panics. PROBLEM: (QAR 71802, QAR 72427, CLD INT-08869) (Patch ID: OSF435-261) ******** This is a patch for a Compaq AlphaServer DS20. A fix has been made to the handling of power supply, temperature, and fan events. PROBLEM: (QAR 72129, CLD HPAQ500L1) (Patch ID: OSF435-266) ******** This problem fixes an nfs/ufs/vm deadlock. While serving a client, the system running ASE/DT as an NFS server can hang with deadlock. PROBLEM: (QAR 72626, CLD BCPM50LZC) (Patch ID: OSF435-267) ******** 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: (QAR 63384) (Patch ID: OSF435-275) ******** 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: (MGO104025) (Patch ID: OSF435-277) ******** This patch fixes a system hang condition. All NFS related services may deadlock. PROBLEM: (STLB42227) (Patch ID: OSF435-284) ******** 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: OSF435-170) ******** 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: OSF435-170) ******** 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: OSF435-170) ******** This patch fixes a 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: OSF435-232) ******** 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 65033, QAR 61856, QAR 64040, SSRT0563U) (Patch ID: OSF435-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: (CLD HPAQC08NV) (Patch ID: OSF435-425592) ******** 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: (QAR 59367) (Patch ID: OSF435-425289) ******** This patch adds automatic detection of a cdfs file system for the mount(8) command. PROBLEM: (QAR 62614) (Patch ID: OSF435-077) ******** 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 72971 CLD MGO104088) (Patch ID: OSF435-262) ******** 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: (HPAQ40343, HPAQ5062G,UVO20042) (Patch ID: OSF435-278) ******** 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" during the time that update is executing (a sync is occurring). PROBLEM: (QAR 65396 58440 58800) (Patch ID: OSF435-425494) ******** The output from the "vmstat -M" command does not correctly match the bucket numbers with the bucket indices. PROBLEM: (QAR 72410) (Patch ID: OSF435-287) ******** 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: OSF435-288) ******** 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: OSF435-294) ******** 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 70220>) (Patch ID: OSF435-303) ******** Use of mmap can sometimes result in data corruption. PROBLEM: (QARS 64531, 68748) (Patch ID: OSF435-310) ******** This patch improves nfs performance by avoiding an undesired cache invalidation that can have a big impact on NFS performance with huge files. PROBLEM: (QAR 58781, QAR 64371) (Patch ID: OSF435-313) ******** 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 73918) (Patch ID: OSF435-322) ******** This patch fixes a problem where AS1200 systems with more than 3 pairs of memory displays the following warning message on the console during boot: "pmap_get_align: Unaligned memory hole found... Please reset the system to clear any previous memlimit" PROBLEM: (BCPM81CNT/BCPM80N9B) (Patch ID: OSF435-325) ******** 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: OSF435-326) ******** 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 73589) (Patch ID: OSF435-328) ******** Because of a problem involving signal delivery, multithreaded applications can exhibit very poor performance or may even hang. PROBLEM: (QAR 67188, QAR 67164) (Patch ID: OSF435-330) ******** 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: (MGO44815A) (Patch ID: OSF435-336) ******** 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: (QAR 74449) (Patch ID: OSF435-348) ******** 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: OSF435-349) ******** 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: OSF435-354) ******** 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: (ALC-08332) (Patch ID: OSF435-361) ******** This fixes a "simple_lock: hierarchy violation" panic from sigq_abort(). PROBLEM: ('QAR 74536') (Patch ID: OSF435-383) ******** This patch fixes a system panic on multi-process systems (approximately 12 cpus) with large memory (128GB). The system can panic with panic: lock time on vm_page_free_lock PROBLEM: (HPAQ70DBD) (Patch ID: OSF435-393) ******** 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: ('QAR 73124, QAR 71118') (Patch ID: OSF435-396) ******** This patch fixes a problem where partitioned turbolasers return incorrect cpu data for cpus that are not in the partition. PROBLEM: ('QAR 74959') (Patch ID: OSF435-401) ******** This patch fixes a problem where ubc_msync() may not flush out all the pages in the requested range. PROBLEM: (BCSMA1923/75276) (Patch ID: OSF435-414) ******** This patch fixes var adm messages from truncation on larger configurations by raising the default size (4096) of 'msgbuf_size' to 8192. PROBLEM: (DEKQC0005, STLNC4615) (Patch ID: OSF435-424) ******** This patch fixes a problem where systems with the BL13 patch kit installed would run low on kernel memory after process accounting had been running for a while. PROBLEM: (QAR 67156,QAR 61985,QAR 66890) (Patch ID: OSF435-332) ******** 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 away)) ["../../../../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_frame = 0xffffffff8cfe3 538) ["../../../../src/kernel/arch/alpha/trap.c":1877, 0xfffffc0000598af8] 10 _XentMM(0x0, 0xfffffc00003fcfb4, 0xfffffc00006d5af0, 0xffffffff8096e008, 0x1) ["../../../../src/kernel/arch/alpha/locore.s":2091, 0xfffffc000058d594] 11 bs_get_bf_xtnt_map(0xffffffff8cfe37a8, 0xfffffc00021f4008, 0xfffffc0001fbfc08, 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, 0xfffffc00d86ec908) ["../../../../ src/kernel/arch/alpha/locore.s":1736, 0xfffffc000056aed4] 8 imm_page_to_sub_xtnt_map(0x0, 0xfffffc00003eb6c4, 0xfffffc00007cb0e0, 0x5cb0, 0xfffffc00d86ec90 8) ["../../../../src/kernel/msfs/bs/bs_inmem_map.c":2290, 0xfffffc00003eb6c0] 9 x_page_to_blk(0xfffffffeae0bf548, 0x5cb0, 0xfffffffe00c5d3f0, 0x800100000001, 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, 0xfffffc00003c7a80] 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, 0xfffffc00a2ef8800, 0x1) ["../../../../ src/kernel/sec/sec_acl.c":906, 0xfffffc000024f7c4] 16 sp_vnaccess(0xfffffc000024f1bc, 0xfffffc00a2ef8800, 0x1, 0x1, 0xfffffc000043d308) ["../../../.. /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, 0xfffffffeae0bf840, 0xfffff ffeae0bf838) ["../../../../src/kernel/vfs/vfs_vnops.c":614, 0xfffffc00005271b4] 19 copen(0x0, 0x3, 0xfffffc00d1f3b880, 0xfffffc008bc2d220, 0xfffffffeae0bf8e0) ["../../../../src/k ernel/vfs/vfs_syscalls.c":2420, 0xfffffc000051a900] 20 open(0xfffffc00d1f3b880, 0xfffffc008bc2d220, 0xfffffffeae0bf8e0, 0x12, 0xfffffc0000573d28) [".. /../../../src/kernel/vfs/vfs_syscalls.c":2347, 0xfffffc000051a7cc] PROBLEM: (QAR 74109 69359,cld alc-08485) ******** This patch fixes a problem that could result in a incorrect scheduling of threads when they were dispatched from the idle state. Prior to this fix, when a thread was woken it was placed in the processor next_thread field as the next thread to run. If multiple threads were awoken, the first thread could be placed in the in the processor next_thread field and then could lose it's priority because the next thread to awaken could subsequently be placed in the processor next_thread field. PROBLEM: ('QAR 73644') (Patch ID: OSF435-374) ******** 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: ('QAR 51449, QAR 70650') (Patch ID: OSF435-353) ******** 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 72787) (Patch ID: OSF435-241) ******** 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: (SSRT0536U) (Patch ID: OSF435-003) ******** 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: OSF435-004) ******** A correction to the port allocation code now prevents a user from allocating port zero if ipport_userreserved is set to 65535. PROBLEM: (QAR 66763, QAR 67104) (Patch ID: OSF435-089) ******** This patch fixes a problem where Digital UNIX systems may panic with one of the following strings while attempting to unlock a socket. "Unaligned kernel space access from kernel mode" "kernel memory fault" A typical stack trace is as follows: 0 boot() 1 panic() 2 trap() 3 _XentMM() 4 sounlock() 5 tcp_input() 6 ipintr() 7 netisr_thread() PROBLEM: (SSRT0595U) (Patch ID: OSF435-118) ******** 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: OSF435-127) ******** This patch fixes a problem where resets are seen due to proxy packets getting into the ipintrcacheaddr cache. PROBLEM: (67968) (Patch ID: OSF435-138) ******** This patch is for AOL systems running Inktomi code. It provides enabling hooks for Inktomi caching server code. PROBLEM: (DEKB20145) (Patch ID: OSF435-165) ******** 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: OSF435-167) ******** 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: (BCGM31BPT) (Patch ID: OSF435-174) ******** This patch fixes a problem on systems running screend where TCP/IP fragments are being dropped. PROBLEM: (None) (Patch ID: OSF435-289) ******** PROBLEM: (CLD EVT102855, QAR 73939) (Patch ID: OSF435-340) ******** 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: (QAR 73901) (Patch ID: OSF435-371) ******** This patch fixes a TCP performance problem if the TCP window scale option is turned off when using the HIPPI interface. PROBLEM: (BCGMB0J3G, HPAQB1T92, BCPMB1K80, BCPMB1RJ5, QAR 75415) (Patch ID: OSF435-398) ******** This patch fixes a system panic: "tcphdr too big". The problem is caused when the SACK option field exceeds 48 bytes and the length adjustment code, found in tcp_output(), calculates a negtive length. A typical stack trace will look as follows: panic tcp_output tcp_input ipintr netisr_thread PROBLEM: (QAR 75381) (Patch ID: OSF435-412) ******** This patch consists of changes necessary for AV firewall 98 to pass ICSA certification. PROBLEM: (none) (Patch ID: OSF435-417) ******** This patch involves virtual mac addressing.