PROBLEM: (BCGMC1JRS UVO106265) (Patch ID: OSF440-011) ******** 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 occurred on Dataless Management Services (DMS) client systems. To correct this problem, this patch must be installed on the DMS client. It does not need to be installed on the DMS server. This corrects a "simple_lock: time limit exceeded" panic in softclock_scan(). PROBLEM: (HPAQ30BCD) (Patch ID: OSF440-012) ******** 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: (BRO101278) (Patch ID: OSF440-015) ******** This is to correct a problem where a signal is delivered, but not responded to by the target process. PROBLEM: (BCPMC1GPQ) (Patch ID: OSF440-003) ******** This is to fix a panic of "get_color_bucket: empty buckets" when the sysconfig attribute "private-cache-percent" is non-zero. PROBLEM: (None) (Patch ID: OSF440-061) ******** Deleted files still occupy filesystem space until the last reference on that file gets closed. PROBLEM: (QAR 65033, QAR 61856, QAR 64040, SSRT0563U, HPAQC08NV) (Patch ID: OSF440-032) ******** A potential security vulnerability has been discovered where under certain circumstances users may gain unauthorized access. Compaq has corrected this potential vulnerability. PROBLEM: (QAR 62614) (Patch ID: OSF440-033) ******** This patch fixes a problem with the mount command where it sometimes kills other processes. This randomly occurs if the file where mount stores its pid, /var/run/mountd.pid, is out-of-date. PROBLEM: (BCGM50N91) (Patch ID: OSF440-120) ******** This patch fixes a problem where process accounting data was not written to the accounting file and the following message was displayed when the accounting file was on an NFS-mounted file system: NFS3 write error 13 on host This problem occurred on Dataless Management Services (DMS) client systems. PROBLEM: (QAR 73131) (Patch ID: OSF440-123) ******** Occasionally, 3rd-party drivers fail to configure when the first device configured is not zero. Additionally, some drivers support a maximum number of devices and a constantly increasing base controller number, caused by reloads, may cause the driver maximum to be exceeded. This can also cause loadable drivers to fail to configure. A loadble driver that is loaded/configured, unloaded/unconfigured, then re-loaded/re-configured gets increasing controller number values on each re-load. Most loadable drivers prefer (or require) the controller numbers to begin at zero and increase as the number of matching devices are found on a system. PROBLEM: (QAR 72971 CLD MGO104088) (Patch ID: OSF440-128) ******** Mount falls back to V2 when a portmap call for the NFS V3 port fails. This logic is incorrect; a portmap timeout doesn't indicate a lack of V3 support. PROBLEM: (QAR 72129, QAR 73203, CLD HPAQ500L1) (Patch ID: OSF440-132) ******** 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: OSF440-133) ******** 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: (73146) (Patch ID: OSF440-136) ******** This patch fixes the following KZPCC Raid controller problems: - The disklabel command fails when configuring partitions with non-zero offset - The disklabel -wr command fail with error message; "unknown device type". - Driver logged errors are not reset on subsequent access attempts, thus producing erronous results. - The iostat command does not display nor report the correct information for this device type. It also can produce a "simple lock timeout" panic on a multi-processor system. - Non-generic kernels fail to recognize logical units on boot. - A custom kernel build fails to recognize multiple controllers and their associated drivers - A system hang or deadlock condition caused by the controller not returning command responses due to the lack of resources. The driver can not process responses that it receives to free up the resources. - A kernel crash during SWCC reconfiguration and rescan operations. SWCC does not receive the expected results from the addition and deletion of logical units. - The sizer -r command fails to report the correct information for this device type. - The inability to generate crash dump information on this device type. - A "kernel memory fault" system panic that can occur when system is under a certain level of stress. - A system panic when creating and deleting a high number (1000's) of logical units. - Unable to install or boot from any ri devices that are not on the first unit on the first controller. PROBLEM: (MGO104022) (Patch ID: OSF440-142) ******** This patch fixes a problem where applications using the fcntl() system calls may appear to hang. PROBLEM: (MGO09365A,BCGM41MGB) (Patch ID: OSF440-143) ******** This patch fixes "simple_lock: time limit exceeded" panics. PROBLEM: (QAR 63384) (Patch ID: OSF440-148) ******** 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: (STLB42227) (Patch ID: OSF440-152) ******** 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: (HPAQ40343, HPAQ5062G, UVO20042) (Patch ID: OSF440-155) ******** 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: (CLD BCSM30WLD ,QARS 69170 70101) (Patch ID: OSF440-039) ******** 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: OSF440-067) ******** 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 66356) (Patch ID: OSF440-081) ******** 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: OSF440-085) ******** 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: (BRO101307 & BCSM11QV2 ,QAR 70038) (Patch ID: OSF440-095) ******** 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: OSF440-099) ******** 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 56967) (Patch ID: OSF440-104) ******** 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: (None) (Patch ID: OSF440-138) ******** This patch removes a Granularity Hint Regions (a.k.a., GH Chunks) restriction which may be encountered on AlphaServer DS20 and ES40 systems running the Digital UNIX V4.0F release. This restriction can reduce performance for certain data base applications. See the Patch Summary and Release Notes document for further information. PROBLEM: (QAR 73146) (Patch ID: OSF440-164) ******** This patch fixes several system hangs/crashes that could occur when the driver finds it necessary to re-initialize the KZPCC controller. (The driver contains code to do this re-initialization in case the controller stops responding to I/O requests for any reason.) PROBLEM: (MGO104025) (Patch ID: OSF440-144) ******** This patch fixes a system hang condition. All NFS related services may deadlock. PROBLEM: (QAR 72410) (Patch ID: OSF440-158) ******** 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: (QAR 70220) (Patch ID: OSF440-170) ******** Use of mmap can sometimes result in data corruption. PROBLEM: (QAR 73918) (Patch ID: OSF440-180) ******** 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: OSF440-182) ******** 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: (QAR 73589) (Patch ID: OSF440-187) ******** Because of a problem involving signal delivery, multithreaded applications can exhibit very poor performance or may even hang. 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 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 74449) (Patch ID: OSF440-206) ******** 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: OSF440-209) ******** 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: OSF440-221) ******** 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: OSF440-227) ******** This fixes a "simple_lock: hierarchy violation" panic from sigq_abort(). PROBLEM: ('QAR 74536') (Patch ID: OSF440-256) ******** 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: (QAR 74759) (Patch ID: OSF440-259) ******** This patch fixes a problem in which unmounting an NFS mounted directory can cause a user process to coredump. PROBLEM: ('QAR 73124, QAR 71118') (Patch ID: OSF440-268) ******** This patch fixes a problem where partitioned turbolasers return incorrect cpu data for cpus that are not in the partition. PROBLEM: (QAR 71139) (Patch ID: OSF440-272) ******** This patch corrects a problem that was causing degraded performance of the WAN Support for Tru64 UNIX layered product. PROBLEM: (56172) (Patch ID: OSF440-276) ******** Under certain conditions when using Asynchronous I/O, NULL pointer can be dereferenced in aio_unwire() causing an kernel memory fault panic. This fix eliminates this possibility. PROBLEM: ('QAR 74959') (Patch ID: OSF440-278) ******** This patch fixes a problem where ubc_msync() may not flush out all the pages in the requested range. PROBLEM: (BCSMA1923/75276) (Patch ID: OSF440-284) ******** 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: OSF440-305) ******** 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 69961) (Patch ID: OSF440-036) ******** This patch corrects a problem where a mount(8) command failure caused the operating system to crash. Instead, the failure will now only cause the AdvFS filesystem domain to shut down. The mount(8) command would fail when mounting an AdvFS file system because of an internal file system error. Now the file system shuts down the AdvFS file domain rather than crashing the system with a panic(). PROBLEM: (XIP100014, XIO100017) (Patch ID: OSF440-056) ******** This patch fixes a problem on systems using the AdvFS filesystem, where the system can panic with the panic string: "del_clean_mcell_list: no primary xtnt record". The stack trace will be similar to: advfs_sad del_clean_mcell_list bs_bfdmn_activate bs_bfdmn_tbl_activate fs_fset_get_info msfs_real_syscall msfs_syscall syscall _Xsyscall PROBLEM: (MGO103845, MGO103895) (Patch ID: OSF440-057) ******** This patch fixes an AdvFS Domain Panic that occurs with the following message on the console: "load_x_cache: bad status from bs_refpg of sbm" Example stack traces are as follows. Note: These are obtained from a system panic and not from the domain panic itself. 5 panic 6 advfs_sad 7 load_x_cache 8 sbm_find_space 9 alloc_from_bitmap 10 alloc_from_one_disk 11 stg_alloc_from_one_disk 12 alloc_copy_stg 13 migrate_normal 14 mig_migrate 15 bs_migrate 16 msfs_real_syscall 17 _Xsyscall PROBLEM: (HPAQC0B99) (Patch ID: OSF440-058) ******** This patch fixes a problem in AdvFS with auditing enabled. During a rmvol operation, the system can panic with a "kernel memory fault" with a stack trace that is similar to the following: > 0 boot() 1 panic(s = 0xfffffc00005b60a8 = "kernel memory fault") 2 trap() 3 _XentMM() 4 audit_rec_build() 5 audit_call() 6 msfs_audit_syscall() 7 msfs_real_syscall() 8 msfs_syscall() 9 syscall() 10 _Xsyscall() PROBLEM: (BCPM117VX, QAR 68804) (Patch ID: OSF440-059) ******** This patch fixes a problem where the "statfs" system call was reporting incorrect block usage on AdvFS filesets. As a side effect of this problem, the sendmail utility may sleep needlessly (waiting for space to become available). PROBLEM: (QAR 58502,QAR 59094,QAR 61399,QAR 67023) (Patch ID: OSF440-060) ******** This patch provides the following fixes and enhancements to AdvFS: - AdvFS volumes were not setting the default I/O byte transfer size to the preferred size reported by the disk drives. This caused I/O consolidations to be smaller than is optimal for the disks. This patch now assigns the driver's preferred I/O transfer byte size to all new AdvFS volumes created with mkfdmn and addvol. - AdvFS chvol read and write transfer size range was increased. With this patch the transfer size range is now between 16 and 3276 512-byte blocks. - The read-ahead algorithm was modified to improve performance under certain conditions. The algorithm now sanity checks the number of pages that it would attempt to prefetch and apply the following restrictions when doing its calculations: o Only read-ahead the number of pages remaining in the file. o Use a predetermined percentage of the buffer pool for use as read-ahead buffers. PROBLEM: (QAR 70283) (Patch ID: OSF440-112) ******** This patch fixes the problem where the system panics if AdvFS detects an inconsistency in the free list of mcells that is kept on a per-volume basis in an AdvFS domain. The panic string seen with this panic is "alloc_mcell: bad mcell free list". PROBLEM: (UVO106494) (Patch ID: OSF440-125) ******** This patch fixes a problem where "update" takes too long to sync mmap files when using an AdvFS file system. PROBLEM: (QARS 70619 68822 72776 72391) (Patch ID: OSF440-141) ******** This patch fixes the following two problems in AdvFS: - When a "log half full" or "log full" problem occurs, an entire system will panic. With this patch, only the AdvFS domain will panic instead of bringing down the entire system. - The erorr message "ftx_bfdmn_recovery:bad record size\n N1 = 1" is received when the wordCnt, as returned by lgr_read, is not enough to hold the ftxDoneLRT record that preceeds each log record in a log page. This caused the log page trailer to overwrite the ftxDoneLRT record in a log record. This patch now leaves enough room to write a log header at the end of a log page. PROBLEM: (CLD ALC-08618, QAR 69288) (Patch ID: OSF440-147) ******** This patch corrects a problem where a "can't clear a bit twice" panic occurs after an unanticipated system crash and an improperly handled AdvFS recovery operation. Note: Although the system will have paniced with a "can't clear a bit twice" panic message, the AdvFS file domain is often still good. On the following reboot the system will not mount the affected AdvFS domain complaining that the domain is in an "inconsistent state". To recover the domain, use dbx to set the variable AdvfsFixUpSBM to 1: dbx dbx>a AdvfsFixUpSBM = 1 dbx>quit Then use the AdvFS verify utility to check the domain. If the recovery is successful, verify will report no errors and the domain will be mountable. Please remember to set AdvfsFixUpSBM back to zero when you have finished recovering the domain. PROBLEM: (MGO104093,MGO104098,DSAT31W43, QAR 71350) (Patch ID: OSF440-082) ******** This patch corrects a problem in AdvFS which causes single-CPU systems to hang and causes multiple-CPU systems to panic with a "simple lock time limit exceeded" message specifying lock class name BfAccessTblMutex. This problem was originally reported when sys_check was being used to report on systems where there are more than 256 AdvFS filesets. The same problem could occur with any form of file access with that many filesets. PROBLEM: (MGO103900, QAR 71550) (Patch ID: OSF440-097) ******** This patch corrects a problem in AdvFS where unmounting a domain that is already in a panicked state could result in the following system panic message: log_flush_sync: pinpg error\n N1 = 5 Note: In this instance an I/O error (EIO = 5) caused the original domain panic. Stack trace: 6 advfs_sad() 7 log_flush_sync() 8 lgr_writev_ftx() 9 log_donerec_nunpin() 10 ftx_done_urdr() 11 ftx_done_n() 12 quota_deactivate() 13 msfs_unmount() Kernel Rebuild required. PROBLEM: (QAR 71271, QAR 71674) (Patch ID: OSF440-166) ******** This patch fixes a problem in AdvFS. AdvFS may skip filesystem recovery after aborted domain activation. PROBLEM: (CFS.67765,QAR 72623) (Patch ID: OSF440-174) ******** This patch corrects a kernel memory fault that occurs when entering the "mount -o dual" command. 9 _XentMM() 10 bs_bfdmn_sweep() 11 bs_bfdmn_activate() 12 bs_bfdmn_tbl_activate() 13 bs_bfset_activate_int() 14 bs_bfset_activate() 15 advfs_mountfs() PROBLEM: (QAR 74075) ******** This patch fixes a problem that may cause panics to occur when msfs_getpage() receives an error return from fs_write_add_stg() when attempting to write to an AdvFS domain that is out of disk space. PROBLEM: ('QAR 74052, QAR 73883') (Patch ID: OSF440-213) ******** This patch fixes a problem in AdvFS. A fileset is busy when attempting to unmount giving an EBUSY error even though the fileset has no open files. PROBLEM: (QAR 72949) (Patch ID: OSF440-220) ******** For ASE Disaster Tolerance systems only, a system may hung because a thread is reclaiming a vnode that is currently flushing the vnode's modified data to disk. The thread will be hung in filesystem flush synchronization. The I/O requests will not complete because ASE currently has suspended I/O processing and the thread that is blocked is an ASE process. This is a typical trace back, such as the dtwm process: (../dbx) t > 0 thread_block() ["../../../../src/kernel/kern/sched_prim.c":2352, 0xfffffc000 02bc31c] 1 thread_sleep(event = 0x0, lock = 0xfffffc00007a0780, interruptible = 0x0) ["../../../../src/kernel/kern/sched_prim.c":2002, 0xfffffc00002bbbb0] 2 _cond_wait(0x0, 0x0, 0xfffffc000040ec14, 0xfffffc00007a0780, 0xfffffc00003fa1c4) ["../../../../src/kernel/msfs/bs/ms_generic_locks.c":646, 0xfffffc000040ec10] 3 bfflush_sync(bfap = 0xffffffff80bd5110, waitLsn = struct { num = 0x4 }) ["../../../../src/kernel/msfs/bs/bs_qio.c":2541, 0xfffffc00003fa1c0] 4 bfflush(bfap = 0xffffffff80bd5110) ["../../../../src/kernel/msfs/bs/bs_qio .c":2662, 0xfffffc00003fa3c4] 5 msfs_reclaim(0x1, 0xfffffc00007414f8, 0x2, 0xfffffc0000754a10, 0x0) ["../../../../src/kernel/msfs/osf/msfs_misc.c":1967, 0xfffffc0000433f1c] 6 vclean(vp = 0xfffffc001971a600, flags = 0x4, newops = 0xfffffc0000753378) ["../../../../src/kernel/vfs/vfs_subr.c":2759, 0xfffffc00005170e0] 7 vgone(vp = 0xfffffc001971a600, ops = 0xfffffc0000753378) ["../../../../src/kernel/vfs/vfs_subr.c":2862, 0xfffffc0000517274] 8 getnewvnode(vops = 0xfffffc0000753378, vpp = 0xffffffffa1e0f670) ["../../../../src/kernel/vfs/vfs_subr.c":1901, 0xfffffc0000516148] 9 vdealloc() ["../../../../src/kernel/vfs/vfs_subr.c":1357, 0xfffffc0000515814] 10 vrele(vp = 0x112e) ["../../../../src/kernel/vfs/vfs_subr.c":2403, 0xfffffc0000516b80] 11 namei(0xfffffc001912b720, 0xffffffffa1e0f8f0, 0xffffffffa1e0f8e0, 0x0, 0xffffffffa1e0f7d8) ["../../../../src/kernel/vfs/vfs_lookup.c":829, 0xfffffc0000514590] 12 stat1(0xc98ed, 0x375c0162, 0x375c0161, 0x2bf62375c0161, 0xfffffc0000574218) ["../../../../src/kernel/vfs/vfs_syscalls.c":2942, 0xfffffc000051b00c] 13 stat(0x375c0161, 0x2bf62375c0161, 0xfffffc0000574218, 0x74, 0xfffffc0000574218) ["../../../../src/kernel/vfs/vfs_syscalls.c":2910, 0xfffffc000051af8c] 14 syscall(0x0, 0x0, 0x343df375c047c, 0x3ff803de850, 0x0) ["../../../../src/kernel/arch/alpha/syscall_trap.c":627, 0xfffffc0000574214] 15 _Xsyscall(0x8, 0x3ff800d88f8, 0x3ffc057e620, 0x1400664c0, 0x11ffff280) ["../../../../src/kernel/arch/alpha/locore.s":1500, 0xfffffc000056a954] PROBLEM: ('QAR 73644') (Patch ID: OSF440-244) ******** 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 73692, QAR 69021, QAR 74011') (Patch ID: OSF440-257) ******** This patch fixes a problem in the AdvFS system. A panic occurs with the following error message: lock_read: hierarchy violation PROBLEM: (QAR 75161) (Patch ID: OSF440-265) ******** This patch fixes a situation in which a domain that is being recovered can cause a slight Advfs memory leak. The problem can possibly result in a system panic whenever a domain is recovered via the mount command. The panic is due to a memory corruption. PROBLEM: (DJOB71733) (Patch ID: OSF440-289) ******** This patch fixes a problem where a single cpu system using AdvFS can hang in cleanup_closed_list(). PROBLEM: (MGO67225A,TKTBA0006,BCSMA1GK5,EVT79308A,STLBB3923) (Patch ID: OSF440-303) ******** This patch corrects AdvFS problems involving clone filesets. The statfs syscall (used by df) was incorrectly returning zero blocks USED for clones. The read-ahead code was incorrectly passing up opportunities to do read-ahead on clone filesets, resulting in a large performance penalty. PROBLEM: (MGO05514A, QAR 73107) (Patch ID: OSF440-168) ******** 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: (MGO44815A) (Patch ID: OSF440-191) ******** 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 72022, QAR 71836) (Patch ID: OSF440-107) ******** This patch fixes two separate problems: 1) When configuring the AlphaServer ES40, the ISA devices IDE and USB are not configured if a combo card is installed. The following error is seen during the boot process: shared_intr_add: attempt to share non-sharable interrupts, index 0xe ata_probe: handler_add failed 2) System panics with a kernel memory fault when installing on a AlphaServer DS20 A sample stack trace is listed below: 0 boot 1 panic 2 trap 3 _XentMM 4 linear_write_io_port 5 write_io_port 6 i2c_write_csr 7 i2c_reset 8 i2c_init 9 i2c_thread PROBLEM: (QAR 71921, QAR 72204, CLD INT-08869, QAR 71802, QAR 72427) (Patch ID: OSF440-159) ******** 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: OSF440-253) ******** 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 71292) (Patch ID: OSF440-088) ******** This patch fixes a problem where on systems with a Powerstorm 4D10T (ELSA Gloria Synergy) graphics board, sometimes the generic kernel (genvmunix) failed to configure the graphics driver giving the message: comet driver: could not register screen Other times, the system would crash during startup when configuring the graphics driver. PROBLEM: (QAR 71907) (Patch ID: OSF440-088) ******** This patch fixes a problem where on systems with a Powerstorm 4D10T (ELSA Gloria Synergy) graphics board, sometimes when the window system starts, the colors are incorrect. PROBLEM: (None) (Patch ID: OSF440-207) ******** This patch provides the driver support for the PCI To Ethernet/Graphics Combo Adapter (3X-DEPVD-AA) (also known as the ITI6021E Fast Ethernet NIC 3D Video Combination Adapter, InterServer Combo, or JIB). PROBLEM: ******** This patch fixes a problem where on systems with a Powerstorm 4D10T (ELSA Gloria Synergy) graphics card (SN-PBXGK-BB), the system could crash if an X11 application used cursors larger than 64x64. PROBLEM: ******** This patch fixes a problem where on systems with a Powerstorm 4D10T (ELSA Gloria Synergy) graphics card (SN-PBXGK-BB), when using 8-plane PseudoColor visuals, incorrect colors may be displayed. PROBLEM: (NONE) (Patch ID: OSF440-065) ******** Increased error detection within the driver. PROBLEM: (74484,74936,70605,71711) (Patch ID: OSF440-239) ******** This patch updates the emx Fiber Channel driver to revision 1.12, adds support for the KGPSA-CA adapter, and it also fixes several problems listed below. PROBLEM: (Qar 74484) (Patch ID: OSF440-239) ******** In an ASE environment, the driver was not appropriately restoring the link state after a LIP. This typically occurs on a cable pull scenario. When this problem occurs, all i/o through the adapter stalls and never completes. PROBLEM: (Qar 74936)(Patch ID: OSF440-239) ******** When connected to the new Pleiades II switches, the switch ports would consume target ids on the adapter's scsi bus. See the Patch Summary and Release Notes for further information. PROBLEM (QAR 70605) (Patch ID: OSF440-239) A kernel memory fault in routine emx_handle_els_request can occur with a stack trace similar to the following: 1: panic+260 2: event_timeout+236 3: xcpu_puts+76 4: printf+392 5: panic+696 6: trap+8660 7: _XentMM+84 8: emx_handle_els_request+5160 9: emx_ring_event+2216 10: emx_intr_deferred+372 11: emx_interrupt_thread+408 PROBLEM: (Qar 71711)(Patch ID: OSF440-239) ******** A switch nameserver bug was encountered that caused driver timeouts to improperly fire. This resulted in a scenario in which the system could hang at boot up, infinitely trying to probe the FC link. The last messages on the console would typically look like the following: emx0 at pci3 slot 4 KGPSA adapter: Driver Rev 1.09 : F/W Rev 2.20X2(1.12) : wwn 1000-0000-c920-a6 c8 PROBLEM: (TKTB90028, TKTBA0054) (Patch ID: OSF440-269) ******** This patch fixes a problem where on systems with a Powerstorm 4D10T (ELSA Gloria Synergy) graphics board, the graphics were not reset to console mode (the blue screen) when the halt button was pressed. PROBLEM: (73146) (PATCH ID:) ******** This patch fixes the following KZPCC Raid controller problems: - A kernel crash when newly created I2O_BS devices (via SWCC utility) were not being configured due to an inability to obtain a kernel controller structure. - The i2o_bs driver wasn't being notified as expected when the i2o bus code executed an iop reset. - ExecLCTNotify commands took longer than expected to complete. - SWCC observed that multiple devices were assigned the same dev_t value. - Observed that I/O was taking longer to complete than our expected timeout value allowed. - A kernel crash that occurs during the reset/recovery process. - An error message is displayed during boot which indicates the memory on the board cannot be configured due to no matching entry in the pci_option_data table. - Incorrect bus structs being returned by the get_bus(). The symptom being that things are not getting connected and configured as one would expect. Thus, in one instance, the boot device was no longer found. PROBLEM: (QAR 75510,75579,75788) (Patch ID: OSF440-294) ******** This patch updates the emx Fiber Channel driver to revision 1.13, correcting issues with Link initialization on the KGPSA-CA adapter. The link initialization problem had two footprints: a) If the cable is pulled from the switch, then reinserted, the switch led will flicker green, then turn amber and remain in this state until the system reboots. On the hosts, after roughly 1 minute from the time that the cable is pulled, access to the FC devices through that adapter will now fail. b) Occasionally, at boot, the following message will appear during the boot up messages: emx?: emx_linkup_timedout: link up timeout has expired All fibre channel devices attached to the link will not be visible. PROBLEM: (77583, 77156, 75510, 75579, 75788, 76179, 76295, 76513, 76795, 76796) (PATCH ID: OSF440-314) ******** This patch updates the emx Fiber Channel driver to revision 1.17, correcting issues with cascaded switches and Link initialization on the KGPSA-CA adapter. This driver revision also corrects some EMX DRIVER ERR mailbox warning messages that are occasionally seen during boot. General driver performance improvements are also contained. The cascaded switch problem would typically show itself, if present at boot, with the following message : "emxX: %s: link attach timeout has expired". The link would never initialize and devices on the adapter would not be seen. If the problem occurred post boot, devices would simply appear to be non-existent. The link initialization problem had two footprints: a) If the cable is pulled from the switch, then reinserted, the switch led will flicker green, then turn amber and remain in this state until the system reboots. On the hosts, after roughly 1 minute from the time that the cable is pulled, access to the FC devices through that adapter will now fail. b) Occasionally, at boot, the following message will appear during the boot up messages: emx?: emx_linkup_timedout: link up timeout has expired All fibre channel devices attached to the link will not be visible. The emx mailbox warning messages, appear during boot at the time of the emx adapter is probed. The warnings typically were one of the following messages: a) emx0 at pci1 slot 3 KGPSA-CA : Driver Rev 1.12 : F/W Rev 3.00(1.10) : wwn 1000-0000-c921-1863 EMX DRIVER ERR: emx0: emx_mbx_event - Unsuccessful mailbox command 0x17 - 0x17 : 0xfffd Unknown Status b) emx0 at pci1 slot 3 KGPSA-CA : Driver Rev 1.12 : F/W Rev 3.00(1.10) : wwn 1000-0000-c921-1863 EMX DRIVER ERR: emx0: emx_init_link - Send Init Link command failed (0x200 00 - 0x05 : Mailbox Command Incomplete) PROBLEM: (HPAQC032X/QAR 66952) (Patch ID: OSF440-018) ******** 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 512 byte kmembucket corruption. PROBLEM: (QAR 69554, QAR 70444, QAR 72011, QAR 72852, QAR 73439) ******** This patch fixes the following Universal Serial Bus (USB) problems: - The USB mouse no longer functions after resetting the Xserver. - System panics may occur inerror 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 46648 QAR 70765>) (Patch ID: OSF440-073) ******** This patch fixes a system hang in which there is a large number of pending ioctl's on the streams queue. PROBLEM: ('QAR 51449, QAR 70650') (Patch ID: OSF440-219) ******** 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: OSF440-110) ******** 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: (UVO58394) (Patch ID: OSF440-116) ******** This patch fixes a problem most frequently encountered by the ppp daemon /usr/sbin/pppd, when the ppp connection is terminated. When run in debug mode, an exiting pppd will log a message of the form listed below when the error is encountered. >> May 25 12:29:17 dragon pppd[2525]: ioctl(SIOCDIFADDR): Invalid argument Successive attempts to bring the ppp interface will fail, and executing 'ifconfig -a' will show that IP addressses still configured on the ppp interface for the ppp connection that was terminated. PROBLEM: (DEKB20145, UTO101928) (Patch ID: OSF440-070) ******** 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: OSF440-071) ******** 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: (CLD HPAQ61WN1) (Patch ID: OSF440-216) ******** 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: (CLD EVT102855, QAR 73939) (Patch ID: OSF440-196) ******** 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: OSF440-240) ******** 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: OSF440-270) ******** 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: OSF440-292) ******** This patch consists of changes necessary for AV firewall 98 to pass ICSA certification. PROBLEM: (HPAQ7003V QAR 73588) (Patch ID: OSF440-160) ******** 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: (None) (Patch ID: OSF440-295) ******** This patch involves virtual mac addressing.