PROBLEM: (MGO09365A,BCGM41MGB) (Patch ID: OSF500-003) ******** This patch fixes "simple_lock: time limit exceeded" panics. PROBLEM: (HPAQ50FLC, QAR 71826, QAR 71891) (Patch ID: OSF500-004) ******** 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 ... PROBLEM: (QARS 71524 66356) (Patch ID: OSF500-007) ******** 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: (MGO104022) (Patch ID: OSF500-010) ******** This patch fixes a problem where applications using the fcntl() system calls may appear to hang. PROBLEM: (None) (Patch ID: OSF500-011) ******** System will panic with a "lock hierarchy violation" when running "fuser -d" on Advfs in lockmode 4. PROBLEM: (BCGM50N91) (Patch ID: OSF500-014) ******** 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: (HPAQ40343, HPAQ5062G, UVO20042) (Patch ID: OSF500-038) ******** This patch fixes a problem with heavy I/O loads on UFS filesystems that can result in poor response time; the system could appear to be "paused". In many cases, the system appears to "pause" after an update had executed (a sync is occurring). PROBLEM: (None) (Patch ID: OSF500-040) ******** This patch fixes system hangs that occur when there are nfs mounted files, the system is actively paging and the nfs server is unavailable. PROBLEM: (QAR 73345) (Patch ID: OSF500-053) ******** On large memory systems (1GB or larger) a "page owner not valid" panic can be seen if SSM objects are created and accessed during times of heavy paging and swapping activity. The other symptom is a performance problem that can lead to high page thrashing (i.e. thrashes on the same page), which in turn can make systems appear to be hung. PROBLEM: (QARS 73697,73494) ******** This patch fixes an AdvFS problem in which processes may hang. A second symptom is periodic short hangs where the system is unresponsive for a few minutes and then becomes available again. PROBLEM: (QAR 72431) (Patch ID: OSF500-054) ******** This patch fixes problems in the AdvFS file system. The problems included an EBUSY unmount problem and a panic that occurred when executing bs_real_invalidate_pages(). The system panics with the following message: ADVFS EXCEPTION Module = bs_buffer2.c, Line = 7516 bs_real_invalidate_pages(1): buf refd or pinned panic (cpu 0): bs_real_invalidate_pages(1): buf refd or pinned An example stack trace is: 18 panic() 19 advfs_sad () 20 bs_real_invalidate_pages() 21 msfs_reclaim() 22 vclean() 23 vgone() 24 getnewvnode() 25 vdealloc() 26 vrele() 27 namei() 28 unlink() 29 syscall() PROBLEM: (QAR 74759) (Patch ID: OSF500-100) ******** This patch fixes a problem in which unmounting an NFS mounted directory can cause a user process to coredump. PROBLEM: ('QAR 73869') (Patch ID: OSF500-117) ******** This patch fixes a problem with hangs on AlphaServer ES40 when specifying granularity hints. PROBLEM: ('QAR 74959') (Patch ID: OSF500-120) ******** This patch fixes a problem where ubc_msync() may not flush out all the pages in the requested range. PROBLEM: (QAR 73626) (Patch ID: OSF500-128) ******** This patch fixes a problem with the sync2() system call. Sync2 does not check returns from sync_int() or return errors to the caller of sync2(). A return from sync2() could be be handled like a sigreturn, causing all registers to be restored despite the fact that the registers may not have been previously saved. This causes register corruption. PROBLEM: (BCSMA1923/75276) (Patch ID: OSF500-130) ******** 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: OSF500-143) ******** 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: (MGO44815A) (Patch ID: OSF500-045) ******** 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 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 74449) (Patch ID: OSF500-063) ******** The patch fixes a problem with virtual memory. When running the Oracle database, Oracle can not detach from a shared memory segment. PROBLEM: ('QAR 68794, QAR 73596') (Patch ID: OSF500-074) ******** This patch fixes two separate panics with the following error messages: 1) vm_page_activate: already active A sample stack trace is listed below: 3 panic("vm_page_activate: already active") 4 vm_page_activate() 5 vm_pageout_scan() 6 vm_pageout() 2) simple_lock: time limit exceeded A sample stack trace is listed below: 5 panic("simple_lock: time limit exceeded") 6 simple_lock_fault() 7 simple_lock_time_violation() 8 vm_pg_free() 9 vm_anon_page_free() 10 u_anon_oop_pageout() 11 vm_pageout_scan() 12 vm_pageout() PROBLEM: (ALC-08332) (Patch ID: OSF500-082) ******** This fixes a "simple_lock: hierarchy violation" panic from sigq_abort(). PROBLEM: (NONE) (Patch ID: OSF500-083) ******** This patch adds the following kernel features: - enhanced core path support which allows applications to specify the directory where core files will be generated. - XA_FORK exit action support which allows applications to register actions to be performed when a process forks(). PROBLEM: (QAR 73927) (Patch ID: OSF500-084) ******** This patch corrects a problem in which a "device busy" error would be reported; the behavior has been changed to wait for the busy pages to be released. PROBLEM: ('QAR 73692, QAR 69021, QAR 74011') (Patch ID: OSF500-101) ******** This patch fixes a problem in the AdvFS system. A panic occurs with the following error message: lock_read: hierarchy violation PROBLEM: (DJOB71733) (Patch ID: OSF500-125) ******** This patch fixes a problem where a single cpu system using AdvFS can hang in cleanup_closed_list(). PROBLEM: ('QAR 75382') (Patch ID: OSF500-131) ******** This patch fixes a problem where several 8K pages in a file on an AdvFS filesystem can incorrectly contain all zeros instead of the data that was written to that portion of the file. The problem is that in certain circumstances, AdvFS will incorrectly deallocate several 8K pages of pre-allocated storage. This causes a hole to be created in the AdvFS extent map. When data is read from that hole, AdvFS returns 8K pages of zeros instead of the data that was written to that portion of the file. v50supportos-139-katz PROBLEM: (MGO67225A,TKTBA0006,BCSMA1GK5,EVT79308A,STLBB3923) (Patch ID: OSF500-139) ******** This patch corrects an AdvFS problem involving clone filesets. The read-ahead code was incorrectly passing up opportunities to do read-ahead on clone filesets, resulting in a large performance penalty. PROBLEM: ('QAR 73644') (Patch ID: OSF500-087) ******** 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: ( MGO05514A, QAR 73107) (Patch ID: OSF500-065) ******** This patch corrects two problems in AdvFS property list handling: 1) Creation of property lists entries in AdvFS filesets with no available mcells will result in kernel memory fault (kmf). Abbreviated stack: 17 _XentMM() 18 msfs_pl_pin_cur() 19 msfs_pl_create_rec() 20 msfs_pl_findhead_setdata() 21 msfs_pl_set_entry() 22 msfs_setproplist_int() 23 msfs_setproplist() 24 setproplist() 25 proplist_syscall() 26 syscall() 27 _Xsyscall() 2) The get_proplist_entry function (used to disassemble the property list buffer returned by the "getproplist" system call) returned incorrect name length on property list names longer than 127 characters. PROBLEM: (None) (Patch ID: OSF500-008) ******** This patch fixes a hang of the FDDI driver if that driver is brought down following a read-and-zero-counters request. Such a request can be done via netstat: netstat -z -I fta0 followed by ifconfig fta0 down will cause the following message to be displayed and will hang the interface: fta0: Command [0x40] error PROBLEM: (DEKB20145, UTO101928) (Patch ID: OSF500-015) ******** 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: (QAR 72626, CLD BCPM50LZC) (Patch ID: OSF500-018) ******** 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: (BCGMB0J3G, HPAQB1T92, BCPMB1K80, BCPMB1RJ5, QAR 75415) (Patch ID: OSF500-110) ******** 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: OSF500-129) ******** This patch consists of changes necessary for AV firewall 98 to pass ICSA certification. PROBLEM: (BCPM81CNT/BCPM80N9B) (Patch ID: OSF500-039) ******** 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. PROBLEM: (CLD EVT102855, QAR 73939) (Patch ID: OSF500-051) ******** 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: (CLD HPAQ61WN1) (Patch ID: OSF500-073) ******** This patch fixes a problem in which the system may panic with the error message "tcp_output REXMT". An example panic stack trace is: 0 boot 1 panic 2 tcp_setpersist 3 tcp_timers 4 tcp_usrreq 5 tcp_slowtimo 6 pfslowtimo 7 pftimeout_thread PROBLEM: (QAR 73901) (Patch ID: OSF500-094) ******** This patch fixes a TCP performance problem if the TCP window scale option is turned off when using the HIPPI interface. PROBLEM: (HPAQ7003V QAR 73588) (Patch ID: OSF500-013) ******** This patch fixes a problem with packetfilter applications that use ip packets greater than 8k. Application using packets greater than 8k can see messages in the application or tcpdump indicating truncated ip packets with missing data. PROBLEM: (CLD MGO34008A, QAR 73553) (Patch ID: OSF500-052) ******** This patch corrects a problem where ICMP redirect packets can modify the default route. PROBLEM: (none) (Patch ID: OSF500-138) ******** This patch involves virtual mac addressing. PROBLEM: (CLD MGO103853, CLD MGO103295, CLD MGO103959) (Patch ID: OSF500-022) ******** 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 73491') (Patch ID: OSF500-046) ******** This patch fixes a situation where multiple device special files may be created for the same physical device, even if the device was seen previously, and has a unique identifier. This condition only occurs on configurations where there is a shared SCSI bus, either in a cluster or shared between standalone systems. During heavy bus traffic it is possible that one adapter accessing a device can cause starvation on the lower priority SCSI IDs preventing another adapter from querying a device for required inquiry information. This can lead to one host incorrectly identifying a previously found SCSI device as a new device. PROBLEM: (QAR 74240) (Patch ID: OSF500-069) ******** This submit fixes a hardware management problem that will cause a system hang at boot time (in dsfmgr) whenever a hardware cpu upgrade is performed. The hang will look like this during the boot process: dsfmgr: NOTE: updating kernel basenames and old devnames for system at / kevm tty00 tty01 lp0 PROBLEM: (QAR 73967 QAR 73853) (Patch ID: OSF500-098) ******** 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 73124, QAR 71118') (Patch ID: OSF500-109) ******** This patch fixes a problem where partitioned AlphaServer 8200/8400 systems return incorrect cpu data for cpus that are not in the partition. PROBLEM: (QAR 71921, QAR 72204, CLD INT-08869, QAR 71802, QAR 72427) (Patch ID: OSF500-006) ******** This patch fixes the following Compaq AlphaServer problems: - On the ES40 and DS20, non-fatal 680 environment machine checks are being logged as fatal/non-correctable errors. - On the DS20, a fix has been made to the handling of power supply, temperature, and fan events so that they are reported correctly. - Provides support for the Compaq AlphaServer DS20E. PROBLEM: (BCSM61PZS) (Patch ID: OSF500-113) ******** This patch allows the com1_environment variables to be stored in NVRAM. On a DS10 platform, resetting console baud rate to anything other than the rate it was running, a system panic occurs at boot. PROBLEM: (QAR 75859) (Patch ID: OSF500-121) ******** This patch corrects siginfo codes for floating point and integer exceptions to better describe the specific exceptional condition. Without this patch, the generic FPE_FLTINV si_code might appear for all exceptional conditions even when FPE_FLTOVF, FPE_FLTDIV, FPE_INTOVF would be more informative. PROBLEM: (QAR 74057, QAR 65727) (Patch ID: OSF500-064) ******** 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 74538, QAR 74546') (Patch ID: OSF500-096) ******** This patch fixes a problem where registers might be corrupted with the preemption_on/off interfaces. PROBLEM: (CFS.71077) (Patch ID: OSF500-090) ******** The tape status register bit was being incorrectly cleared. This could result in a unit attention on the tape drive being missed. PROBLEM: (QAR 69554, QAR 70444, QAR 72011, QAR 72852, QAR 73439) (Patch ID: OSF500-005) ******** This patch fixes the following Universal Serial Bus (USB) problems: - The USB mouse no longer functions after resetting the Xserver. - System panics may occur in error handling after USB device fails a request. - The USB device may not deconfigure properly when unplugged from the bus. - Problems that will prevent some USB devices from being configured at boot time. - A key on a USB keyboard will continue to repeat after being unplugged. - USB keyboards may transmit the incorrect keycode for several keys. PROBLEM: (QAR 75090) (Patch ID: OSF500-085) ******** When booting at times the USB controller number maybe "-1". This causes doconfig to fail. PROBLEM: (58325) (PATCH ID: OSF500-219) ******** 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: (UVO74098) (PATCH ID: OSF500-180) ******** This patch adds a fix to VMAC functionality when used with NETrain. PROBLEM: (77638, 78380) (PATCH ID: OSF500-263) ******** 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: (74277, 74545) (PATCH ID: OSF500-232) ******** This patch fixes a problem in which operations on NFS files can hang indefinately. PROBLEM: (79365, 78896) (PATCH ID: OSF500-236) ******** This patch fixes a problem in which a reboot will fail after hwmgr is used to delete or add devices. PROBLEM: (75185, 75088, 74801) (PATCH ID: OSF500-155) ******** This patch corrects a problem in which the perrmask register on Tsunami systems can be overwritten. PROBLEM: (78586, 76831) (PATCH ID: OSF500-274) ******** This patch fixes a system hang that can occur during an NFS operation on a system running granularity hints. PROBLEM: (76279, 80469) (PATCH ID: OSF500-251) ******** In certain cases, executables or object files compiled on other versions of TRU64 Unix will not be able to correctly use the 4 networking system calls: sendmsg, osendmsg, recvmsg, and orecvmsg. Using them will spuriously return the EINVAL error code and no data will be sent or received. PROBLEM: (BCSM10B3R) (PATCH ID: OSF500-151) ******** This patch corrects a problem with four networking system calls, sendmsg/osendmsg and recvmsg/orecvmsg. Applications using these system calls may see an apparent hangs or failures because of large negative values in their return calls. PROBLEM: (75153, 75038, 75557, HPAL80TBB) (PATCH ID: OSF500-153) ******** This patch fixes the following two filesystem problems: - In AdvFS, a system can panic with the following error message panic: bs_logflush_start: cannot write lsn An example stack is as follows: 5 panic( bs_logflush_start: cannot write lsn) 6 advfs_sad 7 bs_logflush_start 8 call_logflush 9 bfflush_start 10 bfflush 11 msfs_fsync 12 fsync 13 syscall 14 _Xsyscall - NFS errors are recieved when doing file I/O on an AdvFS exported file system. PROBLEM: (BCSM412FX) (PATCH ID: OSF500-255) ******** 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 PROBLEM: (BCSM702LV, MGO59344E, MGO75812A) (PATCH ID: OSF500-285) ******** There is a potential for a system panic in routine sbflush() if there is an attempt to flush a socket buffer while it is locked by another thread. This patch corrects this problem. PROBLEM: (73035, 75406, 74962) (PATCH ID: OSF500-257) ******** This patch fixes a problem with AdvFS where all processes are waiting for buffers causing the system to hang. PROBLEM: (73112, 78765) (PATCH ID: OSF500-276) ******** 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: (78714, 78661) (PATCH ID: OSF500-241) ******** This patch fixes a problem in which when opening a RAID type device, the ALL_DTYPE_RAID was not being allowed. PROBLEM: (75537, 76478) (PATCH ID: OSF500-145) ******** This patch fixes a problem in which the system can hang if there is no cpu in slot 0. It also fixes an instruction fault due to a divide by 0. PROBLEM: (BCGM10RFF, 77112) (PATCH ID: OSF500-167) ******** 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: (13096) (PATCH ID: OSF500-149) ******** n 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: (72111, 74264) (PATCH ID: OSF500-181) ******** This patch fixes a problem with verify. When verify is run on a brand new domain, nfs warnings are displayed even though no nfs related activity is being done. PROBLEM: (76142, 75158) (PATCH ID: OSF500-281) ******** This patch fixes a problem in AdvFS. When calling bs_startio, the wrong number of parameters was being used, resulting in a potential slow down of some flushes. PROBLEM: (79218, 78973, 78888) (PATCH ID: OSF500-235) ******** This patch fixes the following two problems in the I/O subsystem: - only the first byte of the HSZ serial number is checked - the time allowed for the command timeout on AIT tape drives is increased to from 5 seconds to 5 minutes. PROBLEM: (73836, 75780) (PATCH ID: OSF500-289) ******** This patch fixes a problem in AdvFS. The function bfflush_range() may return success before flushing all the pages it should. PROBLEM: (TKTR30001) (PATCH ID: OSF500-238) ******** 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: (BCPMB215Q) (PATCH ID: OSF500-150) ******** 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: (MGO45830B) (PATCH ID: OSF500-243) ******** System spends excessive time in the internet checksum routine due to an invalid message length. Performance is degraded significantly. PROBLEM: (74559) (PATCH ID: OSF500-133) ******** This patch fixes a problem with VM page corruption that has the following panic message: vm_pg_alloc: page not free A sample stack trace is listed below: 7 boot() 8 panic() 9 vm_pg_alloc() 10 ubc_page_alloc() 11 ubc_lookup() 12 nfs3_getapage() 13 nfs3_getpage() 14 rw3vp_cache() 15 rw3vp() 16 nfs3_rdwr() 17 vn_write() 18 rwuio() 19 write() 20 syscall() 21 _Xsyscall() PROBLEM: (77175, 77559) (PATCH ID: OSF500-175) ******** This patch fixes a panic which has the following error message: simple_lock: hierarchy violation pc of caller: 0xfffffc0000580820 lock address: 0xfffffc00019c8080 lock info addr: 0xfffffc0000b0b0a0 lock class name: vm_control.vm_queue_lock class already locked: cam_ccmn_data_pool current spl level: 4 simple lock held by cpu 0: The stack trace is listed below: 17 panic() 18 simple_lock_fault() 19 simple_lock_hierarchy_violation() 20 vm_page_stealer() 21 vm_pg_alloc() 22 malloc_pg_alloc() 23 malloc_internal() 24 malloc() 25 ccmn_sched_call() 26 ccmn_get_dbuf() 27 cdisk_rec_read() 28 cdisk_rec_read_cap_done() 29 xpt_callback_thread() PROBLEM: (78797) (PATCH ID: OSF500-231) ******** The "can_replace: slot replacement mismatch" panic can occur when running multithreaded applications and is most likely if such an application calls exec() while other threads are concurrently blocking and unblocking in the kernel. PROBLEM: (77293) (PATCH ID: OSF500-194) ******** This patch fixes a panic which has the following error message: lock_clear_recursive: recursion not enabled The stack trace is listed below: 1 panic ("lock_clear_recursive: recursion not enabled") 2 lock_fault() 3 lock_clear_recursive() 4 u_stack_create() 5 exec_stack_alloc() 6 common_exec() 7 execve() 8 syscall() 9 _Xsyscall() PROBLEM: (74906, 74796) (PATCH ID: OSF500-140) ******** This patch fixes a problem in which metadata buffers are being written asynchronously instead of on a delayed basis. PROBLEM: (75551, 75904) (PATCH ID: OSF500-279) ******** This patch fixes a problem in AdvFS where v_numoutput is not being decremented causing AdvFS to hang. PROBLEM: (UVO04205, 73635) (PATCH ID: OSF500-261) ******** 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: (76425, 76389) (PATCH ID: OSF500-163) ******** This patch fixes a problem in which network deamons, such as NIS and NFS do not function properly because of mislabbeled packets. PROBLEM: (79937, 79251, 79305, 80263) (PATCH ID: OSF500-298) ******** 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: (78838) (PATCH ID: OSF500-270) ******** The problem caused an incorrect bcache size to be returned to the kernel from the HWRPB. This problem occurred on Professional Workstation 900 and 1000 systems and AlphaServer DS10, DS20, DS20E, ES40, GS80, GS160, and GS320 systems. PROBLEM: (BCSM511NN, TKTB30013, MGO62066A, 79783, BCSM50XTD) (PATCH ID: OSF500-262) ******** This patch prevents a deadlock situation from occurring on an NFS server that has clients with NFS over TCP mounts. When analysis of that system is completed, at least one of the nfs_tcp_threads will be hung in rrok3free(). The stack trace will look similar to this: 0 thread_block() 1 mpsleep() 2 rrok3free() 3 svcktcp_reply() 4 svc_sendreply() 5 rfs_sendreply() 6 rfs_dispatch() 7 nfs_rpc_recv() 8 nfs_tcp_thread () PROBLEM: (HPAQB1FTS) (PATCH ID: OSF500-152) ******** 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: (HPAQ418B4) (PATCH ID: OSF500-284) ******** This patch fixes a problem where some network based multimedia applications will cause a kernel memory fault when exiting. A sample stack trace is as follows: 1 panic(s = 0xfffffc00007d10a0 = "kernel memory fault") 2 trap 3 _XentMM 4 igmp_leavegroup 5 in_delmulti 6 ip_freemoptions 7 in_pcbfree 8 in_pcbdetach 9 udp_usrreq 10 soclose 11 soo_close 12 closef 13 close_ufe 14 exit 15 rexit 16 syscall 17 _Xsyscall PROBLEM: (TKTR90018) (PATCH ID: OSF500-209) ******** 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: (76155, 76156, 77967) (PATCH ID: OSF500-227) ******** This patch fixes a kernel memory fault caused by either one of the following conditions: 1. On EV6 platforms, when the debugger is used to view the OT_DEVMAP object mapping memory in I/O space that is mapped to a user process. 2. When routine pmap_coproc_exit_notify() modifies the pmaps' coproc_tbi function to be 0, a null pointer, while it is being checked by routine pmap_remove_all() PROBLEM: (73321, 73943) (PATCH ID: OSF500-165) ******** This patch fixes a problem in Advfs. A panic occurs with the following error message: lock_read: hierarchy violation Two relevant stack traces are listed below: Stack Trace #1 1 panic() 2 thread_block() 3 thread_preempt() 4 boot() 5 panic() 6 cpu_ip_intr() 7 _XentInt() 8 simple_lock() 9 sq_wrapper() 10 csq_lateral() 11 runq_run() 12 netisr_thread() Stack Trace #2 1 panic() 2 event_timeout() 3 xcpu_puts() 4 printf() 5 panic() 6 lock_fault() 7 lock_read() 8 x_load_inmem_xtnt_map() 9 page_is_mapped() 10 bs_pinpg_one_int() 11 bs_pinpg_clone() 12 bs_pinpg_ftx() 13 rbf_pinpg() 14 alloc_mcell_undo() 16 ftx_fail() 17 stg_add_stg_no_cow() 18 stg_add_stg() 19 bmt_extend() 20 alloc_mcell() 21 bmt_alloc_prim_mcell() 22 new_mcell() 23 rbf_int_create() 24 rbf_create() 25 fs_create_file() 26 msfs_create() 27 vn_open() 28 copen() 29 open() 30 syscall() 31 _Xsyscall() PROBLEM: (77274, 78605) (PATCH ID: OSF500-265) ******** This patch fixes a problem with AdvFS. An AdvFS domain becomes inaccessible when using the mount -d option. PROBLEM: (72418, 78280) (PATCH ID: OSF500-269) ******** This patch fixes a problem in AdvFS in which a system that had already domain panic'ed results in a system panic. PROBLEM: (76177, 76174, 75915, 75456) (PATCH ID: OSF500-234) ******** This patch provides support for an increase in the number of binlog records for FRU/config tables to greater than 32K. PROBLEM: (79143, 78222, 77462, 80085, 81131, 77551) (PATCH ID: OSF500-272) ******** This patch corrects several cam device related problems. - The ddr database entry for HSG80 is now handled correctly by the .mrg file. - A kernel memory fault while performing HSZ80 failover has been corrected. A sample stack trace is provided: 5 panic() 6 biodone() 7 cdisk_strategy() 8 cdisk_rec_done() 9 cdisk_rec_modesns_done() 10 xpt_callback_thread() - The RA3000 (HSZ22) now correctly reports the value for AWRE/ARRE in the error page. - This patch corrects a problem that caused HSG70 or HSG80 pairs to fail to respond to selection when performing a transparent failover from one controller to another. Prior to this patch, the HSG70 or HSG80 pairs were unable to see paths to devices, consequently the devices were declared unreachable. - SCSI RAID device types are registered as control ports; not disks. PROBLEM: (HPAQA20BT) (PATCH ID: OSF500-216) ******** 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: (77713) (PATCH ID: OSF500-169) ******** This patch fixes a problem in which the POSIX interval timer is not resilent to clock slowdown cause either by NTP or by a backwards change of the clock. PROBLEM: (MGO85573B) (PATCH ID: OSF500-132) ******** This patch fixes a bug such that when 'fuser -k' is issued on a dismounted NFS mount point in which some process is running, a hang will occur. A new flag, -p, has been introduced. When the -p flag is used with the -c flag, as in 'fuser -c -p -k /mnt', the parent directories are ignored and the processes are gracefully killed. PROBLEM: (HPAQ20V27) (PATCH ID: OSF500-210) ******** 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: (77824, 77829, SSRT0675U) (PATCH ID: OSF500-193) ******** 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: (78020, 78520) (PATCH ID: OSF500-278) ******** This patch fixes a problem in AdvFS where user data may be lost when a clone file is migrated. PROBLEM: (74651, 75705) (PATCH ID: OSF500-197) ******** 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: (76461, 75539) (PATCH ID: OSF500-162) ******** This patch fixes a problem in which an application can hang because of an undelivered signal. PROBLEM: (MGO90721A) (PATCH ID: OSF500-157) ******** 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: (BRO96818B) (PATCH ID: OSF500-211) ******** 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: (TKTBC0035, 78015) (PATCH ID: OSF500-222) ******** 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 PROBLEM: (73029) (PATCH ID: OSF500-159) ******** This patch fixes a problem where the hardware manager reports inaccurately the cpu speed. It reported a cpu speed that was one MHz less than the correct speed. PROBLEM: (73864, 79088) (PATCH ID: OSF500-268) ******** This patch fixes a problem with AdvFS in which a hang occurs due to a deadlock between bsbuf.state and bmt extent map lock. PROBLEM: (73827, 71974) (PATCH ID: OSF500-137) ******** This patch fixes a problem in which an invalid error status is returned from the remove_entry system call. PROBLEM: (79152, 79374) (PATCH ID: OSF500-237) ******** This patch corrects a kermel memory fault caused by hwmgr. A sample of the dump trace is as follows: 0 thread_block() 1 thread_preempt() 2 cms_flushbufs() 3 boot() 4 panic() 5 trap() 6 _XentMM() 7 find_proc_devnode() 8 hwc_kds_func() 9 kds_info_func() 10 getsysinfo() 11 syscall() 12 _Xsyscall() PROBLEM: (ISO100518) (PATCH ID: OSF500-206) ******** 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: (77157, 76777) (PATCH ID: OSF500-161) ******** This patch fixes a problem where the output of a "ps" command, the PAGEIN column reports 0 for all processes. After installing this patch, the ps PAGEIN value increases as advfs accesses the disk for vm accesses (but not for normal file read). PROBLEM: (77842, 76966, BCSM111C6) (PATCH ID: OSF500-250) ******** This patch fixes support of converting bootable tape bootstrings to device names and converting device names back to bootable tape bootstrings. PROBLEM: (75800, 77023) (PATCH ID: OSF500-173) ******** The patch fixes several panics on systems with holes in memory. The error messages are listed below: 1) panic: put_free_ptepage: invalid pvh state 2) panic: kernel memory fault trap: invalid memory read access from kernel mode Stack trace is listed below: 0 stop_secondary_cpu() [585, 0xfffffc00004ad350] 1 panic() [751, 0xfffffc0000285154] 2 event_timeout() [1159, 0xfffffc00004ae190] 3 xcpu_puts() [895, 0xfffffc000028543c] 4 printf() [423, 0xfffffc00002845e0] 5 panic() [804, 0xfffffc00002852b8] 6 trap() [1707, 0xfffffc00004c3cc8] 7 _XentMM() [1678, 0xfffffc00004b8a18] 8 simple_lock() [1022, 0xfffffc00004bb220] 9 pmap_enter() [1394, 0xfffffc00004db444] 10 u_dev_fault() [348, 0xfffffc0000481ac0] 11 u_map_fault() [560, 0xfffffc000049a6e0] 12 vm_fault() [134, 0xfffffc000048c620] 13 trap() [1726, 0xfffffc00004c3018] 14 _XentMM() [1678, 0xfffffc00004b8a18] 3) panic: not wired simple_lock: hierarchy violation Stack trace is listed below: 1 panic() 2 event_timeout() 3 xcpu_puts() 4 printf() 5 panic() 6 pmap_lw_unwire_new() 7 lw_unwire_new() 8 vm_map_pageable() 9 physio() 10 physiock() 11 volread() 12 spec_read() 13 msfsspec_read() 14 vn_pread() 15 prwuio() PROBLEM: (74610, 73445) (PATCH ID: OSF500-142) ******** This patch fixes a problem in which the SCSI version number was being checked for not SCSI-2 when is should have been checked for not SCSI 2 or SCSI 3. PROBLEM: (HPAQ30SQ8) (PATCH ID: OSF500-198) ******** 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: (79486, DEK013137) (PATCH ID: OSF500-296) ******** This patch fixes panics and memory corruption in setuid/setgid. PROBLEM: (UVO58439L) (PATCH ID: OSF500-271) ******** This patch corrects a problem whereby under certain unlikely conditions, a b-tree index for a directory could become corrupted. Once corrupted, the file system will domain panic upon removal of files from the directory with the panic string "idx_remove_filename_int: Bad node count - domain panic". PROBLEM: (QCAPUN003) (PATCH ID: OSF500-166) ******** This patch fixes a problem where the system appears to hang. A child process is holding a lock too long and preventing other processes from doing work. The child process is waiting to be re-parented as its parent is winding down. No new processes can be created, although certain existing processes will still continue to function. A forced crash will reveal several processes waiting for the pgrphash lock. The pgrphash lock will be held by a child process waiting for its parent to die which is being held up by an external event. A sample stack trace for the child process holding the pgrphash lock 0 thread_block 1 get_parent 2 fixjobc 3 pgmv 4 setpgrp1 5 setpgid 6 syscall 7 _Xsyscall