PROBLEM: (TKTBC0035, 78015) (PATCH ID: OSF505-027) ******** 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 an EV6 CPU system, DECevent displays the text in an incorrect format that translates to an EV5 CPU. PROBLEM: (13096) (PATCH ID: OSF505-019) ******** In the per-VP scheduling state that is shared between the kernel and the DECthreads library scheduler, the compiler generates ldq/stq pairs for a 32-bit data object that neighbors another 32-bit variable. This patch fixes the stq that causes a word tear that corrupts the per-VP floating point flag field called nxm_fp_owned. The affected data structures are defined in . PROBLEM: (78797) (PATCH ID: OSF505-020) ******** 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: (74906, 74796) (PATCH ID: OSF505-034) ******** This patch fixes a problem in which metadata buffers are being written asynchronously instead of on a delayed basis. PROBLEM: (77713) (PATCH ID: OSF505-041) ******** 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: (BCGM10RFF, 77112) (PATCH ID: OSF505-047) ******** 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: (QCAPUN003) (PATCH ID: OSF505-048) ******** 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 PROBLEM: (HPAQ20V27) (PATCH ID: OSF505-050) ******** 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: (MGO90721A) (PATCH ID: OSF505-007) ******** 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: (MGO85573B, N/A) (PATCH ID: OSF505-008) ******** 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: (TKTR30001) (PATCH ID: OSF505-009) ******** 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: (79937) (PATCH ID: OSF505-065) ******** This patch fixes a hang or simple_lock_state_violation 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: (79750) (PATCH ID: OSF505-079) ******** This patch fixes a system panic in cfs_unmount. The panic string is: cfs_unmount: panic("VFS_UNMOUNT failed "). This is caused by a race condition in ubc_invalidate() where pages could be missed if they transition from the clean list to the dirty list. PROBLEM: (79241, 79696) (PATCH ID: OSF505-083) ******** This patch fixes "simple_lock: time limit exceeded" system panic either from cache_lookup() or cache_enter(). This is caused by the namecache LRU list getting corrupted. PROBLEM: (80469) (PATCH ID: OSF505-084) ******** In certain cases, binary compatibility for the four system calls sendmsg, nsendmsg, recvmsg, and nrecvmsg were not preserved between V4.0x and V5.x releases. This patch corrects this problem, so these four system calls are properly compatible in V5.0 with V4.0 compiled executables/objects. PROBLEM: (73112, 78765) (PATCH ID: OSF505-114) ******** 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: (BCSM702LV, MGO59344E, MGO75812A) (PATCH ID: OSF505-126) ******** 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: (79486, DEK013137) (PATCH ID: OSF505-138) ******** This patch fixes panics and memory corruption in setuid/setgid. PROBLEM: (76279, 80469) (PATCH ID: OSF505-094) ******** 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: (77638, 78380) (PATCH ID: OSF505-103) ******** 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: (78586, 76831) (PATCH ID: OSF505-112) ******** This patch fixes a system hang that can occur during an NFS operation on a system running granularity hints. PROBLEM: (77157, 76777) (PATCH ID: OSF505-039) ******** 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: (QAR.79000, n/a) (PATCH ID: OSF505-067) ******** This patch fixes an Advfs problem where under the right conditions a Kernel Memory Fault panic can occur while writing to an Atomic Data Logging file. 5 panic ( Kernel Memory Fault) 6 trap 7 _XentMM 8 ftx_fail_2 9 ftx_fail 10 fs_write 11 msfs_write 12 vn_write 13 rwuio 14 write 15 syscall 16 _Xsyscall PROBLEM: (UVO58439L) (PATCH ID: OSF505-111) ******** 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: (BRO96818B) (PATCH ID: OSF505-054) ******** This fixes a kernel memory fault in u_anon_faultpage() when it accesses 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: (79158) (PATCH ID: OSF505-076) ******** Adding a swap parition of less than 8KB in size causes system instability. PROBLEM: (BCGM919P3, EVT376821B, EVT376821, 82934) (PATCH ID: OSF505-187) ******** This patch fixes a hang seen while running collect and the vdump utility. This patch prevents the hang in tok_wait from occurring. PROBLEM: (VNO65701A) (PATCH ID: OSF505-218) ******** This patch fixes an issue with lightweight wiring of pages and shared memory regions. This problem can occur when running Oracle and may cause ORA-01034: Oracle not available" errors when attempting to connect to Oracle databases. PROBLEM: (HPAQ30LKL) (PATCH ID: OSF505-183) ******** This patch fixes inaccuracy problems when using setrlimit/getrlimit with a threaded application. PROBLEM: (BCPMB0MC4, 117-2-306, 84332) (PATCH ID: OSF505-223) ******** This patch fixes a system hang caused by netisr queue corruption due to a race condition that is primarily encountered by third party drivers and layered products that call schednetisr_nospl(). PROBLEM: (MGO10736A, EVT0396650, TPOB36405, BCSM10NZK) (PATCH ID: OSF505-233) ******** This patch fixes a problem where threads can hang in x_load_inmem_xtnt_map() when called from x_page_to_blkmap(). A typical hung thread will have the following calls at the top of its stack trace: 0 thread_block 1 lock_read 2 x_load_inmem_xtnt_map 3 x_page_to_blkmap 4 x_page_to_iolist 5 blkmap PROBLEM: (ALC-2-076) (PATCH ID: OSF505-253) ******** This patch fixes a timing window where flushing data to disk can be incomplete when a system is going down. Note this can only occur if all of these conditions are true: o More than one thread calls the reboot() system call without first going through shutdown, /sbin/reboot, or /sbin/halt (note the operating system itself does not do this, it would have to be an application program which is calling reboot()). o O_SYNC is not in use. o AdvFS data logging is not in use. PROBLEM: (81379, 77978) (PATCH ID: OSF505-159) ******** The system returns the incorrect status from read EEROM. PROBLEM: (BCGM70ZJC, UVO58439J) (PATCH ID: OSF505-148) ******** This patch introduces a kernel tunable parameter "non_preemempt_limit" that can be used to debug certain problems with kernel threads that run too long. PROBLEM: (78704) (PATCH ID: OSF505-236) ******** This patch fixes a hang in the ufs filesystem. PROBLEM: (82597, 83100) (PATCH ID: OSF505-203) ******** This patch fixes a kernel memory fault when writing to /proc. This issue can be seen as a kernel memory fault or possibly other failures in u_anon_rss_enforce. This issue is predominently seen as a KMF, the condition only occurs when anon_rss_enforce is set to 2 (HARD LIMIT). A typical stack trace is as follows: ... 4 panic src/kernel/bsd/subr_prf.c : 1339 5 trap src/kernel/arch/alpha/trap.c : 2262 6 _XentMM src/kernel/arch/alpha/locore.s : 2126 7 u_anon_rss_enforce src/kernel/vm/u_mape_anon.c : 4666 8 u_anon_fault src/kernel/vm/u_mape_anon.c : 1277 9 u_map_copy_overwrite src/kernel/vm/vm_umap.c : 2084 10 procfs_write src/kernel/procfs/procfs_vnops.c : 2222 11 vn_write src/kernel/vfs/vfs_vnops.c : 1372 12 rwuio src/kernel/bsd/sys_generic.c : 2257 13 write src/kernel/bsd/sys_generic.c : 2179 14 syscall src/kernel/arch/alpha/syscall_trap.c : 719 15 _Xsyscall src/kernel/arch/alpha/locore.s : 1796 Typical reproduction of this issue can be seen by doing the following: 1) Add "anon_rss_enforce=2" to the vm section of /etc/sysconfigtab 2) Reboot with new setting 3) Run dbx on any a.out file "$ dbx a.out" PROBLEM: (82489, SSRT0676U) (PATCH ID: OSF505-215) ******** 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. SYNOPSIS mountd [-d] [-i] [-n] [-s] [-r] [-R] [exportsfile] FLAGS ... -r Have mountd listen for requests on a reserved port. This is the default behavior. -R mountd may listen on an unreserved port. PROBLEM: (76340, 80511) (PATCH ID: OSF505-162) ******** This patch fixes a problem in UFS. The O_SYNC does not work properly causing the inode update to fail on a synchronous write. PROBLEM: (81696, 82048) (PATCH ID: OSF505-150) ******** The symptom may be seen when updating an AdvFS file that contains a frag via directIO. If the file is opened for directIO and the frag page is only partially overwritten, then the updated data may not appear in subsequent reads. PROBLEM: (BCPM91FRG, 82491) (PATCH ID: OSF505-234) ******** This patch fixes a problem that causes Tarantella Enterprise 1.41 not to install on Tru64 UNIX. PROBLEM: (ALC-2-076) (PATCH ID: OSF505-249) ******** This patch fixes a potential problem flushing data to disk when using data logging with sparse files in an AdvFS filesystem. PROBLEM: (83842) (PATCH ID: OSF505-197) ******** This patch prevents stat(), lstat(), fstat(), statfs(), fstatfs(), getmntinfo(), and getfsstat() from returning EOVERFLOW errors for programs compiled on Tru64 UNIX v4.0* or earlier. A program that is compiled on v4.0* or earlier and was linked static (cc -non_shared) and calls the getcwd() or statvfs() functions can fail. Any program that was compiled on v4.0* or earlier that calls statfs(), fstatfs(), getmntinfo(), or getfsstat() could fail, such as the Oracle 8.1.7 install. PROBLEM: (80060, 80011) (PATCH ID: OSF505-156) ******** This patch fixes a performance problem in AdvFS. Checksum calculation loops were removed to speed up performance. PROBLEM: (84601) (PATCH ID: OSF505-198) ******** If Oracle customers are running one of the affected Oracle configurations, Oracle may have already detected an inconsistency in the database and reported errors similar to the following in the alert log and trace file: ORA-01578: ORACLE data block corrupted (file # 1, block # 100) ORA-01119: data file 1: '/scratch/820/qa/dbs/t_db1.f' or ORA-00368: checksum error in redo block ORA-00354: Log corruption near block #231 Oracle customers that have run the dbverify (dbv) utility may have encountered an error message similar to the following: *** Corrupt block relative dba: 0x0040900b (file 0, block 36875) Bad header found during dbv: Data in bad block - type: 27 format: 2 rdba: 0x0040900d last change scn: 0x0000.0001349a seq: 0x2 flg: 0x04 consistency value in tail: 0x349a1b02 check value in block header: 0xa377, computed block checksum: 0x0 spare1: 0x0, spare2: 0x0, spare3: 0x0 *** PROBLEM: (83661, 85312, STL111443) (PATCH ID: OSF505-226) ******** This patch fixes a problem where the setgid bit of a directory was not being set when created, if its parent directory has the setgid bit set. PROBLEM: (78804) (PATCH ID: OSF505-188) ******** This patch fixes an issue with some remote ioctls for tape/changer drivers not working in a cluster. PROBLEM: (85447, 85450, MGO07072A, NWO42386A) (PATCH ID: OSF505-263) ******** This patch fixes several virtual memory algorithms related to the allocation and freeing of pages within the kernel. PROBLEM: (ALC-2-076) (PATCH ID: OSF505-217) ******** This patch provides support for activating temporary atomic write data logging on all files within the mount point. The data logging is turned off when the fileset is unmounted. PROBLEM: (BCGMA0VHK) (PATCH ID: OSF505-181) ******** This patch fixes a problem in which the system call fcntl(fd, F_DUPFD, 15) fails with "too many files" even after fd limits have been increased. PROBLEM: (83392) (PATCH ID: OSF505-239) ******** This patch corrects the behavior of the FIONBIO, FIOASYNC, and FIONREAD ioctl's in a cluster environment. These commands would fail, returning ENOTTY when they should have succeeded. PROBLEM: (80302, 80232) (PATCH ID: OSF505-147) ******** This patch fixes a kernel memory fault from ufs_mount(). PROBLEM: (81889, BCGM81PWJ) (PATCH ID: OSF505-185) ******** This patch resolves hang-like behavior when LSM volumes are used to create AdvFS domain volumes. With some systems the default preferred IO byte transfer size for read and write requests is initially set too high. Run the "chvol" command on the domain volumes and see if the rblks or wblks field is very large. These are the sizes of the read and write IO transfer size that AdvFS uses to issue reads or writes, respectively. In some cases, the transfer size converted to bytes may be as large as 1GB or 2GB's. The patch will cause AdvFS during domain activation to check if an AdvFS volume's underlying driver is LSM. If the default "preferred" IO byte transfer size is 64MB's or larger for LSM drivers, then AdvFS will instead use a lower size of 256KB's (512 blocks). If a larger value is desirable, then you can still use "chvol" to change the transfer size for reads or writes. "chvol -l" command will display the preferred, maximum and minimum transfer sizes. The patch also eliminates confusing warning messages about exceeding the preferred read or write transfer size seen when the IO transfer size has been set higher than the preferred transfer size default. PROBLEM: (SSRT0700U) (PATCH ID: OSF505-169) ******** 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: (GB_G00942) (PATCH ID: OSF505-248) ******** This patch corrects an AdvFS panic which can occur during a rmfset operation. The panic string: "rbf_delete_int: can't find bf attributes" PROBLEM: (BCGM32243) (PATCH ID: OSF505-199) ******** This fixes a "u_anon_free: page busy" panic. An example stack trace: panic("u_anon_free: page busy") u_anon_free() u_anon_unmap() u_map_delete() vm_map_remove() vm_deallocate() procfs_read() vn_read() rwuio() read() syscall() _Xsyscall() PROBLEM: (81341, qar81334) (PATCH ID: OSF505-175) ******** The system can get a memory fault with a trace such as the following : 3 panic(s = (unallocated - symbol optimized away)) 4 trap() 5 _XentMM() 6 bs_bfs_close() 7 quotaUndo() 8 ftx_fail_2(ftxH 9 fs_write_add_stg(fffc0009afd4 10 fs_write() 11 vn_write() 12 rwuio() 13 write() 14 syscall() 15 _Xsyscall() PROBLEM: (BCGM805NL) (PATCH ID: OSF505-251) ******** | These changes address panics which can occur if a | signal is sent to a multi-threaded task in which | one or more threads are calling exit() or exec(). | The panic is invariably a kernel memory fault whose | faulting virtual address is usually 0x50. The | following panic message is typical: | trap: invalid memory read access from kernel mode | faulting virtual address: 0x0000000000000050 | pc of faulting instruction: 0xfffffc0000283bc0 | ra contents at time of fault: 0xfffffc0000283bb4 | sp contents at time of fault: 0xfffffe0450d77360 An example stack trace: 0 thread_block 1 thread_preempt 2 boot 3 panic 4 trap 5 _XentMM 6 thread_signal_wakeup 7 psignal_internal 8 kill 9 syscall 10 _Xsyscall PROBLEM: (83467) (PATCH ID: OSF505-205) ******** Under certain circumstances, a Tru64 UNIX system can panic with the string: "lock_write: simple lock owned" in the if_slowtimo() routine. PROBLEM: (78785, 78853) (PATCH ID: OSF505-040) ******** This patch fixes a problem where Network File System (NFS) attribute caching routines (nfs_attrcache_va(), nfs3_attrcache(), and nfs_attrcache() erroneously caused the Cluster File System (CFS) to purge its attribute cache. This behavior had the potential to cause a noticeable performance degradation on systems that perform large writes, because the caching routines would send out many thousands of purge requests that would delay the writes. The system now purges information that is cached by CFS at the same intervals as the NFS client cache. The CFS purge requests are made from the nfs_purge_caches() routine. PROBLEM: (BCSM511NN, TKTB30013, MGO62066A, 79783, BCSM50XTD) (PATCH ID: OSF505-102) ******** 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 () This patch is also to prevent a sbdrop panic from occurring. The stack trace will contain: 5 panic() 6 sbdrop() 7 tcp_input() 8 ipintr() 9 netisr_thread() PROBLEM: (BCSM412FX) (PATCH ID: OSF505-091) ******** 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: (MGO45830B) (PATCH ID: OSF505-088) ******** This patch corrects a problem which could cause the system to spend excessive time in the internet checksum routine, resulting in a degradation of system performance. PROBLEM: (HPAQ60DTF, 79899, 80475, 80027) (PATCH ID: OSF505-093) ******** This patch corrects the following error seen while trying to do a write to a soft mounted NFS filesystem: Jun 5 10:38:35 fchelp vmunix: NFS3 RFS3_WRITE failed for server ncinfs: RPC: Server can't decode arguments Jun 5 10:38:35 fchelp vmunix: NFS3 write error 5 on host ncinfs This patch also increases performance of NFS client I/O for many new network interface cards, including Gigabit Ethernet (DEGPA). PROBLEM: (MGO59344C, 80674) (PATCH ID: OSF505-134) ******** This patch is to prevent a hang that can occur using NFS over TCP. Many NFS TCP server threads will be blocked for several minutes and their stack trace will look like the following: 0 thread_block 1 mpsleep 2 sosleep 3 sosbwait 4 sosend 5 xdrrecmbuf_send 6 svcktcp_reply 7 svc_sendreply 8 rfs_sendreply 9 rfs_dispatch 10 nfs_rpc_recv 11 nfs_tcp_thread This problem is a race condition and will only be seen on SMP systems. PROBLEM: (HPAQ418B4) (PATCH ID: OSF505-123) ******** 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: (76224) (PATCH ID: OSF505-151) ******** This patch corrects a problem where a directory entry may be attempted to be changed to "." and the code checks for this prevents it from happening. PROBLEM: (84401, MGO35023A, 78934, 79892) (PATCH ID: OSF505-206) ******** This patch corrects a hang that can be seen on multi-cpu systems using NFS-over-TCP. THE SMP race is seen between the 'nfs_tcp_input' and the 'nfs_tcp_thread' functions. The stack of the netisr_thread may look like: (kdbx) tset 0xfffffc003cf38e00 (kdbx) t > 0 thread_block 1 lock_wait 2 lock_write 3 solock 4 soclose 5 tsp_unref 6 nfs_tcp_input 7 sbwakeup 8 sowakeup 9 tcp_close 10 tcp_input_common 11 tcp_input 12 ipintr 13 netisr_thread PROBLEM: (BCGMA1NFM, HPAQ11RSG, EVT0587933, GB_G01162) (PATCH ID: OSF505-232) ******** This patch fixes a problem where a race condition in NFS code could result in a kernel memory fault. A typical stack trace looks like: . . . 5 panic 6 trap 7 _XentMM 8 nfs3_getpage 9 rw3vp_cache 10 rw3vp 11 nfs3_rdwr 12 vn_read 13 rwuio 14 read PROBLEM: (HGO073056) (PATCH ID: OSF505-231) ******** This patch fixes a problem where threads can hang while renaming files on nfs mounted filesystems. This can occur when two threads are renaming files, one from directory "a" to directory "b" and the other from directory "b" to "a". A typical stack trace for a hung thread looks like: 0 thread_block 1 lock_write 2 nfs3_rename 3 rename 4 syscall PROBLEM: (QCABBY005) (PATCH ID: OSF505-245) ******** This patch fixes a panic which can occur on a V5.0A TruCluster system. The panic will look similar to this: 5 panic 6 trap 7 _XentMM 8 free 9 in_pcbfree 10 tcp_input_common 11 tcp_input 12 ipintr 13 netisr_thread PROBLEM: (STL148903, HPAQC15VM, HPAQC1H38, BE_G01081) (PATCH ID: OSF505-202) ******** This patch corrects the following error seen while trying to do a write to a soft mounted NFS filesystem: Jun 5 10:38:35 fchelp vmunix: NFS3 RFS3_WRITE failed for server ncinfs: RPC: Server can't decode arguments Jun 5 10:38:35 fchelp vmunix: NFS3 write error 5 on host ncinfs PROBLEM: (HPAQ81G66, MGO32494A, 79826) (PATCH ID: OSF505-216) ******** This patch fixes kernel memory fault panics with the following stack traces: _XentMM anon_getpage u_anon_fault u_map_fault vm_fault trap _XentMM panic trap _XentMM _ms_free bs_free_bsbuf msfs_fs_cleanup vm_pg_alloc vm_anon_page_alloc u_anon_faultpage u_anon_fault u_map_fault vm_fault trap _XentMM panic vm_kanon_lookup k_mem_free_anon k_mem_unmap k_map_delete vm_map_remove pfmclose speclose PROBLEM: (EVT18628A, 59132) (PATCH ID: OSF505-262) ******** This patch modifies advfs kernel code and several utilities. AdvFS will no longer panic with the following error: ADVFS EXCEPTION : panic cpu(0) : bad frag free list. The code is modified so that during frag allocation when advfs determines that the frag group header's free list has been corrupted, it stops using it and marks it BAD. It is then removed from the free list so no more allocations can take place AND no deallocations are performed. The verify, shfragbf and vfragpg programs are modified to report BAD frag groups. PROBLEM: (87559) (PATCH ID: OSF505-300) ******** The problem causes a system panic. The panic string will be: "simple_unlock: lock not owned by cpu" and will occur in the biodone routine. Typical stack trace: (dbx) t > 0 stop_secondary_cpu() 1 panic() 2 event_timeout() 3 xcpu_puts() 4 printf() 5 panic() 6 simple_lock_fault() 7 simple_unlock_owner_violation() 8 biodone() 9 cdisk_complete() 10 xpt_callback_thread()