cat << '@EOF' # @(#) OBSOLETE: Thu Mar 26 16:58:34 EST 1998 replaced by PHKL_14556 ####### ###### ##### ####### # ####### ####### ####### # # # # # # # # # # # # # # # # # # # # # # # # # ###### ##### # # # ##### # ##### # # # # # # # # # # # # # # # # # # # # # # # ####### ###### ##### ####### ####### ####### # ####### ###### ####### ###### # # ##### ####### ###### # # # # # # # # # # # # # # # # # # # # # # # # # ###### ##### ###### # # # # ##### # # # # # # # ####### # # # # # # # # # # # # # # # # # # ####### # ####### # # ##### ####### ###### ###### # # # # # # # # # # ###### # # # # # # # ###### # ###### # # # # # # # ####### ####### ##### # # # # # # # ## # # # # # # # # # # # # # # # # # # # # ###### ####### ### # # # # ###### ###### ###### # # # # # # # ####### # # # # # # # # # # # # # # # # # # # # # # # ####### ####### ##### # ##### ##### ##### #-------------------------------------------------------------------- @EOF # This is a shell archive. Remove anything before this line, # then unpack it by saving it in a file and typing "sh file". # # Wrapped by HPUX Patch Admin on Thu Mar 26 16:58:34 1998 # # This archive contains: # PHKL_14508.text # LANG=""; export LANG PATH=/bin:/usr/bin:/usr/sbin:/usr/ccs/bin:$PATH; export PATH echo x - PHKL_14508.text cat >PHKL_14508.text <<'@EOF' Patch Name: PHKL_14508 Patch Description: s700 10.10 VM, PM, T520, LVM, SCSI, UFS cumulative patch Creation Date: 98/03/11 Post Date: 98/03/25 Hardware Platforms - OS Releases: s700: 10.10 Products: N/A Filesets: AdvJournalFS.VXFS-ADV-KRN LVM.LVM-KRN OS-Core.CORE-KRN OS-Core.KERN-RUN ProgSupport.C-INC Automatic Reboot?: Yes Status: General Release Critical: No (superseded patches were critical) PHKL_14296: PANIC PHKL_14222: PANIC OTHER The panics discussed above may not occur in a uniprocessor system. Since race conditions exist, the problems could manifest themselves in unexpected ways. Hence the need to provide this patch for the 700 systems. PHKL_13728: HANG PHKL_13280: OTHER Quantum DLT4500/4700 will not operate properly without this patch. PHKL_13153: HANG PHKL_12606: CORRUPTION PHKL_12429: HANG PHKL_12363: HANG PHKL_12061: HANG PHKL_11988: CORRUPTION PHKL_11850: PANIC The system panics when a process tries to dump core. PHKL_11543: PANIC PHKL_11523: CORRUPTION PHKL_11432: CORRUPTION This patch when used with the appropriate SG/DLM version will avoid any potential windows for data corruption during reconfiguration in a HA cluster env. using SG or DLM PHKL_11121: PANIC PHKL_10232: PANIC PHKL_10201: PANIC PHKL_9420: PANIC PHKL_8393: HANG This patch adds a new feature to LVM. The feature is provided to customers who need the option to limit the time LVM waits for powerfailed disks in given logical volumes to return. PHKL_8359: HANG PHKL_8292: HANG PHKL_8201: HANG PHKL_8082: ABORT PHKL_7868: PANIC PHKL_7615: CORRUPTION PHKL_7458: PANIC PHKL_7378: PANIC PHKL_7301: PANIC PHKL_7244: OTHER Performance problems caused by excessive protection id faults PHKL_7187: CORRUPTION PHKL_7167: ABORT PHKL_7164: ABORT PHKL_7090: PANIC HANG Panic occurs only when using an unsupported device PHKL_7050: PANIC PHKL_6969: PANIC PHKL_6748: HANG PHKL_6643: PANIC PHKL_6484: PANIC CORRUPTION Path Name: /hp-ux_patches/s700/10.X/PHKL_14508 Symptoms: PHKL_14508: mprotect() system call causes high system time resulting in poor system performance. PHKL_14296: Trap panic in lv_resyncpv from LVM. Lots of "pvnum is POWERFAILED" messages. PHKL_14222: The panic may not occur in a uniprocessor system. However, to be on the safe side, this patch must be made available. This defect causes a panic in a multi processor system when two processes are doing mmap/munmap on portions of the same file using a sliding window. The user will see the system panic with "panic: rmfree: overlap" message. The stack trace will be as shown below: panic+0x10 rmfree+0x268 quaddealloc34+0x30 hdl_detach+0x108 detachreg+0x3c do_munmap+0x190 do_munmap+0x84 foreach_pregion+0xec munmap+0x74 syscall+0x1a4 A different panic could occur due to an unrelated race condition when mmap/munmap is called. This second panic is a result of data page fault. The stack trace in this case will be as shown below: panic+0x3C report_trap_or_int_and_panic+0x8C trap+0xC18 $RDB_trap_patch+0x20 smmap+0x8F0 syscall+0x1A4ce PHKL_13728: A system "HANG" occurs whenever a large number of users log In/Out at the same time. The password file has large number of entries and the system can have around 1000 concurrent connections. Problem occurs when many processes try to access the same file concurrently, the inode locking routines start dealing with the contention very inefficiently. PHKL_13280: Quantum DLT4500/4700 do not show up properly on ioscan. PHKL_13153: Processes hang intermittently due to process deactivation and reactivation. PHKL_12606: VxFS file system corruption with the following message: vxfs: mesg 003: vx_mapbad - /adabas/P01 file system free extent bitmap in au 20 marked bad PHKL_12429: After call to pstat_getmsg(), all accesses to the message queue hang. PHKL_12363: Some workloads cause T520 machines to hang with no response to any system input and without response to console transfer-of-control. T500s and other machines do not exhibit this behavior. PHKL_12061: UFS hangs with heavy use of a filesystem branch by multiple processes. The hang is due to a three way deadlock with inodes and bufs being held but not released. This shows up with the buf being both B_BUSY and B_DONE but not being released. PHKL_11988: Under the right conditions of high interrupt load, the first four bytes of a 512 byte transfer could be corrupted. An unrelated change also increases the number of retries performed on read and write requests. This could help successfully read or write data on marginal or defective media. PHKL_11850: System panics with kernel stack overflow when processes dump core PHKL_11815: LVM bad block relocation interferes with media error recovery on EMC disk arrays. PHKL_11543: - Fixes an intermittent panic when opening a tape device on the HSC bus - Improves performance for wide SCSI tape devices connected via the HSC bus - Allows DLT4000 devices to perform odd-sized writes PHKL_11523: When using large environments greater than 20 kbytes user applications dump core sometimes, or get bad data. PHKL_11432: Ghost IO kernel patch : A customer might find corrupt data on disk after a Service Guard or Distributed Lock Manager fail-over. This defect is specific to the HA cluster environments. PHKL_11121: 1. Although users can now exec() programs with up to 2047998 bytes of argument and env strings, sysconf(_SC_ARG_MAX) continues to return 20478 bytes as the maximum length of all arguments and env strings. 2. Expanding the argv/envp string capacity to 2048000 bytes exposed an existing bug in pstat_cmd(). Code in that rou- tine could scan beyond the end of a particular internal 20480-byte buffer, resulting in a trap and system panic. PHKL_10873: HP-UX didn't log any error when a user process: 1. encountered a swap space shortage 2. exceeded a system resource limitation Processes were terminated but the errors were not recorded on any of the system log files. PHKL_10827: pstat_getlv() returns information about first VG only. PHKL_10419: When reading a tape on a 7980S tape drive, reading a partial record fails and returns I/O Error. If a tape device receives a bus reset the device will rewind. Following this, when the device is closed, the driver will write EOF marks at the beginning of the tape causing the remaining data to be unusable. When a tape device is opened for write access and the media is write protected the driver returns I/O Error, which can be ambiguous. EPERM (Permission denied) is a more descriptive error. PHKL_10270: The total length (including terminators) of all argv and env strings passed to a newly-EXECed process was 20480 bytes. If a greater length was detected, the exec() failed with E2BIG. PHKL_10232: panic: kernel scheduler interrupt PHKL_10201: System panic (data page fault) when debugging processes over an interruptable NFS mount point. PHKL_10103: Syslogd fills up file system. PHKL_9420: System panics including data page fault. PHKL_9073: Applications using Memory Mapped Files were performing poorly when mapping thousands of pregions to the same file. The problem would mainly be noticed with shared (MAP_SHARED) and exclusive (MAP_FIXED with address in the process private data space) mappings. This patch is required when using the Object Store database product from ODI. PHKL_9009: Geometry problem reports that media with 77 tracks has 80 tracks, but you cannot write to tracks 78, 79, and 80. The data loss with the "dd" command only occurs on newest workstations with extreme load of I/O processes. PHKL_8928: Unable to mprotect non-mmap(2) addresses. PHKL_8920: On hp-ux 9.04 (S800) and 10.x (S700/S800), large MP systems with a high switch rate result in unacceptable level of KI CPU overhead. Moreover, the KI has the processor spinlock during this time with interrupts disabled! We have observed on a 10.10 TPC benchmark system that enabling the swtch trace in the KI reduces TPC throughput by 10%. PHKL_8906: "SCSI: Unhandled interrupt" and resulting bus reset can cause panic during boot of 710, 715/50, 720 and 725/50 workstations if root disk is LVM and on built-in SCSI bus. It's theoretically possible for the bus reset to cause data corruption on QUANTUM LPS525S disks on the bus. Some M/O drives will not work on the above systems plus 705, 715/33, 730, 735 and 755. PHKL_8790: Running strings on a raw sar(1) output file can show some printable strings (sar ignores these). PHKL_8753: Fixes a bug with Exabyte tape drives that caused append writes (those not at BOT) to be in non-compressed mode when using the BEST density setting. PHKL_8714: After call to pstat_getmsg(), all accesses to the message queue pstat_getmsg() was called hang. PHKL_8504: This patch changes the behavior of the open() call with a write protected tape. The open() will now fail with EIO if the mode is not O_RDONLY. PHKL_8461: The directory entry for a file system object (FSO) will no longer be readable once the contents of that object have been deleted. This was not shipped as a separate patch. PHKL_8393: This change supports a new -t switch for lvchange allowing the administrator the option to limit the time lvm holds i/os to be retried on logical volumes when disks are powerfailed. Without using this option, LVM will hold the i/os as long as there is is one disk where the data resides which may eventually return. Using this option would cause LVM to give up on the powerfailed disk and return i/o errors to the user application using the logical volume. This feature is obviously not to be used indiscriminately. For many High Availability applications, having i/os held in kernel indefinitely is not acceptable. Most customers should not need to use the new switch. PHKL_8359: Select timeouts are retried forever, i.e. I/O's never complete when a device is removed. SCSI bus hang and reset. PHKL_8292: When multiple nfsd's access the same file simultaneously, they hang in a deadlock. PHKL_8201: MP system hangs during panic. The LED shows system staying at INIT CB0B. Machine needs to be TOC'ed to save the core dump. PHKL_8082: LVM may return I/O's with errors instead of sending them to an alternate link. This patch also facilitates using "vgreduce -f" for physical volumes which have alternate links; without this patch "vgreduce -f" is not allowed on LVM disks with alternate links. PHKL_7882: Without immediate reporting enabled a DLT tape drive will take several seconds for each filemark written. If a user application is writing many filemarks to a tape the performance will be poor. This patch enables immediate reporting of filemarks, which should improve performance for an application that writes many filemarks to a tape. PHKL_7868: lvreduce(1M) may cause a system panic, if it is used to reduce an lvol which was left inconsistent by a prior LVM operation. lvreduce(1M) could not be used to remove lvols that were somehow corrupted, if it was, the command would cause a system panic. PHKL_7668: Several types of symptoms may occur: - logins on NFS clients may receive incorrect access on NFS servers - files from NFS servers may appear to be owned by the wrong logins on NFS clients - setuid and setgid binaries available on NFS servers may allow client logins to run with incorrect access PHKL_7637: Too long request timeout, 2 min. 30 sec. on EISA SCSI. Missing SIOC_ABORT and SIOC_RESET_DEV functionality. Mediainit failure. PHKL_7615: Silent data loss. Requires data read & compare to detect. PHKL_7458: "panic trap type 18" problem on HP-UX 10.X NFS file server with short file name file system. PHKL_7378: Fixes a problem with a panic caused by use of non-supported Exabyte tape drives. Adds support for Quantum DLT-2000, DLT-4000, and DLT-6000 tape drives. PHKL_7334: Panic during power failure recovery on non-UPS systems. PHKL_7301: System panic with "Data page fault" in set_purge_SIDS() when using mprotect(2): trap type 15, pcsq.pcoq = 0.249f0c, isr.ior = 0.3c panic: (display==0xb800, flags==0x0) Data page fault panic+0x10 report_trap_or_int_and_panic+0x8c trap+0x72c set_purge_SIDS+0x0 invalidate_protids+0xbc hdl_changerange+0x1e0 hdl_mprotect+0x398 do_mprotect+0x140 foreach_pregion+0xe8 mprotect+0x78 syscall+0x1f4 This panic was mostly observed on systems running SAP R/3. PHKL_7244: MP T500 running 10.01 or 10.10 with Informix database exhibits poor performance and high levels of protection id traps after reboot. Problem exhibits itself after stopping/restarting application until system rebooted. /usr was a JFS VxFS file system. PHKL_7187: lvmerge could merge an lvol back with all PEs marked as current and yet the syncing of stale LTGs had failed. lv_recover_ltg(k), which does the syncing, had no mechanism to return error to lv_table_reimage(k). lv_table_reimage(k) therefore returns success when this may not be the case. PHKL_7167: program with itimer gets SIGILL when debugger uses ptrace PT_SINGLE PHKL_7164: Performance suffers for sequential i/o with LVM and disk arrays with stripe depth > 64k. Edison ARM utilities (and diagnostic tools that require exclusive access to a device) fail reporting device busy (EBUSY) even when all volume groups accessing the device are deactivated. Edison ARM utilities (and diagnostic tools that require exclusive access to a device) fail reporting device busy (EBUSY) if the device was ever used as a Service Guard Cluster Lock disk. PHKL_7124: For very large /etc/passwd files, passwd command may return EDEADLK and print an error message about lockf deadlock detection. PHKL_7090: panic: (display==0xb800, flags==0x0) Data page fault panic: (display==0xbf00, flags==0x0) Non-access data TLB miss panic: callout table overflow System hang with empty CD-ROM drive in /etc/fstab. Mediainit fails after two hours. Autochanger devices don't show up in ioscan output. SCSI_DISK2 doesn't work with unmounted QUANTUM PD* disks. (note: it isn't expected to work with mounted ones) TEAC floppy driver doesn't identify 5.25" 360K format. Ioscan shows incorrect s/w, h/w status for sctl driver. Bus hang resets or worse with QUANTUM PD* disks. Bus hang resets with Quantum VP3215 disks. Driver hang for single device on MP systems. PHKL_7050: pvmove leads to panic: lv_reducelv extmap, when the mirrored logical volume contains unallocated physical extents (might caused by previous unsuccessful pvmove operation (kill -9). vgchange: Couldn't activate volume group "/dev/vgpam": Invalid argument when users is doing deactivate a volume group, the system panic with "lv_cache_deactivate inflight". PHKL_6675 fixes some case and this patch fixes a special case. PHKL_6969: system panic when vgchange -a y VG with bad sectors on the bad block directory area. PHKL_6852: When a customer has a /etc/lvmtab which is out of data with running kernel, this will cause vgcfgbackup to fail. PHKL_6801: None. PHKL_6748: Rename deadlock: This deadlock occurs in the following situation: Process 1 is moving a directory to a new parent directory at the same time as Process 2 is doing a lookup on the new parent directory Process 1's directory is being moved into. Both processes will sleep forever and all accesses to both directories will also sleep. PHKL_6653: None. This is a pstat enhancement. PHKL_6643: The system will panic if an access is made to an Exabyte tape drive other than those models that are officially supported. PHKL_6484: itrunc: no space panic when truncating a file with a hole in it on a full file system. If the truncation makes the new end of the file fall into the middle of the hole, a disk block must be allocated for the end of the file, and if one can't be allocated, itrunc() would panic. This fix has itrunc gracefully backout instead. Possibility of random file system corruption or data loss when removing ACLs or files with ACLs has also been fixed. Defect Description: PHKL_14508: Use of a global mprot_list_lock lock caused spinlock contention as it's one lock per system and hence poor system performance. It is still used to protect mprot_list. The fix was to use another pool of locks called prp_hash_locks for protection ids. The hashing function chooses different locks (from this pool of hash locks) for different range of addresses thus removing dependency on the various locks that should be acquired before the protection ids for a given page are changed. PHKL_14296: LVM panic the system when lv_lvhold return bad status to the caller(lv_resyncpv). PHKL_14222: As mentioned above, the panics may not occur in a uniprocessor system. However, since the race condition exists, this patch must be provided. Both the problems (panics) discussed earlier occur in a multiprocessor system when two processes are doing map/munmap on portions of the same file using a sliding window. Panic-1 -------- The panic is caused by a race condition in hdl_mmf_attach() in hdl_policy.c in the machine directory. The race condition is in case-3 of "overlapping" pregions. In this case, the new process' pregion starts within and extends past the existing process pregion. In the original implementation, we were releasing the region lock to call mapvnode(). At that time, the new pregion is not yet placed on the region's pregion-list and hence opens a window for a race condition. With the fix, the pregion is placed on the region's pregion-list before releasing the region lock, thereby eliminating the race condition. Panic-2 -------- The second panic is caused by a race condition in the error path of smmap() in vm_map.c in the sys directory. In a code segment following the label "bad", in the case where vnode is associated with the region, we release the region lock to be able to call dectext(), we copy the file descriptor from the vas, acquire the file-table lock and then check that the file descriptor is not zero before proceeding further. In the meantime, the file descriptor could have been closed and hence dereferencing it would cause a data page fault. To avoid this race condition, we need to postpone calling dectext(), which is what the fix does. PHKL_13728: Classic "thundering herd" problem was made worse by the fact that the first thing each woken process did was to try to lock a "COMMON" spinlock. A process that gets the spinlock first, locks the INODE and releases the spinlock has to try hard to be able to get the spinlock second time while it tries to unlock the same inode. Hence the inode was locked whilst no useful work was being done. PHKL_13280: Quantum DLT4500/4700 were not recognized as multilun devices. PHKL_13153: The scheduler decides the system is thrashing in some occations when pageout rate is low and free memory is plenty and hence deactivates certain processes. PHKL_12606: The following steps lead to the root cause of the problem: 1. file system corruption is related to reorg activity. 2. inproper handling of indirect address extents on files. 3. 'sometimes' vx_copy_blk() doesn't seem to copy the block and apparently no error was reported. 4. VxFS does a flush prior to the copy and then when it is all done, the extents are freed. But On HP-UX, the file data is accessed via the file vnode and flushed by an invalidating putpage, while indirect blocks and directories are accessed via the file system device vnode. For regular files, vx_extflush() will exit without doing anything, so there will still be buffers laying around in the cache hanging off the system device vnode. PHKL_12429: pstat_msginfo() calls msgconv() to convert the offset into a message queue pointer. msgconv() then locks the queue and returns a pointer to the queue's lock. pstat_msginfo() had not been released the lock of the message queue. PHKL_12363: Certain workloads cause T520s to lock-up external I/O. These hangs are ordinarily very uncommon, but certain workloads seem to bring them out. Reproduction of the defect is thus very difficult under normal circumstances. It is recommended that all customers with T520 machines apply this patch, in order to avoid uncovering the problem as workloads change. This patch may be applied to other, non-T520 machines, but they will only see the effects of the patches superceded by this one---this patch will not affect them. PHKL_12061: Problem was due to incorrectly releasing an inode while still holding a buf. This violates the rule which would prevent a deadlock from happening. The problem shows up as a three way deadlock with two processes marching back to the root from the leaves via ".." and another process marching from the root to the leaves. This creates a a deadlock of processes waiting for the same inode and holding the wanted buf at the same time. PHKL_11988: The data in the DMA buffer is not flushed from the data cache to memory before the dma engine fetches it. When that happens, the dma engine will fetch incorrect data from memory. This usually results in four bytes of corrupted data. The corrupted data will begin on a 512 byte boundary. An unrelated change increases the number of re-tries for read and write requests to the floppy. PHKL_11850: When an application dumps core and a pagefault occurs, the kernel stack is small and hence it panics the system. The reason is that on 700 system , the stack size is 8K whereas on an 800 system, this is 12K which is why this problem is seen on a 700 system ONLY. The fix was to increase the size of kernel stack similar to the one that 800 system had (12K). PHKL_11815: When an EMC disk array returns an EMEDIA error to LVM, LVM at a minimum marks the block as bad in the bad block directory (and, normally, relocates the block to a new location on disk.) This is detrimental to the functionality of EMC disk arrays, since the bad blocks can be fixed on the hardware itself. PHKL_11543: - The tape driver will occasionally panic on the open of a tape device which is attached to the HSC bus. The panic is caused when a tape device responds with a "check condition" very early in the open process. The problem is intermittent and can not be reliably reproduced. - Patches PHKL_10417 through PHKL_10422 changed the way the driver negotiated with the device for narrow (8 bit) or wide (16 bit) transfers. This fixed a problem with 7980S tape drives, but caused the driver to never correctly negotiate for wide transfers. Any wide device on a wide interface would suffer a performance degradation because the driver was throttling it down to 8 bit transfers instead of 16 bit transfers. - Because of problems with transfering an odd number of bytes over a wide bus, the driver prevents doing an odd sized write to a wide device. The DLT4000 is a narrow device, but it is differential so it attaches to a wide bus. The driver was looking at the bus size, rather than the device type, to determine the transfer size and so it was blocking odd-sized transfers to DLT4000 devices even though these should be allowed. Writing an odd-sized record to a DLT4000 would return an EIO error. PHKL_11523: During the final stages of EXEC, the kernel has to relocate the argv and envp pointers to point to the argument and environment strings which reside in the user stack. There was a defect in this reloction code that caused all pointers pointing to locations in the user's stack at offsets of 20K from the base to have bad addresses. PHKL_11432: When a node dies in an HA cluster environment, there may be IO requests still pending on its intellegent disk IO boards (eg. Wizard card). The IO boards may continue to write this stale data to disks. This process is known as "Ghost IO". This situation may lead to data corruption when the other nodes in the HA cluster detect the failure, apply recovery logic, and perform IO to the disks. There is a need for detecting the death of a node and reseting the bus. This feature only impacts Service Guard/Distributed Lock Manager environments. PHKL_11121: 1. An earlier patch, PHKL_10177, expanded the actual space available to execve(), but failed to modify sysconf() to report the new maximum. This patch corrects that. There is no change to module kern_exec.c (home of execve()) other than a revision roll to ensure its inclusion in this patch. 2. pstat_cmd() scans the argv/envp buffer so that ps can display the first 64 characters. A limit error allowed the routine to scan until it found a null string terminator, even if that was well beyond the 64 bytes needed. This de- fect was unnoticed as long as there was only one 20480 byte buffer, since we were guaranteed to find a null terminator before (or at) the end of the buffer. With many internal 20480 byte buffers making up the total 2048000 argv/envp space, a particular argv/envp string can straddle more than one buffer. If these buffers are not contiguous, and pstat_cmd() scans off the end of a buffer before finding a null string terminator, it may reference an illegal memory address. That results in a trap and system panic. PHKL_10873: This patch provide support for logging of errors in memory management related system calls such as brk/sbrk as well as handling error cases during stack growth. Errors are logged on the system console (dmesg) and also in syslog. The variable mman_elog, which defaults to OFF, is used to control the logging. This variable can be set through adb at a customer site to enable error logging. PHKL_10827: pstat_lvinfo() algorithm describes that if the number of entries requested is non-zero, it will traverse through all the Volume Groups (VG) to report the open logical volume information. The test (lvix >= vgp->num_lvols) is used to test if LV index is covered by VG. This should be (lvix > cur_lvs) which is lvix compared to the number of open logical volumes. Also there can be some volumes that are configured but not mounted.(the VG where they reside is still ACTIVE). The fix now shows the all the logical volumes that are open in the system.(within any Volume Group). The defect can be reproduced by writing a program based on pstat_getlv() to display information about Logical Volumes configured on a system. The output of this program only shows logical volumes for the first volume group. PHKL_10419: 7980S problem was caused by a change in the SCSI interface driver which caused the interface to negotiate for synchronous even when the driver had not enabled that negotiation. The 7980S drive is not SCSI-2 compliant, and has problems with synchronous negotiation in some places. Other changes were enhancements - no defect. PHKL_10270: The internal buffer within the kernel was created with a length of 20480 bytes, with no provision for increasing its size. This patch provides for up to 100 such buffers, with all but the first allocated only if required (that is, if more than 20480 bytes of argv/env information is found). Thus, exec() now supports up to 2048000 bytes of argv/env information. PHKL_10232: Running an EXEC_MAGIC program using a stack pointer in the first quadrant could result in a panic: kernel scheduler interrupt. This problem would only be seen on UP systems. PHKL_10201: When debugging processes over an interruptable NFS mount point there was a window during which a traced process could sleep in exec() while the debugger would exit clearing the traced bit and freeing the ptrace data structure. Upon wakeup, the no longer traced process would panic the system trying to dereference a NULL pointer. PHKL_10103: msg_bufx was set to the value over MSG_BSIZE. PHKL_9420: The exit() kernel routine was freeing a memory resource without reseting a pointer to NULL. The previously freed memory could then still be referenced thus causing memory corruption in other parts of the kernel and leading to system panics. PHKL_9073: The pregions list associated to a shared region was designed as a doubly-linked list thus providing a linear access to pregions in the list. This design was not suited to deal with thousands of pregions and the doubly-linked list was replaced by a skip-list for faster access. Two other changes were required to deliver better performance: the algorithm to check the total virtual address space and the routine to locate the stack pregion were enhanced. PHKL_9009: Using floppy media with 77 tracks, the ioctl commands will report 80 tracks, but you cannot write to the last tracks. The write corruption occurs on PC floppy media during loop of dd commands and pdc_model calls under heavy I/O load. The problem occurs when the floppy-disk-controller (FDC) enters unknown state during high numbers of interrupts. Problem only found under extreme load conditions on newer workstations with very fast processors. PHKL_8928: Currently mprotect() restricts the addresses it will accept for protection. Only those addresses returned from a call to mmap() can be used for mprotect(). However there are customers who need to mprotect addresses in the data, stack and shared memory segments; objects not created vi a call to mmap(). So mprotect() was opened to allow mprotect'ing on data, stack and shared memory objects. Text is not allowed unless the executable is EXEC_MAGIC. PHKL_8920: The KI swtch trace generation code in the kernel walks all pregions in the vas of the swtched process. PTC's MI and performance tools do not need rss values updated every context switch - the extra overhead is not worth the small increase in accuracy. It is sufficient to copy the pid's vas_t->va.prss+vas_t->va.rss (private + shared) value which is updated every 5 seconds by statdaemon. PHKL_8906: The c720 driver does not lisc->sclk soon enough. Chip timing parameters are set up incorrectly. PHKL_8790: pstat_dynamic() allocates a buffer but fails to initialize it before using it. Buffer ends up containing some garbage. This is a cosmetic defect only; sar ignores the uninitialized spaces. PHKL_8753: The Exabyte bug can be reproduced by writing a large (100 Mb) file to an Exabyte drive using the 'BEST' device file in 'no rewind' mode, then writing the same file again to the same device. The first write will be substantially faster because it is compressed while following writes are not compressed. PHKL_8714: pstat_msginfo() calls msgconv() to convert the offset into a message queue pointer. msgconv() was changed to not only do the conversion, but to lock the queue and return a pointer to the queue's lock. pstat_msginfo() had not been changed to take into account msgconv()'s new behavior. PHKL_8504: Before this patch the open() call did not look at media write protection. A write() to a write protected tape would fail, but an open() with FWRITE mode would succeed. This change was made to make the GSC driver behave the same as the NIO driver. PHKL_8461: The name of a file in a directory entry is not cleared when the file object itself is deleted (say, with rm(1)). To demonstrate this: $ mkdir test $ cd test $ touch delete_me $ ls delete_me $ rm delete_me $ ll total 0 $ strings . # Examine strings in cwd. delete_me # Filename is still in cwd entry. This was not shipped as a separate patch. PHKL_8393: LVM makes every effort to avoid returning an error to user applications. LVM will hold onto an I/O to retry it later if there is even the smallest hope that the device will return. If a disk simply does not respond and no bad writes made it to the media, LVM will hang onto the i/o as long as the disk does not respond with an indication that there was actually a bad write or read. The patch provides a new feature that allows administrators the option of limiting the time lvm will wait for disks in an logical volume to return, and cause lvm to return i/os with EIO instead of hanging onto them indefinitely. PHKL_8359: Select timeouts are retried forever. B_NDELAY should eliminate retries on select timeout. Zalon chip bug results in SCSI bus hang. PHKL_8292: ufs_bread(), called by nfs server routines, prematurely unlocks the inode while the caller still owns the buffer. This opens a window for another process to grab the inode lock. Deadlock occurs when the process owning the buffer tries to access the inode again and the process holding the inode waits for the buffer to be available before it can release the inode lock. The fix is to delay the inode unlocking in ufs_bread() until the inode is no longer needed. PHKL_8201: In 10.X, interrupt distribution is implemented to allow reassignment of interrupt processors to I/O interfaces for workload balancing. The assigned interrupt processor for an I/O interface may or may not be the system monarch depending on the the number of I/O cards and processors available. During a panic, if the panic processor is the system monarch, it will flush the buffer cache on its way down. If the interrupt of the disk it is syncing is serviced by one of the other processor(s), the I/O completion interrupt will not be received and the ISR will not be called because the other processor(s) are TOC'ed at this point. Without the ISR to signal biodone(), the biowait() sleeps forever. The fix is to add a timeout in the panic_boot path to break out from the hang in disk sync'ing and continue with the reboot. PHKL_8082: Without this patch LVM will not retry failed i/os on alternate links unless the error is one that denotes that the device is offline or powerfailed. Other errors, are not retried on an alternate link and may cause LVM to report the error to users applications. Typically, customers with unmirrored lvols using multiported devices like the HP3232 (Nike) disk array would see the problem when an EIO error is reported to LVM from the underlying device driver due to a device or driver problem. In this situation LVM would report the EIO to user applications without trying any available alternate link. Another problem this patch fixes allows reducing out physical volumes from a volume group when the device is not available and the device has links, formerly devices with links could not be removed if they were not available. PHKL_7882: A flag in the driver indicates, for each device type, whether or not immediate reporting should be enabled for filemarks. That flag was not being set for DLT drives. To reproduce, write a short C program that writes 20 blocks of 1K bytes, each separated by a filemark. Performance will be substantially better with this patch applied. PHKL_7868: The problem was that the kernel forced a panic whenever any inconsistency was found during an lvreduce. For example, if a logical extent in an lvol referred to a physical extent that was not allocated, it would cause lvreduce(1M) to panic the system. This occured even when the objective was to remove the offending lvol. This is a very rare occurance. PHKL_7668: A future HP-UX release will increase the value of MAXUID, providing for a greater range of valid UIDs and GIDs. It will also introduce problems in mixed-mode NFS environments. Let "LUID" specify a machine running a version of HP-UX with large-UID capability. Let "SUID" specify a machine with current small-UID capability. The following problems may occur: LUID client, SUID server - Client logins with UIDs outside the server's range appear as the anonymous user. However, the anonymous user UID is configurable, and is sometimes configured as the root user (in order to "trust" all client root logins without large-scale modifications to the /etc/exports file). Thus, all logins with large UIDs on the client could be mapped to root on the server. - Files owned by the nobody user on the server will appear to be owned by the wrong user on the client. SUID client, LUID server - Files owned by large-UID logins on the server will appear to be owned by the wrong user on the client. - Executables with the setuid or setgid mode turned on will allow logins on the client to run as the wrong users. PHKL_7637: NCR 53C710 and 53C700 chip bug. Missing SIOC_ABORT and SIOC_RESET_DEV functionality. Integer overflow in request timeout calculation. PHKL_7615: Access to the PDC while comparing data read and written to the floppy reproduces this data loss. May not be easily reproducible on 10.x systems, as the problem was originally found and fixed on 9.x systems. In this case, the data loss was caused by overflow of the floppy DMA buffer when its interrupts are not serviced fast enough. PHKL_7458: K200 HP-UX10.01 is the NFS file server. "/db1" is exported. exportfs /db1 -anon=65534,root=g40 /db2 -anon=65534,root=g40 /home -anon=65534,root=g40 /usr/itl.obj -anon=65534,root=g40 These are HFS file systems. g40 HP-UX9.04 is the client. The customer executed NFS mount command on g40. 1- mount k200:/db1/itloper /users/itloper/itl 2- mount k200:/db1/itloper/itc /users/itloper/itc The system rebooted at step 2 by trap type 18. PHKL_7378: System would panic with any access to a non-supported Exabyte tape drive. PHKL_7334: page reference traps were not correctly set on I/O pages. PHKL_7301: The code for processes Virtual Address Space duplication (used by fork) inserted pregions in the associated region lists before setting the VAS field va_proc. This opened a time window where set_purge_SIDS() could dereference a proc pointer before it was actually set. The system would then trap and panic with a data page fault. The defect would occur when using mprotect(2), and this panic was mostly observed on systems running SAP R/3. PHKL_7244: We only allow a public mapping if we are mapping shared (and thus read-only for now) and if the file's modes meet our tests (no ACL, and mode at least r-xr-xr-x). In one case, /usr (where the shared libraries reside) on their system turns out to be a JFS file system. JFS does not know about ACL and does not manipulate the va_acl bit in 'struct vattr', when VOP_GETATTR() is called. HFS on the other hand will set va_acl to 1 if that file has ACL and 0, if not. Since, smmap() does not initialize the structure (on the stack) and calls VOP_GETATTR() and then looks at the va_acl bit, it can either be a 1 or a 0, randomly. It is not correct for VM subsystem to assume all file systems support ACL and will correct set/reset the bit in the vattr structure as there could be third party file system (eg: JFS) that do not support it. When the libc.1 is first mmapp'ed, the smmap() code finds that va_acl is set (wrongly), it decides not to do public mapping (the region does not get the RHDL_MMAP_PUBLIC set) and so the protection id is set to the second quadrant space id of that process, instead of the public protection id of 0 Since, the informix (oninit) processes have a lot of shared memory segments, each of which has an unique protection id, and constantly accesses the shared memory region and execute library code, the protection id (pid3 & pid4) is getting thrashed in the pid registers. The instruction protection fault code is getting thrashed in the pid registers. The instruction protection fault code (IMEM_PROT) does not make use of the cache (kept per processor) and always uses the trap (long) path to update the protection registers. Hence, you see about 30-40% of the time in trap code. The following fix will ensure that the shared library text segments always get the public protection id. This will cut down the number of protection faults seen in informix. PHKL_7187: lvmerge could merge an lvol back with all PEs marked as current and yet the syncing of stale LTGs had failed. lv_recover_ltg(k), which does the syncing, had no mechanism to return error to lv_table_reimage(k). lv_table_reimage(k) therefore returns success when this may not be the case PHKL_7167: See defect PHKL_7164: LVM user data was aligned to a 1k bound. For sequential i/o directed to disk arrays which stripe the data, i/os with a buf size approaching the stripe depth of the device (64k for the Edison array) would require the device to perform two i/os for each i/o directed to the device. LVM was not always closing and releasing devices held when volume groups were deactivated or when a device was used as a Service Guard Cluster Lock disk. PHKL_7124: PHKL_6763 caused the kernel routine direnter() to return EDEADLK if it couldn't lock all the directories and files it needed to. The change was made to fix a deadlock problem caused by moving directories, and it was thought that direnter() could only hit this state for the DE_RENAME function. The problem can also be hit for large, popular files like /etc/passwd which are being linked to a new name. The fix is to have ufs_link() retry direnter() if EDEADLK is returned, just as ufs_rename() did in the original patch. PHKL_7090: De422730, DSDe427313: Greely M/O's missing from non-wide multilun list. DSDe428060, DSDe428124: Dereference NULL pointer returned by scsi_mode_sense. DSDe427385: Dereference bogus DSP in c720_isrMA. DSDe427660: Dereference bogus pointer in isrDumpState script dump. DSDe427441, DSDe428177: Abort NOT averted by deferred command complete. DSDe427619: LSP_ABORT pushback in isrCA deactivates. DSDe428250: Request timeout integer overflow. Related: Bump sd_format_msecs to 24 hours. DSDe426840: km_io_alloc is too soon in open path. DSDe426722: close synchronization bug DSDe426499: QUANTUM/SCSI_DISK2 pass-thru veto even if open_cnt == 1. DSDe426662: Callout table overflow with scsi_retry entries. DSDe427253: Missing return after isrEscape in isrUntaggedReselect. DSDe425386: TEAC floppy driver does not correctly identify 5.25" 360K format. floppy: Add MODE SELECT in sf_set_geometry to work around firmware bug. DSDe428562: ioscan doesn't show correct s/w, h/w status for pass-thru driver. DSDe427008: Assertion failure due to c700_isr during if_reset_bus/c700_queuedone/scsi_cbfn. NODTSstall: Wasn't checking REQ in c700 for stalled phase mismatch. NODTSresid: Bogus scb->data_resid. PHKL_7050: Customer were using pvmove command to move data from one disk to another. For some reason, the mirrored logical volume to be moved contains unallocated physical extents. system panic: lv_reducelv extmap For vgchange: Couldn't activate volume group problem, it is easily duplicatable following the replacement of a disk mech, or with a simply vgcfgrestore/vgchange combination to the right disks. - connect an HP-FL disk to system, then do the following: Create a volume group with this disk in it (automatically runs vgcfgbackup) pvcreate -f /dev/rdsk/c0t2d0 mkdir /dev/vgdan mknod /dev/vgdan/group c 64 0x090000 vgcreate /dev/vgdan /dev/dsk/c0t2d0 then de-activate the vg: vgchange -a n /dev/vgdan restore the lvm data structures to the disk: vgcfgrestore -n /dev/vgdan /dev/rdsk/c0t2d0 At this point, any further activation of the VG will fail: vgchange -a y /dev/vgdan vgchange: Couldn't activate volume group "/dev/vgpam": Invalid argument The lv_cache_deactivate inflight panics problem were: When user is doing deactivate a volume group, if mwc cache is not clean, the deactivation routine will detect it and panic. When the last user LV (/dev/vgXX/lvol[1-n]) of a volume group is closing and the controlling LV (/dev/vgXX/group) still opened, it should also wait for all outstanding MWC cache writes to be finished. PHKL_6969: if a LVM disk have bad sectors on the bad block directory area. vgchange -a y VG will cause the panic. PHKL_6852: The customer has a T500 & HPUX10.01 and ran into the problem with "/etc/lvmtab is out of date with running kernel" when doing a vgcfgbackup. The current PV value is set to 7, while there are only 6 disks in the /etc/lvmtab. PHKL_6801: None. PHKL_6748: Directory renaming code locks the new parent directory and reads the new parent directory buffer, thereby locking it. It then drops the new parent directory lock and later tries to reacquire it. If a lookup process has gotten the new parent directory lock in the meantime and is sleeping waiting for the new parent directory buffer to be free, deadlock! PHKL_6653: No defect with the kernel. Although this patch does allow a patch to fix a defect with fuser -k to work. PHKL_6643: If a drive was found that had a manufacturer of Exabyte but was not one of the supported drives the product name got set to NULL. Dereferencing this NULL pointer later on caused a system panic. PHKL_6484: If truncating a file with a hole in the middle of it causes the new end of file to fall in the middle of a hole, a new disk block must be allocated to hold the end of file. If the file system is full and a block can't be allocated, itrunc was panicing. There is a remote possibility that removing an Access Control List could cause file system data loss or corruption. This defect was found during a code inspection, and has never (to our knowledge) been seen by any customer. SR: 1653096131 1653144071 1653148098 1653149054 1653153247 1653162669 1653166785 1653177899 1653182501 1653202754 1653215020 1653217463 1653218065 1653220897 1653221820 1653222950 1653227983 1653235176 4701311381 4701311415 4701312934 4701314179 4701314302 4701315317 4701317131 4701318352 4701319335 4701319541 4701320580 4701320606 4701321554 4701321695 4701321711 4701329417 4701330647 4701334698 4701334839 4701336412 4701337394 4701339945 4701342089 4701347922 4701349175 4701352278 4701355321 4701358523 4701365049 4701374975 5000697466 5000698738 5000714352 5003281469 5003300400 5003309385 5003314252 5003314633 5003318667 5003321364 5003323493 5003325506 5003329078 5003330746 5003330910 5003334961 5003341925 5003345496 5003346486 5003359414 5003359489 5003365692 5003366930 5003398800 Patch Files: /usr/conf/h/mtio.h /usr/conf/h/pstat.h /usr/conf/lib/libhp-ux.a(asm_excp.o) /usr/conf/lib/libhp-ux.a(asm_rv.o) /usr/conf/lib/libhp-ux.a(asm_tlb.o) /usr/conf/lib/libhp-ux.a(asm_tlb2_0.o) /usr/conf/lib/libhp-ux.a(asm_vm.o) /usr/conf/lib/libhp-ux.a(clock.o) /usr/conf/lib/libhp-ux.a(cpd.o) /usr/conf/lib/libhp-ux.a(dmem.o) /usr/conf/lib/libhp-ux.a(dump.o) /usr/conf/lib/libhp-ux.a(fmpyfadd.o) /usr/conf/lib/libhp-ux.a(fpudispatch.o) /usr/conf/lib/libhp-ux.a(hdl_fault.o) /usr/conf/lib/libhp-ux.a(hdl_mprotect.o) /usr/conf/lib/libhp-ux.a(hdl_policy.o) /usr/conf/lib/libhp-ux.a(hdl_trans.o) /usr/conf/lib/libhp-ux.a(init_main.o) /usr/conf/lib/libhp-ux.a(kern_exec.o) /usr/conf/lib/libhp-ux.a(kern_exit.o) /usr/conf/lib/libhp-ux.a(kern_fork.o) /usr/conf/lib/libhp-ux.a(kern_mman.o) /usr/conf/lib/libhp-ux.a(lpmc.o) /usr/conf/lib/libhp-ux.a(lv_config.o) /usr/conf/lib/libhp-ux.a(lv_lvm.o) /usr/conf/lib/libhp-ux.a(machdep.o) /usr/conf/lib/libhp-ux.a(pc_fdc.o) /usr/conf/lib/libhp-ux.a(pc_floppy.o) /usr/conf/lib/libhp-ux.a(pm_config.o) /usr/conf/lib/libhp-ux.a(pm_procdup.o) /usr/conf/lib/libhp-ux.a(proc_iface.o) /usr/conf/lib/libhp-ux.a(pstat.o) /usr/conf/lib/libhp-ux.a(scsi_c700.o) /usr/conf/lib/libhp-ux.a(scsi_c720.o) /usr/conf/lib/libhp-ux.a(scsi_ctl.o) /usr/conf/lib/libhp-ux.a(scsi_disk.o) /usr/conf/lib/libhp-ux.a(scsi_floppy.o) /usr/conf/lib/libhp-ux.a(scsi_tape.o) /usr/conf/lib/libhp-ux.a(snakes_rs232.o) /usr/conf/lib/libhp-ux.a(spinlock.o) /usr/conf/lib/libhp-ux.a(subr_prf.o) /usr/conf/lib/libhp-ux.a(sysV_shm.o) /usr/conf/lib/libhp-ux.a(sys_ki.o) /usr/conf/lib/libhp-ux.a(trap.o) /usr/conf/lib/libhp-ux.a(ufs_dsort.o) /usr/conf/lib/libhp-ux.a(vm_devswap.o) /usr/conf/lib/libhp-ux.a(vm_machdep.o) /usr/conf/lib/libhp-ux.a(vm_mmap.o) /usr/conf/lib/libhp-ux.a(vm_pdir1_1.o) /usr/conf/lib/libhp-ux.a(vm_pdir2_0.o) /usr/conf/lib/libhp-ux.a(vm_pregion.o) /usr/conf/lib/libhp-ux.a(vm_region.o) /usr/conf/lib/libhp-ux.a(vm_remap.o) /usr/conf/lib/libhp-ux.a(vm_vas.o) /usr/conf/lib/libhp-ux.a(vm_vhand.o) /usr/conf/lib/libhp-ux.a(wsio_scsi.o) /usr/conf/lib/liblvm.a(lv_block.o) /usr/conf/lib/liblvm.a(lv_cluster_lock.o) /usr/conf/lib/liblvm.a(lv_defect.o) /usr/conf/lib/liblvm.a(lv_hp.o) /usr/conf/lib/liblvm.a(lv_ioctls.o) /usr/conf/lib/liblvm.a(lv_kdb.o) /usr/conf/lib/liblvm.a(lv_lvsubr.o) /usr/conf/lib/liblvm.a(lv_malloc.o) /usr/conf/lib/liblvm.a(lv_mircons.o) /usr/conf/lib/liblvm.a(lv_pbuf.o) /usr/conf/lib/liblvm.a(lv_phys.o) /usr/conf/lib/liblvm.a(lv_schedule.o) /usr/conf/lib/liblvm.a(lv_strategy.o) /usr/conf/lib/liblvm.a(lv_subr.o) /usr/conf/lib/liblvm.a(lv_syscalls.o) /usr/conf/lib/liblvm.a(lv_vgda.o) /usr/conf/lib/liblvm.a(lv_vgsa.o) /usr/conf/lib/liblvm.a(sh_vgsa.o) /usr/conf/lib/liblvm.a(slvm_comm.o) /usr/conf/lib/liblvm.a(slvm_schedule.o) /usr/conf/lib/libufs.a(ufs_dir.o) /usr/conf/lib/libufs.a(ufs_inode.o) /usr/conf/lib/libufs.a(ufs_vnops.o) /usr/conf/lib/libvxfs_adv.a(vx_reorg.o) /usr/conf/master.d/core-hpux /usr/conf/space.h.d/core-hpux.h /usr/include/sys/mtio.h /usr/include/sys/pstat.h what(1) Output: /usr/conf/h/mtio.h: mtio.h $Date: 97/01/20 10:07:51 $ $Revision: 1.23.89 .13 $ PATCH_10.10 (PHKL_8753) /usr/conf/h/pstat.h: pstat.h $Date: 96/01/18 13:52:54 $ $Revision: 1.9.89 .13 $ PATCH_10.10 (PHKL_6653) /usr/conf/lib/libhp-ux.a(asm_excp.o): asm_excp.s $Date: 96/02/29 17:42:54 $ $Revision: 1.2 1.89.7 $ PATCH_10.10 (PHKL_6801) /usr/conf/lib/libhp-ux.a(asm_rv.o): asm_rv.s $Date: 97/07/17 18:01:38 $ $Revision: 1.53. 89.26 $ PATCH_10.10 (PHKL_11850) /usr/conf/lib/libhp-ux.a(asm_tlb.o): asm_tlb.s $Date: 96/04/19 10:15:17 $ $Revision: 1.5.89.7 $ PATCH_10.10 (PHKL_7334) /usr/conf/lib/libhp-ux.a(asm_tlb2_0.o): asm_tlb2_0.s $Date: 96/04/19 10:15:22 $ $Revision: 1.2.90.6 $ PATCH_10.10 (PHKL_7334) /usr/conf/lib/libhp-ux.a(asm_vm.o): asm_vm.s $Date: 97/09/02 16:55:18 $ $Revision: 1 .55.89.13 $ PATCH_10.10 (PHKL_12363) /usr/conf/lib/libhp-ux.a(clock.o): clock.c $Date: 97/07/17 18:02:49 $ $Revision: 1.37.8 9.7 $ PATCH_10.10 (PHKL_11850) /usr/conf/lib/libhp-ux.a(cpd.o): cpd.c $Date: 97/06/19 17:48:48 $ $Revision: 1.3.89.9 $ PATCH_10.10 (PHKL_11432) /usr/conf/lib/libhp-ux.a(dmem.o): dmem.c $Date: 96/02/29 17:49:24 $ $Revision: 1.50.8 9.14 $ PATCH_10.10 (PHKL_6801) /usr/conf/lib/libhp-ux.a(dump.o): dump.c $Date: 97/06/19 17:49:41 $ $Revision: 1.7.89. 8 $ PATCH_10.10 (PHKL_11432) /usr/conf/lib/libhp-ux.a(fmpyfadd.o): fmpyfadd.c $Date: 96/02/29 17:58:11 $ $Revision: 1. 2.89.5 $ PATCH_10.10 (PHKL_6801) /usr/conf/lib/libhp-ux.a(fpudispatch.o): fpudispatch.c $Date: 96/02/29 17:49:31 $ $Revision: 1.4.89.8 $ PATCH_10.10 (PHKL_6801) /usr/conf/lib/libhp-ux.a(hdl_fault.o): hdl_fault.c $Date: 97/04/25 14:21:38 $ $Revision: 1.10.89.15 $ PATCH_10.10 (PHKL_10873) /usr/conf/lib/libhp-ux.a(hdl_mprotect.o): hdl_mprotect.c $Date: 98/03/11 15:06:48 $ $Revision : 1.3.89.12 $ PATCH_10.10 (PHKL_14508) /usr/conf/lib/libhp-ux.a(hdl_policy.o): hdl_policy.c $Date: 98/02/18 13:19:05 $ $Revision: 1 .11.89.19 $ PATCH_10.10 (PHKL_14222) /usr/conf/lib/libhp-ux.a(hdl_trans.o): hdl_trans.c $Date: 96/02/29 17:49:20 $ $Revision: 1 .10.89.13 $ PATCH_10.10 (PHKL_6801) /usr/conf/lib/libhp-ux.a(init_main.o): init_main.c $Date: 97/07/17 17:53:18 $ $Revision: 1. 116.89.30 $ PATCH_10.10 (PHKL_11850) /usr/conf/lib/libhp-ux.a(kern_exec.o): kern_exec.c $Date: 97/06/24 16:52:46 $ $Revision: 1.89.89.39 $ PATCH_10.10 (PHKL_11523) /usr/conf/lib/libhp-ux.a(kern_exit.o): kern_exit.c $Date: 97/07/17 17:54:36 $ $Revision: 1. 73.89.39 $ PATCH_10.10 (PHKL_11850) /usr/conf/lib/libhp-ux.a(kern_fork.o): kern_fork.c $Date: 97/07/17 17:04:35 $ $Revision: 1. 67.89.46 $ PATCH_10.10 (PHKL_11850) /usr/conf/lib/libhp-ux.a(kern_mman.o): kern_mman.c $Date: 97/04/25 14:15:18 $ $Revision: 1.33.89.13 $ PATCH_10.10 (PHKL_10873) /usr/conf/lib/libhp-ux.a(lpmc.o): lpmc.c $Date: 96/02/29 17:49:26 $ $Revision: 1.4.89 .7 $ PATCH_10.10 (PHKL_6801) /usr/conf/lib/libhp-ux.a(lv_config.o): lv_config.c $Date: 97/06/19 16:23:19 $ $Revision: 1. 8.89.11 $ PATCH_10.10 (PHKL_11432) /usr/conf/lib/libhp-ux.a(lv_lvm.o): lv_lvm.c $Date: 97/06/19 17:48:28 $ $Revision: 1.2.8 9.3 $ PATCH_10.10 (PHKL_11432) /usr/conf/lib/libhp-ux.a(machdep.o): machdep.c $Date: 96/08/07 10:29:00 $ $Revision: 1. 120.89.16 $ PATCH_10.10 (PHKL_8201) /usr/conf/lib/libhp-ux.a(pc_fdc.o): pc_fdc.c $Date: 97/07/29 15:07:29 $ $Revision: 1.3.8 9.8 $ PATCH_10.10 (PHKL_11988) /usr/conf/lib/libhp-ux.a(pc_floppy.o): pc_floppy.c $Date: 97/07/29 15:17:00 $ $Revision: 1. 3.89.7 $ PATCH_10.10 (PHKL_11988) /usr/conf/lib/libhp-ux.a(pm_config.o): pm_config.c $Date: 97/06/24 16:50:45 $ $Revision: 1. 3.89.13 $ PATCH_10.10 (PHKL_11523) /usr/conf/lib/libhp-ux.a(pm_procdup.o): pm_procdup.c $Date: 97/07/17 17:58:16 $ $Revision: 1 .8.89.21 $ PATCH_10.10 (PHKL_11850) /usr/conf/lib/libhp-ux.a(proc_iface.o): proc_iface.c $Date: 96/04/19 10:19:12 $ $Revision: 1.2.89.15 $ PATCH_10.10 (PHKL_7334) /usr/conf/lib/libhp-ux.a(pstat.o): pstat.c $Date: 97/09/06 19:47:52 $ $Revision: 1.14.8 9.38 $ PATCH_10.10 (PHKL_12429) /usr/conf/lib/libhp-ux.a(scsi_c700.o): scsi_c700.c $Date: 96/07/26 13:08:57 $ $Revision: 1.3.89.9 $ PATCH_10.10 (PHKL_7637) /usr/conf/lib/libhp-ux.a(scsi_c720.o): scsi_c720.c $Date: 97/07/03 09:57:00 $ $Revision: 1.2.89.20 $ PATCH_10.10 (PHKL_11543) /usr/conf/lib/libhp-ux.a(scsi_ctl.o): scsi_ctl.c $Date: 97/11/19 10:08:18 $ $Revision: 1.3 .89.20 $ PATCH_10.10 (PHKL_13280) /usr/conf/lib/libhp-ux.a(scsi_disk.o): scsi_disk.c $Date: 96/11/25 13:22:12 $ $Revision: 1.3.89.14 $ PATCH_10.10 (PHKL_8906) /usr/conf/lib/libhp-ux.a(scsi_floppy.o): scsi_floppy.c $Date: 96/04/04 11:46:49 $ $Revision: 1.3.89.6 $ PATCH_10.10 (PHKL_7090) /usr/conf/lib/libhp-ux.a(scsi_tape.o): scsi_tape.c $Date: 97/06/30 10:25:49 $ $Revision: 1. 3.89.21 $ PATCH_10.10 (PHKL_11543) /usr/conf/lib/libhp-ux.a(snakes_rs232.o): snakes_rs232.c $Date: 96/04/19 10:16:51 $ $Revision: 1.5.89.3 $ PATCH_10.10 (PHKL_7334) /usr/conf/lib/libhp-ux.a(spinlock.o): spinlock.c $Date: 98/03/11 15:05:39 $ $Revision: 1 .12.89.12 $ PATCH_10.10 (PHKL_14508) /usr/conf/lib/libhp-ux.a(subr_prf.o): subr_prf.c $Date: 97/07/17 17:56:07 $ $Revision: 1.6 3.89.13 $ PATCH_10.10 (PHKL_11850) /usr/conf/lib/libhp-ux.a(sysV_shm.o): sysV_shm.c $Date: 96/11/13 16:13:08 $ $Revision: 1.53.89.9 $ PATCH_10.10 (PHKL_9073) /usr/conf/lib/libhp-ux.a(sys_ki.o): sys_ki.c $Date: 96/11/08 12:42:51 $ $Revision: 1.1 5.89.26 $ PATCH_10.10 (PHKL_8920) /usr/conf/lib/libhp-ux.a(trap.o): trap.c $Date: 96/04/19 10:12:44 $ $Revision: 1.165.89.33 $ PATCH_10.10 (PHKL_7334) /usr/conf/lib/libhp-ux.a(ufs_dsort.o): ufs_dsort.c $Date: 97/10/03 14:59:31 $ $Revision: 1.16.89.7 $ PATCH_10.10 (PHKL_12606) /usr/conf/lib/libhp-ux.a(vm_devswap.o): vm_devswap.c $Date: 96/02/29 17:53:41 $ $Revision: 1.15.89.21 $ PATCH_10.10 (PHKL_6801) /usr/conf/lib/libhp-ux.a(vm_machdep.o): vm_machdep.c $Date: 97/09/02 16:54:23 $ $Revision: 1 .152.89.43 $ PATCH_10.10 (PHKL_12363) /usr/conf/lib/libhp-ux.a(vm_mmap.o): vm_mmap.c $Date: 98/02/18 13:10:08 $ $Revision: 1.13.89.23 $ PATCH_10.10 (PHKL_14222) /usr/conf/lib/libhp-ux.a(vm_pdir1_1.o): vm_pdir1_1.c $Date: 96/04/19 10:15:13 $ $Revision: 1.2.90.12 $ PATCH_10.10 (PHKL_7334) /usr/conf/lib/libhp-ux.a(vm_pdir2_0.o): vm_pdir2_0.c $Date: 96/02/29 17:49:36 $ $Revision: 1.2.90.10 $ PATCH_10.10 (PHKL_6801) /usr/conf/lib/libhp-ux.a(vm_pregion.o): vm_pregion.c $Date: 96/11/13 16:12:57 $ $Revision: 1.12.89.15 $ PATCH_10.10 (PHKL_9073) /usr/conf/lib/libhp-ux.a(vm_region.o): vm_region.c $Date: 96/11/13 16:13:10 $ $Revision: 1.17.89.7 $ PATCH_10.10 (PHKL_9073) /usr/conf/lib/libhp-ux.a(vm_remap.o): vm_remap.c $Date: 96/02/29 17:53:43 $ $Revision: 1. 6.89.10 $ PATCH_10.10 (PHKL_6801) /usr/conf/lib/libhp-ux.a(vm_vas.o): vm_vas.c $Date: 97/07/17 17:57:14 $ $Revision: 1.14. 89.31 $ PATCH_10.10 (PHKL_11850) /usr/conf/lib/libhp-ux.a(vm_vhand.o): vm_vhand.c $Date: 97/11/07 16:04:43 $ $Revision: 1.16.89.18 $ PATCH_10.10 (PHKL_13153) /usr/conf/lib/libhp-ux.a(wsio_scsi.o): wsio_scsi.c $Date: 96/11/25 13:29:41 $ $Revision: 1.3.89.4 $ PATCH_10.10 (PHKL_8906) /usr/conf/lib/liblvm.a(lv_block.o): lv_block.c $Date: 97/06/19 16:23:18 $ $Revision: 1 .8.89.6 $ PATCH_10.10 (PHKL_11432) /usr/conf/lib/liblvm.a(lv_cluster_lock.o): lv_cluster_lock.c $Date: 97/06/19 16:22:52 $ $Revi sion: 1.3.89.13 $ PATCH_10.10 (PHKL_11432) /usr/conf/lib/liblvm.a(lv_defect.o): lv_defect.c $Date: 97/06/19 16:23:17 $ $Revision: 1. 8.89.14 $ PATCH_10.10 (PHKL_11432) /usr/conf/lib/liblvm.a(lv_hp.o): lv_hp.c $Date: 97/06/18 16:16:19 $ $Revision: 1.8.89 .37 $ PATCH_10.10 (PHKL_11432) /usr/conf/lib/liblvm.a(lv_ioctls.o): lv_ioctls.c $Date: 97/06/18 16:17:26 $ $Revision: 1.8.89.22 $ PATCH_10.10 (PHKL_11432) /usr/conf/lib/liblvm.a(lv_kdb.o): lv_kdb.c $Date: 97/06/19 16:22:56 $ $Revision: 1.6 .89.6 $ PATCH_10.10 (PHKL_11432) /usr/conf/lib/liblvm.a(lv_lvsubr.o): lv_lvsubr.c $Date: 98/02/25 11:12:15 $ $Revision: 1.8.89.30 $ PATCH_10.10 (PHKL_14296) /usr/conf/lib/liblvm.a(lv_malloc.o): lv_malloc.c $Date: 97/06/19 16:22:54 $ $Revision: 1.8.89.6 $ PATCH_10.10 (PHKL_11432) /usr/conf/lib/liblvm.a(lv_mircons.o): lv_mircons.c $Date: 97/06/19 16:23:11 $ $Revision: 1 .8.89.18 $ PATCH_10.10 (PHKL_11432) /usr/conf/lib/liblvm.a(lv_pbuf.o): lv_pbuf.c $Date: 97/06/19 16:23:09 $ $Revision: 1. 8.89.8 $ PATCH_10.10 (PHKL_11432) /usr/conf/lib/liblvm.a(lv_phys.o): lv_phys.c $Date: 97/07/25 13:06:16 $ $Revision: 1.8. 89.13 $ PATCH_10.10 (PHKL_11815) /usr/conf/lib/liblvm.a(lv_schedule.o): lv_schedule.c $Date: 97/06/19 16:23:05 $ $Revision: 1.8.89.15 $ PATCH_10.10 (PHKL_11432) /usr/conf/lib/liblvm.a(lv_strategy.o): lv_strategy.c $Date: 97/06/19 16:23:04 $ $Revision: 1.8.89.13 $ PATCH_10.10 (PHKL_11432) /usr/conf/lib/liblvm.a(lv_subr.o): lv_subr.c $Date: 97/06/19 16:23:02 $ $Revision: 1.8. 89.17 $ PATCH_10.10 (PHKL_11432) /usr/conf/lib/liblvm.a(lv_syscalls.o): lv_syscalls.c $Date: 97/06/18 16:17:32 $ $Revision: 1.8.89.13 $ PATCH_10.10 (PHKL_11432) /usr/conf/lib/liblvm.a(lv_vgda.o): lv_vgda.c $Date: 97/06/19 16:23:00 $ $Revision: 1. 8.89.12 $ PATCH_10.10 (PHKL_11432) /usr/conf/lib/liblvm.a(lv_vgsa.o): lv_vgsa.c $Date: 97/06/19 16:22:57 $ $Revision: 1.8. 89.20 $ PATCH_10.10 (PHKL_11432) /usr/conf/lib/liblvm.a(sh_vgsa.o): sh_vgsa.c $Date: 97/06/18 16:17:34 $ $Revision: 1.2. 89.13 $ PATCH_10.10 (PHKL_11432) /usr/conf/lib/liblvm.a(slvm_comm.o): slvm_comm.c $Date: 97/06/19 16:22:48 $ $Revision: 1. 2.89.7 $ PATCH_10.10 (PHKL_11432) /usr/conf/lib/liblvm.a(slvm_schedule.o): slvm_schedule.c $Date: 97/06/19 16:22:29 $ $Revision : 1.2.89.17 $ PATCH_10.10 (PHKL_11432) /usr/conf/lib/libufs.a(ufs_dir.o): ufs_dir.c $Date: 97/08/06 15:29:48 $ $Revision: 1.17.89.17 $ PATCH_10.10 (PHKL_12061) /usr/conf/lib/libufs.a(ufs_inode.o): ufs_inode.c $Date: 98/01/07 15:16:02 $ $Revision: 1.42.89.16 $ PATCH_10.10 (PHKL_13728) /usr/conf/lib/libufs.a(ufs_vnops.o): ufs_vnops.c $Date: 96/08/14 17:02:08 $ $Revision: 1.24.89.25 $ PATCH_10.10 (PHKL_8292) /usr/conf/lib/libvxfs_adv.a(vx_reorg.o): vx_reorg.c $Date: 97/10/03 14:58:34 $ $Revision: 1 .3.89.6 $ PATCH_10.10 (PHKL_12606) /usr/conf/master.d/core-hpux: core-hpux $Date: 97/06/24 16:56:43 $ $Revision: 1. 2.89.12 $ PATCH_10.10 (PHKL_11523) /usr/conf/space.h.d/core-hpux.h: core-hpux.h $Date: 97/06/24 16:58:57 $ $Revision: 1.2.89.21 $ PATCH_10.10 (PHKL_11523) /usr/include/sys/mtio.h: mtio.h $Date: 97/01/20 10:07:51 $ $Revision: 1.23.89 .13 $ PATCH_10.10 (PHKL_8753) /usr/include/sys/pstat.h: pstat.h $Date: 96/01/18 13:52:54 $ $Revision: 1.9.89 .13 $ PATCH_10.10 (PHKL_6653) cksum(1) Output: 1968850153 25660 /usr/conf/h/mtio.h 351025292 35051 /usr/conf/h/pstat.h 3931996340 3108 /usr/conf/lib/libhp-ux.a(asm_excp.o) 2009585479 15492 /usr/conf/lib/libhp-ux.a(asm_rv.o) 1169006284 41224 /usr/conf/lib/libhp-ux.a(asm_tlb.o) 2534453469 14452 /usr/conf/lib/libhp-ux.a(asm_tlb2_0.o) 623325753 19612 /usr/conf/lib/libhp-ux.a(asm_vm.o) 2356856306 20076 /usr/conf/lib/libhp-ux.a(clock.o) 1501320178 11172 /usr/conf/lib/libhp-ux.a(cpd.o) 2366865159 8908 /usr/conf/lib/libhp-ux.a(dmem.o) 823013355 12692 /usr/conf/lib/libhp-ux.a(dump.o) 986054333 17224 /usr/conf/lib/libhp-ux.a(fmpyfadd.o) 3159161935 10932 /usr/conf/lib/libhp-ux.a(fpudispatch.o) 3165764122 12940 /usr/conf/lib/libhp-ux.a(hdl_fault.o) 2893473673 15916 /usr/conf/lib/libhp-ux.a(hdl_mprotect.o) 1532574344 11632 /usr/conf/lib/libhp-ux.a(hdl_policy.o) 3260695634 8880 /usr/conf/lib/libhp-ux.a(hdl_trans.o) 4114243508 18404 /usr/conf/lib/libhp-ux.a(init_main.o) 3447400473 15732 /usr/conf/lib/libhp-ux.a(kern_exec.o) 3515088498 15628 /usr/conf/lib/libhp-ux.a(kern_exit.o) 2695060553 14236 /usr/conf/lib/libhp-ux.a(kern_fork.o) 2668531744 3816 /usr/conf/lib/libhp-ux.a(kern_mman.o) 3103322954 6824 /usr/conf/lib/libhp-ux.a(lpmc.o) 557290747 26576 /usr/conf/lib/libhp-ux.a(lv_config.o) 157892121 102088 /usr/conf/lib/libhp-ux.a(lv_lvm.o) 2666974195 30032 /usr/conf/lib/libhp-ux.a(machdep.o) 3868930204 27196 /usr/conf/lib/libhp-ux.a(pc_fdc.o) 4241247167 22464 /usr/conf/lib/libhp-ux.a(pc_floppy.o) 579935598 5980 /usr/conf/lib/libhp-ux.a(pm_config.o) 4125167237 6408 /usr/conf/lib/libhp-ux.a(pm_procdup.o) 1374434585 12912 /usr/conf/lib/libhp-ux.a(proc_iface.o) 3418112664 23188 /usr/conf/lib/libhp-ux.a(pstat.o) 43376672 106560 /usr/conf/lib/libhp-ux.a(scsi_c700.o) 3643034372 78156 /usr/conf/lib/libhp-ux.a(scsi_c720.o) 2514426210 69756 /usr/conf/lib/libhp-ux.a(scsi_ctl.o) 3393391491 16992 /usr/conf/lib/libhp-ux.a(scsi_disk.o) 1060465429 22308 /usr/conf/lib/libhp-ux.a(scsi_floppy.o) 2727899563 68216 /usr/conf/lib/libhp-ux.a(scsi_tape.o) 3705526801 5964 /usr/conf/lib/libhp-ux.a(snakes_rs232.o) 3274364135 15132 /usr/conf/lib/libhp-ux.a(spinlock.o) 2307164276 16472 /usr/conf/lib/libhp-ux.a(subr_prf.o) 3611221468 8428 /usr/conf/lib/libhp-ux.a(sysV_shm.o) 2093087402 59652 /usr/conf/lib/libhp-ux.a(sys_ki.o) 403410752 21680 /usr/conf/lib/libhp-ux.a(trap.o) 169788701 8300 /usr/conf/lib/libhp-ux.a(ufs_dsort.o) 2090489607 15296 /usr/conf/lib/libhp-ux.a(vm_devswap.o) 4031508929 89976 /usr/conf/lib/libhp-ux.a(vm_machdep.o) 51554130 20588 /usr/conf/lib/libhp-ux.a(vm_mmap.o) 874224294 39144 /usr/conf/lib/libhp-ux.a(vm_pdir1_1.o) 2738926588 29600 /usr/conf/lib/libhp-ux.a(vm_pdir2_0.o) 1975125224 11700 /usr/conf/lib/libhp-ux.a(vm_pregion.o) 3495003745 11328 /usr/conf/lib/libhp-ux.a(vm_region.o) 4138546304 8704 /usr/conf/lib/libhp-ux.a(vm_remap.o) 3426720097 12964 /usr/conf/lib/libhp-ux.a(vm_vas.o) 4146996706 16036 /usr/conf/lib/libhp-ux.a(vm_vhand.o) 4081411541 154884 /usr/conf/lib/libhp-ux.a(wsio_scsi.o) 2081605216 2360 /usr/conf/lib/liblvm.a(lv_block.o) 3655535219 10124 /usr/conf/lib/liblvm.a(lv_cluster_lock.o) 3243873833 12032 /usr/conf/lib/liblvm.a(lv_defect.o) 88337327 41764 /usr/conf/lib/liblvm.a(lv_hp.o) 3329440977 26764 /usr/conf/lib/liblvm.a(lv_ioctls.o) 1066660338 732 /usr/conf/lib/liblvm.a(lv_kdb.o) 4260432339 34472 /usr/conf/lib/liblvm.a(lv_lvsubr.o) 4053459022 2416 /usr/conf/lib/liblvm.a(lv_malloc.o) 1611741354 18132 /usr/conf/lib/liblvm.a(lv_mircons.o) 4247065797 5876 /usr/conf/lib/liblvm.a(lv_pbuf.o) 507102696 6796 /usr/conf/lib/liblvm.a(lv_phys.o) 1010723492 19996 /usr/conf/lib/liblvm.a(lv_schedule.o) 2539597430 7436 /usr/conf/lib/liblvm.a(lv_strategy.o) 1892668715 8584 /usr/conf/lib/liblvm.a(lv_subr.o) 2989147741 18152 /usr/conf/lib/liblvm.a(lv_syscalls.o) 78888363 8700 /usr/conf/lib/liblvm.a(lv_vgda.o) 1823992439 12764 /usr/conf/lib/liblvm.a(lv_vgsa.o) 1683985499 28684 /usr/conf/lib/liblvm.a(sh_vgsa.o) 3955021617 23012 /usr/conf/lib/liblvm.a(slvm_comm.o) 1923340697 6980 /usr/conf/lib/liblvm.a(slvm_schedule.o) 123507040 19684 /usr/conf/lib/libufs.a(ufs_dir.o) 905493489 26360 /usr/conf/lib/libufs.a(ufs_inode.o) 640680162 30648 /usr/conf/lib/libufs.a(ufs_vnops.o) 2651167216 16996 /usr/conf/lib/libvxfs_adv.a(vx_reorg.o) 3941969772 16352 /usr/conf/master.d/core-hpux 2591358869 18864 /usr/conf/space.h.d/core-hpux.h 1968850153 25660 /usr/include/sys/mtio.h 351025292 35051 /usr/include/sys/pstat.h Patch Conflicts: None Patch Dependencies: s700: 10.10: PHCO_8459 Hardware Dependencies: None Other Dependencies: PC Floppy drive and associated drivers must be installed. Supersedes: PHKL_6484 PHKL_6643 PHKL_6653 PHKL_6748 PHKL_6801 PHKL_6852 PHKL_6969 PHKL_7050 PHKL_7090 PHKL_7124 PHKL_7164 PHKL_7167 PHKL_7187 PHKL_7244 PHKL_7301 PHKL_7334 PHKL_7378 PHKL_7458 PHKL_7615 PHKL_7637 PHKL_7668 PHKL_7868 PHKL_7882 PHKL_8082 PHKL_8201 PHKL_8292 PHKL_8359 PHKL_8393 PHKL_8461 PHKL_8504 PHKL_8714 PHKL_8753 PHKL_8790 PHKL_8906 PHKL_8920 PHKL_8928 PHKL_9009 PHKL_9073 PHKL_9420 PHKL_10103 PHKL_10201 PHKL_10232 PHKL_10270 PHKL_10419 PHKL_10827 PHKL_10873 PHKL_11121 PHKL_11432 PHKL_11523 PHKL_11543 PHKL_11815 PHKL_11850 PHKL_11988 PHKL_12061 PHKL_12363 PHKL_12429 PHKL_12606 PHKL_13153 PHKL_13280 PHKL_13728 PHKL_14222 PHKL_14296 Equivalent Patches: PHKL_14509: s800: 10.10 Patch Package Size: 2060 KBytes Installation Instructions: Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch. ------------------------------------------------------------ 1. Back up your system before installing a patch. 2. Login as root. 3. Copy the patch to the /tmp directory. 4. Move to the /tmp directory and unshar the patch: cd /tmp sh PHKL_14508 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHKL_14508.depot 5b. For a homogeneous NFS Diskless cluster run swcluster on the server to install the patch on the server and the clients: swcluster -i -b This will invoke swcluster in the interactive mode and force all clients to be shut down. WARNING: All cluster clients must be shut down prior to the patch installation. Installing the patch while the clients are booted is unsupported and can lead to serious problems. The swcluster command will invoke an swinstall session in which you must specify: alternate root path - default is /export/shared_root/OS_700 source depot path - /tmp/PHKL_14508.depot To complete the installation, select the patch by choosing "Actions -> Match What Target Has" and then "Actions -> Install" from the Menubar. 5c. For a heterogeneous NFS Diskless cluster: - run swinstall on the server as in step 5a to install the patch on the cluster server. - run swcluster on the server as in step 5b to install the patch on the cluster clients. By default swinstall will archive the original software in /var/adm/sw/patch/PHKL_14508. If you do not wish to retain a copy of the original software, you can create an empty file named /var/adm/sw/patch/PATCH_NOSAVE. Warning: If this file exists when a patch is installed, the patch cannot be deinstalled. Please be careful when using this feature. It is recommended that you move the PHKL_14508.text file to /var/adm/sw/patch for future reference. To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHKL_14508.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: If you are planning to install the advanced VxFS product (AdvJournalFS.VXFS-ADV-KRN), it is imperative that this patch, and all listed superseded patches after PHKL_12429, be removed from the system via swremove(1M) before the actual product installation. After the installation of the Advanced VxFS product has completed, this patch can be re-installed. (It is not necessary to re-install superseded patches.) All patches listed in the Supersedes field after PHKL_12429 are subject to this behavior and need to be removed before installing the Advanced VxFS product. After running swremove(1M), use the swlist(1M) command to insure that none of the previous patches were restored during the removal process. If one was, remove it using swremove(1M). --- This is a JFS patch that should not be installed on systems using the OmniStorage product. If you are using the OmniStorage product then using the methods taken to receive this patch please obtain the equivalent OmniStorage/JFS patch. If you cannot locate the patch, please contact your local HP support entity. --- When this patch is installed the default environment size is 20478 bytes. To enable the system to use the larger environment size of 2048000 bytes, the following steps must be followed. 1. A new tunable called `large_ncargs_enabled' must be defined in the sytem file in the following manner large_ncargs_enabled 1 2. A new kernel must be built (using this system file) and the sysytem rebooted. To return to the default environment size, the new tunable needs to be either removed from the system file, or its value set to zero. A new kernel should then be built (using the modified system file) and the machine rebooted. --- Due to the number of objects in this patch, the customization phase of the update may take more than 10 minutes. During that time the system will not appear to make forward progress, but it will actually be installing the objects. @EOF chmod 644 PHKL_14508.text exit 0