Patch Name: PHKL_12426 Patch Description: s700 9.03 9.05 9.07 chown() limit, SCSI, NFS, VM, DUX patch Creation Date: 97/09/05 Post Date: 97/09/10 Hardware Platforms - OS Releases: s700: 9.03 9.05 9.07 Products: N/A Filesets: C-INC KERN-BLD NFS-INC NFS-RUN Automatic Reboot?: Yes Status: General Release Critical: No (superseded patches were critical) PHKL_11725: ABORT PHKL_10222: HANG PHKL_9149: PANIC PHKL_6869: PANIC CORRUPTION PHKL_5832: HANG PHKL_5763: HANG PHKL_5747: HANG PHKL_5536: PANIC PHKL_5358: HANG PHKL_5348: CORRUPTION PHKL_5165: PANIC PHKL_4943: PANIC PHKL_4937: PANIC PHKL_4777: HANG PHKL_4500: PANIC PHKL_4268: MEMORY_LEAK PHKL_4247: PANIC PHKL_4161: PANIC PHKL_4048: PANIC PHKL_3992: PANIC PHKL_3798: PANIC PHKL_3791: PANIC PHKL_3617: PANIC PHKL_3601: PANIC HANG PHKL_3600: PANIC PHKL_3505: CORRUPTION PHKL_3472: CORRUPTION PHKL_3434: PANIC PHKL_3361: PANIC PHKL_3290: PANIC Path Name: /hp-ux_patches/s700/9.X/PHKL_12426 Symptoms: PHKL_12426: When a user specifies the owner and group value of a file to be 60,000 (Decimal), the chown command fails. But when he specifies a value of 100,000, the chown command takes the last 16 bits and modifies the ownership of the file. (in this case chown command should fail). According to chown man page, the maximum value for uid and gid should be less than 60,000 and any specified value which is greater than or equal to UID_MAX (60,000) is INVALID and chown should return an error code (EINVAL). PHKL_11725: Systems that have patch PHKL_4413 installed may experience intermittent X server failures where mouse movement data is incorrectly sent from the keyboard device. This would cause the X server to abort. Such failures were seen on a customer's system with a frequency of about once per day. PHKL_10222: If the HIL keyboard is disconnected, reconnected, and then disconnected again very rapidly, the system will hang until the keyboard is once again connected. PHKL_9868: EXEC_MAGIC processes would core-dump after creating a memory mapped file (mmap(2)) with an address in the first quadrant (smaller than 0x40000000). This defect was introduced by PHKL_7852. PHKL_9229: Debugger gets EIO when issuing a ptrace PT_SINGLE request. PHKL_9149: panic: "bread: size 0" when using MMAP files on DUX. PHKL_7852: If you place your text in second quadrant of an EXEC MAGIC process (with -R linker option) and then mmap into the first quadrant, subsequent mmaps may fail with ENOMEM. PHKL_6869: Data corruption with FDDI on systems with hardware TLB-miss handlers. The known symptoms are user data corruption (as with Oracle ORA-00600 error 3339) and file-system panics. These symptoms were seen on systems used as NFS Servers. Hardware TLB-miss handlers are available on PA7100, PA7100LC and PA7200 PA-RISC processors. For a list of system models, see the file /usr/lib/sched.models. PHKL_6760: 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_6050: rpc.lockd timers are too agressive, causing NFS lock timeouts on busy networks PHKL_5994: Going over disk quota on an NFS-mounted filesystem causes erroneous "file system full" messages on the client console. PHKL_5832: EISA drivers that must lock the bus may not function properly. PHKL_5763: System hangs when there is heavy load and some processes which are swapped out use many number of private memory mapped regions or shared memory regions of atleast 33 pages. PHKL_5747: Memory-mapped filesystem call performance is slow when there are lots of memory mapped regions. PHKL_5699: This patch is an update of existing patches that makes them compatible with 9.07 release. PHKL_5656: Lexmark 3270 keyboard does not work. PHKL_5589: HIL interface problems are experienced with the ABB keyboard, such as loss of input from ABB-specific function keys or the inability to trigger or silence the built-in ABB keyboard alarm. PHKL_5536: panic: kernel out of virtual space; on an NFS server PHKL_5518: C1533 DDS2 drive will be better supported. PHKL_5391: Memory-mapped filesystem call performance is slow when there are lots of memory mapped regions. PHKL_5358: System hangs. The SRUN process kernel stack will have release_buffer, brelse, bmap, rwip, ufs_rdwr, vno_rw, rwuio. PHKL_5348: "mangled entry" - corrupt directory blocks PHKL_5165: This is a re-release of PHKL_4937 that is compatible with the 9.03, 9.05 and 9.05 PCO releases. PHKL_5160: This is a re-release and combination of patches PHKL_5137, PHKL_4324 and PHKL_3798 that is compatible with the 9.03, 9.05 and 9.05 PCO releases. PHKL_5137: panic "SCSI: unrecovered deferred error (dev = 0x%x)" PHKL_5076: Most customers should never see any visible symptoms. PHKL_5049: Applies several fixes for bugs found post-release. One includes: "Fixes a potential data corruption that can occur when performing raw SDS reads which span multiple stripes into a buffer that is not 32 byte aligned. The corruption can affect up to the last 32 bytes of each stripe prior to the last one. Note that filesystem I/O's, swap, and dd(1) are not susceptible to this corruption." PHKL_4959: The customer may experience a delay in either starting or stopping audio. PHKL_4943: panic "bread: size 0" when using pipes on DUX. PHKL_4937: panic: Data segmentation fault, in function openforwrite() PHKL_4895: Writes to full filesystem do not return errors. PHKL_4777: System hang under PHKL_4500. PHKL_4710: Incorrect cylinder group summary information. PHKL_4676: Internal beeper and microphone does not transmit system beeps with PHKL_3572. PHKL_4605: poor performance problem with access(2) over NFS. PHKL_4500: panic: virtual_fault: on DBD_NONE page while running xdb. PHKL_4324: Merge the 9.03 and 9.05 patch lines. PHKL_4323: SCSI defects and a diagnostic/RS232/VME defect. PHKL_4268: Memory leak in NFS. PHKL_4263: Programs executing over NFS swap text remotely, rather than locally. PHKL_4247: When debugging an NFS mounted file and another process modifies the text, the system can panic. PHKL_4226: Single-Ended SCSI devices are unaccessible after reboot. PHKL_4174: Hilkbd driver completes read even without any input. PHKL_4161: PHKL_4029 can panic when mounting NFS on DUX clients. PHKL_4158: SCSI floppy write protect & media missing fixes. PHKL_4110: rmdir does not return EBUSY on root or CWD. PHKL_4099: SCSI request timeouts on SE bus. PHKL_4054: SCSI: request timeout - bus = 0x1, tgt = 0x2 PHKL_4048: PHKL_3975 can panic systems with automounter, so it is backed out. PHKL_4029: Increase HOSTNAMESZ from 32 to 256 as per RFC 1123. (Resubmittal of PHKL_3986) PHKL_3992: Various keyboard problems with ME30 or PC-AT keyboards. PHKL_3986: Increase HOSTNAMESZ from 32 to 256 as per RFC 1123. PHKL_3975: Problems using readdir and seekdir across NFS. PHKL_3940: Open count not incremented correctly in PHKL_3572. PHKL_3929: "panic: H_READCONFIG failed" when booting. PHKL_3913: SCSI: request timeout - bus = 0x1, tgt = 0x2 PHKL_3798: "panic: trap type 18" when a process fragments the 3rd/4th quadrant resource map. PHKL_3795: Poor performance using memory mapped Files. PHKL_3791: panic: sti_save(): timeout on semaphore PHKL_3756: Mmap() cannot fix address in private data space. PHKL_3621: PC-NFS client of HP-UX machine sees apparent error trying to save a writable file or update its timestamp. PHKL_3620: physstrat does not allow interruptable DIL. PHKL_3617: panic "findentry: idx beyond region size" when doing raw I/O with shared memory. PHKL_3602: PT_CONTIN1 and PT_SINGLE1 ptrace requests have been added. PHKL_3601: panic: "freeing free inode" using mmap() on DUX servers. system hang using mmap(). PHKL_3600: Swapper/vhand interaction causes panic "csysmemreserve: reservation overrun". PHKL_3578: Audio driver state not restored on beep completion. PHKL_3572: "clicking" on the audio device. PHKL_3561: Remove OSF AES involving involving symbolic links. PHKL_3507: Poor syncer performance on systems with huge buffer caches. PHKL_3505: fsync(2) followed by crash shows data loss. Indirect blocks are not being written out to disk. PHKL_3472: Binaries not updated when written through NFS. PHKL_3434: panic "csysmemreserve: reservation overrun". PHKL_3422: Read failures on NFS file when server disk is full. PHKL_3421: Misleading message printed when comparing function pointers. PHKL_3394: Backplane networking setting of CPU number incorrect. PHKL_3361: panic "crfree: credential reference overflow". PHKL_3290: "panic: dup biodone" "SCSI: bus timeout - bus = 0xXX" EISA performance degradation after extended uptime. PHKL_3289: Invalid SCSI sense data returned to SCSI pass-thru commands. PHKL_3217: SCSI tape driver cannot set density to 1600bpi on 7980S tape drive. Defect Description: PHKL_12426: There is NO check in chown() system call for values of uid/gid which are greater or equal to UID_MAX (60,000). uid and gid are of type int (signed) and when they are assigned to va_uid and va_gid for doing a vnode operation, they are casted to 16-bit shorts. So the truncated values are passed onto the file system. uid and gid are defined as: register struct a { char *fname; int uid; int gid; } *uap; And va_uid and va_uid are defined as: u_short va_uid; /* owner user id */ u_short va_gid; /* owner group id */ Now in chown() we are assigning va_uid to uid thus truncating those values to 16-bits. vattr.va_uid = uap->uid; vattr.va_gid = uap->gid; NOTE: Some signed uid/gids are valid. e.g. -2 is used by NFS for "nobody" or "anonymous". We should not be truncating this information by only allowing positive values. All valid negative values fall as unsigned positive values above 60000 and below 65536 (-1 translates to 65535 in 16-bit signed/unsigned conversion). PHKL_11725: Patch PHKL_4413 regulates the system time of day clock by accessing the system real time clock hardware every 10 minutes. The system real time clock hardware is interfaced to the same coprocessor that also controls the HP-HIL loop used for the keyboard and mouse. A small timing window exists such that if the real time clock is read while a packet of data is being received from the mouse, incorrect data could be transmitted to the X server. PHKL_10222: The keyboard reconnection handler in the HIL driver can hang if the keyboard is disconnected immediately after being disconnected and than reconnected. This problem has only been reproduced by a customer designed HIL switchbox or by rapidly and repeatedly plugging and unplugging a keyboard (i.e. multiple times a second). PHKL_9868: The code change for PHKL_7852 could cause mmap() to alter the protection ID of the text pregion when: 1) specifying an address in the first quadrant, and 2) the executable was EXEC_MAGIC. This resulted in an instruction segmentation fault, and the process would die and core-dump right after resuming execution (returning from mmap()). PHKL_9229: When ptrace is single stepping an user signal handler and handling a sigcleanup call, if another signal is detected and launched during the return of this system call, the user pc is overwritten by the single step breakpoint address upon the completion of the return. PHKL_9149: System doesn't correctly handle resized MMAP regions accessed over DUX. The test for changed file size was modified to correctly handle this case. PHKL_7852: To reproduce the defect, write a test program that does two mmaps. First one specifies the map address as 0x1000 and the second one does not specify any (passes a 0). Use the -R0x40001000 linker option to start the text of this process in the second quadrant. When you run this test program, the first mmap succeeds but the second one fails sometimes. PHKL_6869: The NIO-FDDI card has the ability to split header and data on inbound packets. This allows the DMA-transfer for the data to take place into page-aligned buffers, which allows remapping of virtual pages as an alternative to a memory-to- memory copy. The page remapping is actually implemented as a page exchange, but the low-level VM routine providing page exchange support had a serious defect causing systems with hardware TLB-miss handlers to end up with valid data cache lines from pages not properly marked as accessed. Flushing the data cache would then not invalidate the cache lines as expected and the data cache would be left with stale data, possibly causing data corruption. Although the defect was initially found on systems with NIO-FDDI, the S700 "Built-in" FDDI card has the same header and data split feature, therefore S700 systems with FDDI are also impacted by the defect. PHKL_6760: 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 - A previous patch (PHKL_5079) makes 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. - If this previous patch has not been applied, files created by logins with large UIDs on the client will have the wrong UID on the server. This could be exploited by particular UIDs to gain root access 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_6050: The timers used by the client side portion of rpc.lockd are too aggressive. These timers control the amount of time the client rpc.lockd will wait before retrying locks that are still in progress (i.e., blocked). The timers were originally made more aggressive in response to concerns about slow NFS lock performance; since that time, rpc.lockd has been changed to address the same performance concerns, but in a different fashion. Thus, this patch should be installed with PHNE_5460 or any of its successors to maintain NFS lock performance. PHKL_5994: Filesystem full messages are displayed on the console and in /etc/dmesg output when the filesystem is not full. The filesystem in question is NFS mounted from another system and has quotas enabled on the server. The message occurs when a user reaches the hard limit on the mounted directory. This is caused by HP-UX mapping the EDQUOT error returned by the server to the error ENOSPC. This is later interpreted as a filesystem full condition, and gets printed to the client's console. The fix was to remove the mapping. With this patch installed, the user will see no console errors when they exceed their quota, and the error on their terminal will be "Disk quota exceeded". PHKL_5832: This patch fixes EISA arbitration problems that may occur on some Series 700 platforms that utilize the WAX EISA bus converter chip. EISA drivers that must lock the bus (using the ARBITRATION_DISABLE() and ARBITRATION_ENABLE() macros) may not function properly unless this patch is installed on the system. This problem was discovered with the Interphase FDDI card on a J-Series system. The wrong arbitration functions were being called because the EISA subsystem had incorrectly identified the system as using a non-WAX based EISA bus converter. The problem can cause the EISA card and driver to function incorrectly since the EISA bus will not be properly locked when the driver expects it to be. This can be reproduced by sending lots of small packets over the Interphase FDDI card. PHKL_5763: The system hangs because most processes are swapped out due to heavy load and the process which is the lead candidate to be brought in needs a lot of pages much more than freemem. So the swapper waits until freemem is high enough for this process to be brought in. Since none of the other processes which are swapped out are the lead candidate and there is no memory pressure in the system, vhand does not push out any more pages. This causes the whole system to hang until something happes to disturb this equilibrium point. This can be reproduced by allocating a lot of private memory mapped segments of at least 33 pages each. Then a heavy load is applied which forces this process and its VM data structures to be swapped out. At this point the system can hang. PHKL_5747: If a process memory maps lots of regions (files/anonymous) then performance will be slow, due to the fact that the kernel used a linear lookup. This patch supersedes PHKL_5391 which had a bug where "adb /hp-ux /dev/kmem" would hang the machine if done more than once. PHKL_5699: This patch makes PHKL_3791 and PHKL_5391 work on the 9.07 release. The kernel changes made for 9.07 have been incorporated into this patch. PHKL_3791 and PHKL_5391 had to be merged because they intersected with the 9.07 kernel changes. PHKL_5656: Lexmark 3270 does not send standard id. PHKL_5589: The HIL driver did not handle Register I/O errors correctly and the ABB keyboard was not responding fast enough to HIL loop data during the Write Register command. When the keyboard would not respond fast enough, it would generate a Register I/O error, which the HP-UX driver did not handle correctly. Two changes were applied to fix this problem. First, the Write Register command timing constraints were relaxed to give the keyboard plenty of time to handle loop data. Second, the HP-UX driver was modified to handle Register I/O errors correctly. The following additional changes were made to the HIL driver: A workaround was added for the 8042 firmware defect that returned a count of 7 loop devices when the last loop device is faulty. Ioctl calls will now fail with errno == EIO when less than the minimum number of bytes are returned by a loop command. Ioctl calls will now fail with errno == EIO if a loop reconfiguration occurs during the ioctl's loop command. Ioctl calls will now fail with errno = EIO if a loop command returns either Register I/O Error or Transmission Error. Also, a loop reconfiguration will be forced. When a HIL keyboard with Num Lock, Caps Lock and Scroll Lock indicators is used, striking keys during the "LED indicator flash" as the system boots will no longer cause problems. PHKL_5536: This patch fixes a "panic: kernel out of virtual space" on an NFS server. The panic is caused by an invalid read request coming from an NFS client, in particular a PC. The fix was to return an error if a read requests more than 64Kbytes. (Usually, NFS reads are for 8Kbytes only). PHKL_5518: C1533 device was used as a generic "black box" tape device so setmarks and SIOC_CAPACITY were not usable. Fbackup fastsearch did not work due to the lack of setmark support. PHKL_5391: If a process memory maps lots of regions (files/anonymous) then performance will be slow, due to the fact that the HP-UX kernel used a linear lookup. PHKL_5358: In alloc_more_headers and getnewbuf, toppriority was being incremented without checking to see if MAXPRIORITY was exceeded. This was causing hangs in the while loop in release_buffer because the buf field access_cnt is calculated from toppriority which could get up over 0x10000000. See SR or DTS for reproduction method. PHKL_5348: Reading a block device "/dev/dsk/..." for a filesystem while that filesystem is mounted and active can cause directory corruption. Symptoms include console messages "mangled entry". If allowed to continue, can cause "freeing free inode" panics. Problem can be reproduced by running "fsck -n" while simultaneously creating or deleting lots of small files or subdirectories. PHKL_5165: No additional defects were fixed in this patch. The purpose of the patch is to provide a patch that is equivalent to PHKL_4937 but is compatible with the 9.03, 9.05 and 9.05 PCO releases. PHKL_5160: No additional defects were fixed in this patch. The purpose of the patch is to provide a patch that is equivalent to PHKL_5137, PHKL_4324 and PHKL_3798 but is compatible with the 9.03, 9.05 and 9.05 PCO releases. PHKL_5137: The panic message printed out 0x%x instead of the device. PHKL_5076: Check nfs uid against MAXUID. PHKL_5049: See customer visible symptoms. Several problems fixed, so replication would be difficult. PHKL_4959: When an audio read or write is executed and the data does not fill a physical page, the rest of the page is filled with silence. The next read/write is not done until the DMA for the previous physical page is complete, including the silence. This is seen as latency in the driver. PHKL_4943: This patch fixes a panic when using named pipes on DUX. This happens due to a race condition between the close and the open of a named pipe. This race condition leaves the inode size as zero but the fifosize as non-zero. So the process which does a read thinks that there is data in the pipe to read but the inode size is zero and so the bread panics with the message "bread: size 0". PHKL_4937: Under certain circumstances, the kernel would panic with a data segmentation fault, in the function openforwrite(). Openforwrite() was not locking the vnode associated with the file it was checking, which led to inconsistencies between the vnode flags and internal fields. There were no obvious reproduction methods. PHKL_4895: Return u.u_error when writing to full filesystem. PHKL_4777: Fix for PHKL_4500. Release the region lock in fault_each() for the case when we fail to bring_in_pages(). In PHKL_4500, we were returning without releasing the region lock acquired earlier. Strange things can happen (including system hangs) in the special situation when a user does xdb on an NFS file (this ensures that the path ptrace()->pre_demand_load() is taken) in a heavily loaded (heavy load means bring_in_pages will fail) system. PHKL_4710: Rolled S800 autoch.c rev 1.13.73.9 autochanger fixes to 9.03/9.05. Merged S800 ufs_pmount.c rev 1.6.73.4 with S700 ufs_pmount. Fixes the cylinder group summary information. PHKL_4676: Fix for internal beeper and microphone not transmitting system beeps with PHKL_3572. This problem was originally reported on 747i/745i systems with Release 9.01 PHKL_2837. The source of the problem is PHKL_2837 in Release 9.01 that prevents the beeper from working in 745/747 workstations. The problem lies in the way we maintain the audio_descriptor's open_count (audio_des->open_count). PHKL_2837 and PHKL_3572 allowed this count to be initialized to -1 (it used to be initialized to 0 in the before) so that a distinction could be made between the first open and a secondary open on that audio device. We increment this count in audio_open() to count the number of times this audio device is open. In audio_close(), we check this count and return ENODEV if audio_des->open_count is <= 0. And this is exactly where PHKL_3572 can break the beeping functionality. For more details see PHKL_4655 (Release 9.01) patch text file. PHKL_4605: This patch fixes a performance problem with the access(2) system call when executed across NFS. Without the patch, access does not make proper use of the client's caches; therefore, it generates unnecessary requests to the server. This is very obvious if you run access(2) in a tight loop using a single file as the argument. You would expect the first call to generate a request to the server and any subsequent calls to use the client's cache, but this would not be the case. The patch fixes this problem and allows the client to use its cache and avoid the unnecessary requests. PHKL_4500: The failure was caused due to an error in fault_each() while bringing pages into memory. However, because fault_each() was not reporting this error, the error was not getting propagated up the call chain. The fix involves getting fault_each() to return an error value upon failure and to have its callers for the return value and do likewise upon an error. In particular, pre_demand_load(), which is responsible for fetching file text and data across NFS mount points, needs to check for failure and report an error return value to its caller so that the calling process can terminate itself with a SIGKILL. PHKL_4324: The only reason for this patch is to allow future patches for 9.03 and 9.05 to be interchangeable, as opposed to having to generate separate patches for each one of those two releases. This patch contains core kernel files exclusively and NOT the full contents of the 9.05 software release. Consequently, this patch should not be used to upgrade the OS to the 9.05 release. If a customer is upgrading the hardware then they must use the standard update or install procedure to get the necessary new software. This patch applies only to the 700/9.03 release; the changes are already included in the 700/9.05 release so there is no need for a 700/9.05 patch. PHKL_4323: This patch: 1 reenables 10Mb/s for EISA Fast/Diff which was inadvertently reduced to 6.25Mb/s in the 700/903 release. 2 improves performance by enabling cache bursts for Single-Ended SCSI. 3 fixes a bug which caused the SCSI driver to incorrectly index into a table using device ids greater than 7. 4 allows diagnostics to work with the second RS232 port on models 743i/64 and 743i/100. Items 1, 2 and 3 are already fixed in the 700/905 release. For those running Release 9.03, item 3 is probably the most important; all 9.03 systems with a Fast/Wide SCSI interface with one or more disks having a SCSI ID > 7 should apply this patch so they can grab fix 3 in the above list. Item 4 is not applicable to Release 9.03 because it only applies to the 743i/64 and 743i/100 which only run Release 9.05. Therefore, if you are running either one of those two models with the Release 9.05, and are experiencing problems with the second RS232 port, you probably want to install this patch so you can grab fix 4 in the above list. PHKL_4268: This patch fixes a memory leak in NFS. NFS code clfree() does not FREE all the MALLOC'd structures. So this causes a slow memory leak because the structure not FREE'd is 64 bytes. PHKL_4263: If file executed on remote fs and sticky bit is set on that executable, try to use local swap device instead of using the executable image as the swap. At HP-UX 8.0, HP revised the Virtual Memory System (VM) to include changes to support shared libraries, copy on write, etc. HP also made changes so that when text(code) segments are paged out, they are no longer written to the swap area. This is an improvement for applications on a local disk drive, reducing I/O and swap requirements. However, for applications utilizing a "program" server, the retreival comes from the network via NFS, with a potentially slower access time. For certain large applications, this can be a problem. We have created this patch so that if a file is executed on a remote filesystem and the sticky bit is set on that executable, we will try to use the local swap device for the text instead of using the executable image as the swap. PHKL_4247: When debugging an NFS mounted file and another process modifies the text, the system can panic. The customer is actually running Andrew File System, but the same behavior occurs under NFS as well. PHKL_4226: This patch fixes a problem with devices connected via the HP A2679A EISA SCSI-2 (Single-Ended) Host Adapter. Devices connected to this SCSI card were not accessible after a "soft" system reboot. The only way to clear this error was to cycle power on either the CPU or the SCSI devices. The fix was to reset both the host adapter and the bus during the boot process, an operation that normally occurs without intervention on the other (differential) SCSI host adapters. PHKL_4174: Fix for hilkbd driver completing read even without any input. This problem can be seen only in ITE mode (no X11/HPVUE). A simple open, read, and close of /dev/hilkbd could cause the system to enter an inconsistent state. Specifically, on the next keyboard read, the driver would not wait for keyboard input. This happened because the system was continuously interrupted by the keyboard with the last cooked key pressed though the device file had been closed. This caused subsequent reads on that device file to never wait for keyboard input (since the system was being interrupted with the last pressed key). The fix consisted of: * Turning on autorepeat and cooked mode in the proper sequence in the driver's open routine (nimitz_open) * Clearing the autorepeat register when closing the cooked keyboard driver. PHKL_4161: HOSTNAMESZ is back to 32 and will stay that way because of problems with DUX code being written in an inelastic manner. PHKL_4158: This fix addresses two problems with the SCSI floppy driver: 1) Open and Write attempts to a write protected floppy previously reported no errors. Fix: Return EACCES on any open with WRITE flag specified when write protect is set on the media. 2) Accessing the floppy drive when no diskette was present resulted in a message being displayed on the console that media might have changed, even though no media had ever been in the drive. Fix: Return ENXIO on any open attempt when media is not present in the floppy disk drive. PHKL_4110: rmdir does not return EBUSY when it should. rmdir returned errno 21 [EISDIR] when the path was root. rmdir returned errno 22 [EINVAL] when the path was CWD. Now rmdir returns EBUSY if you try to remove root or CWD (Current Working Directory). PHKL_4099: This patch fixes two known corner cases on the NCR53C700 Single-Ended bus that create timing windows in the scsi_c700 interface driver. The first known corner case was addressed by PHKL_4054, below. This was the driver's reading of registers when SIP and DIP were not set appropriately. The second fix addressed by this patch is another timing window where it is possible for an I/O to become lost in the I/O path of the driver. The fix was for the driver to check for both these conditions and as a result, it addresses all known SCSI request timeout problems encountered to date. PHKL_4054: This patch fixes a problem with the Single-Ended Core SCSI bus where periodically the driver would lose an interrupt. This would result in a SCSI request timeout being logged to the kernel message buffer and the I/O being aborted. In the case of disk drives, a 150 second hang of the system would occur prior to the I/O timing out and being retried. Example message buffer: SCSI: request timeout - bus = 0x1, tgt = 0x2 PHKL_4048: Backing out fix made for PHKL_3975. This patch backs out the fix made for PHKL_3975. The original fix for the NFS readdir problem can cause a panic on systems with automount. So until a better solution is found for the NFS problem the changes are backed out. PHKL_4029: Increase HOSTNAMESZ from 32 to 256 as per RFC 1123. PHKL_3986 didn't include all of the required .o's affected. This patch fixes that deficiency. PHKL_3992: This patch fixes two distinct problems with HIL devices. 1) Moving the mouse slowly during bootup can cause a system with the PC-AT keyboard (C1429) to panic with the message "g->loop_response overflow". This was caused when the HIL driver received mouse movement information (also known as autopoll data) while it was exercising the lights on the PC-AT keyboard. The driver had disabled autopoll input, but had failed to wait for the input queue to drain. With this fix, the driver verifies that the autopoll queue is empty before issuing an HIL command. 2) Systems with the 46021B keyboard and several HIL devices could see input from keyboard or other HIL device misdirected to the ITE (Internal Terminal Emulator), instead of to a window or application. Removing and/or replacing any HIL device usually clears the problem. This was caused when the driver received a loop reconfiguration interrupt in the midst of an HIL command. As part of its reconfiguration, the driver issues its own HIL commands; the completion status values of the two commands were then interleaved, thus causing the driver to interpret an "okay" completion status as the number of devices connected to the HIL. With this fix, the driver defers its reconfiguration until the HIL has no command in progress. The 46021B keyboard seems to cause a large number of loop reconfigurations; these are only expected when devices are added to or removed from the HIL, or when there are loop errors. Applications such as ME30 which stress the HIL may exacerbate the loop reconfigurations. PHKL_3986: Increase HOSTNAMESZ to 256 to allow domain names greater than 32 characters. PHKL_3975: This patch fixes a problem with NFS when customers use the library calls readdir and seekdir. NFS normally compacts the directory entries. The UFS and other filesystems return the directory entries as it is laid out in the disk. This can cause problems in readdir and seekdir in NFS because of the difference in format returned to the library call. So this NFS fix is to expand the directory entries and include blank entries in the buffer returned to user through the system call getdirentries. This is consistent with how the buffer is returned across all filesystems. PHKL_3940: Open count not incremented correctly in PHKL_3572. PHKL_3940 fixes this defect. PHKL_3929: Using an ABB keyboard (this keyboard constantly sends data) or any other HIL device through which data is sent while the system is booting can panic the system with the message "H_READCONFIG failed". Whenever a key is pressed, it is transmitted to the 8042 chip which sets a bit in the Interrupt Pending Register. As part of the boot process, the kernel clears the Interrupt Pending Register in the ASP controller and thus erases any knowledge that an interrupt is pending. Thus, even when the Interrupt Mask Register is set an interrupt is not generated. When the HIL driver sends a H_READCONFIG command to the chip to check if there is a device, it never receives an interrupt, and therefore never gets the data back. This causes it to go into a loop and then panic. This particular panic does not occur under 9.01. It was introduced at 9.03 due to changes in the kernel's interrupt handler. PHKL_3913: This patch fixes a problem with the Single Ended Core SCSI bus where periodically the driver would lose an interrupt. This would result in a SCSI Request Timeout being logged to the msgbuf and the I/O being aborted. In the case of disk drives, a 150 second hang of the system would occur prior to the I/O timing out and being retried. PHKL_3798: The kernel will panic with a trap type 18 when a process fragments the 3rd/4th quadrant resource map. The map becomes fragmented when process(s) heavily use memory mapped files or shared memory, generating space between subsequent mappings. This causes the internal data structure to fragment and grow. Eventually the kernel panics accessing an address like 0.80XXX in the VM system, possibly pageremove(). The failure is an overwriting of the the internal hash array by the 3rd/4th quadrant resource map. The space allocated for the map was smaller than what the map thought it contained and fragmentation overlayed the page directory hash chains. PHKL_3795: Implemented read ahead algorithm and other enhancements to improve the performance of writes to sparse files. With the in-house benchmark, the performance was improved by a factor of 2 for non-sparse files using this patch. The performance of a sparse file was improved by a factor of 6 when writing to a sparse file. This is a port of patches PHKL_2847, PHKL_3028, PHKL_3343 and PHKL_3477 from 9.01. This patch should be installed for any customer who is concerned about memory mapped file performance. PHKL_3791: The frame-buffer driver, part of the graphics display driver set, allows users to obtain information about the display through the GCDESCRIBE ioctl call. Since the frame-buffer can be in use by the Internal Terminal Emulator (ITE), the frame-buffer driver and ITE implement a semaphoring scheme to ensure the two can both safely access the graphics hardware without interacting. Unfortunately, it is possible for the GCDESCRIBE ioctl to exit prematurely, after it has grabbed the semaphore; this leaves the hardware locked, so that the ITE cannot gain access. After some time, the ITE times out waiting on the semaphore and panics, with the message "sti_save(): timeout on semaphore." Specifically, the GCDESCRIBE ioctl locks the semaphore, then tries to save the graphics display state; since it is possible for the display to be busy, the driver enters a retry loop, calling sleep() with a short (.04 second) timeout. The problem is that the sleep() is made at an interruptible priority (> PZERO), so that user signals cause the ioctl to return immediately; while this is appropriate design, since it avoids process delays, the sleep() does not take into account the semaphore lock. Thus, when any user signal interrupts the process, the sleep() performs a longjmp, returning directly to the user program -- leaving the semaphore locked. The fix was to modify the sleep() call to catch the signal, by setting PCATCH; in this way, the ioctl can release the semaphore before returning to the user. An equivalent patch for HP-UX Release 9.01 is PHKL_3790. This defect was fixed in HP-UX Release 9.05. PHKL_3756: Allows caller of mmap() to fix address in private data space with MAP_SHARED as long as no other process has the file mapped. The mmap becomes "exclusive" and only that process is allowed to access the file. With HP's global address space, it is impossible to guarantee the availability of an address. There is a class of applications that hard code in pointer values into file data, requiring the subsequent mmap to be at a specific location. To alleviate this problem, this patch allows a caller of mmap() to map a file shared into the process's private data space. Previously all MAP_SHARED mmap() calls had to return an address in the global address space(quad 3/4). The caller "fixes" the address by specifying an address to mmap() and includes the MAP_FIXED flag. If there are no other users in the system mapping that file, the mmap() will create an "exclusive" mmap, where only that process is allowed to access that file through mmap in MAP_SHARED mode. Only MAP_PRIVATE calls can be made on exclusive mmaps. The exclusive mmap is kept until the user removes all mmap references to that file and the pseudo-address space is removed. During the exclusive mapping, only that process can mmap the file MAP_SHARED. Children (fork or vfork) will be rejected. Since only the parent can access the file, any children created do not contain the exclusive mappings. PHKL_3621: PC-NFS client of HP-UX machine sees apparent error trying to save a writable file or update its timestamp. NFS clients which have write permission for a file need to be able to update the modification time (see utime(2)), but the NFS protocol does not support it. Various vendors have invented nonstandard workarounds. This is one of them. PHKL_3620: Changed physstrat to allow interruptable DIL as on the Series 300. PHKL_3617: Fix for panic "findentry: idx beyond region size" The system panics during raw I/O between a shared memory segment and a disk or tape if the size of the I/O as specified in the read/write call extends past the end of the shared memory segment. The user process requesting the I/O must have one or more shared memory segments contiguous to the first segment which together encompass all the data requested to be input/output. The panic will either be "Data segmentation fault" or "findentry: idx beyond region size". physio() and vsunlock() will be on the stack trace. This fix also prevents a panic that occurs when one or more filesystems on SDS (Software Disk Striping) partitions are mounted and diagnostics is then used to access some other device on the system. PHKL_3602: Two new ptrace requests, PT_CONTIN1 and PT_SINGLE1 have been added. The requests PT_CONTIN1 and PT_SINGLE1 essentially do the same function as their counterparts PT_CONTIN and PT_SINGLE with the difference that signals pending for the traced process are not cleared. PHKL_3601: This patch fixes a "panic: freeing free inode" on DUX servers when a DUX client is using memory mapped files. The patch also fixes a hang related to the use of msems (memory mapped file semaphores) on DUX as well as non-DUX systems. The server panics with "freeing free inode" because it thinks that the mmapped file has already been removed or unlinked; there should not be any more requests against that file coming from the client. However, there is a write request that comes in, which eventually tries to free the inode again, causing the panic. The write request is generated by the client when the last process with the file mmapped exits. At that time, the file is unmapped and any dirty pages are scheduled for I/O; one of those I/O requests causes the server to panic. The fix for this problem was to wait for the IOs to complete before doing the final remove/unlink of the file. In addition, the original msem_lock() call allowed a process to sleep forever if it tried to grab a semaphore it already owned. This in itself was not catastrophic, because the process could be killed and everything would be cleaned up properly. However, if a second process attempted a lock on that same semaphore, while the first process was waiting on itself, then the system would hang. The best way to diagnose this problem is to get a TOC dump and look for the kernel stack of the running process. The routine msleep() should appear at the top. The fix for this problem was to return an error (EDEADLK) whenever a process attempts to grab a semaphore that it already holds. PHKL_3600: This fixes a reservation overrun panic; the panic string looks like: csysmemreserve: reservation overrun The problem was in the interaction between vhand and the swapper. This patch fixes this problem by making sure that vhand does not page out some pages that the swapper is trying to bring in. PHKL_3578: Fix to restore the audio driver state on beep completion. The code has been changed to allow the driver state to be restored on beep completion. Earlier, we would beep and the previous audio state would not be restored until the driver was re-entered through open, RW, ioctl. PHKL_3572: Fix to minimize the "clicking" on the audio device. This is the 9.03 port of the 9.01 patch PHKL_2837. Every time the sample rate, gain and sound format of an audio device is changed, an audible "click" will be heard on the speaker. This is unavoidable due to the programming of the audio hardware. This patch in conjunction with PHSS_3103 (non MPower) or PHSS_3104 (Mpower) attempts to minimize the clicking which occurs by modifying the way the driver sets the defaults on opens and closes. As well as how the Aserver handles monitoring. If both this patch (PHKL_3572) and PHSS_3103/PHSS_3104 are not used together, clicking will still occur. This is because changes are needed in the driver (PHKL_3572) as well as the Aserver (PHSS_3103/PHSS_3104). Prior to this patch, the audio driver would reset the sample rate, data format and gain when the last close of the audio device occurred (open count = 1). It would also ensure that audio DMA had completed on the next subsequent open (open count = 0). With this particular change in place, the audio driver reacts slightly different. The audio driver will now never reset the audio system to default sample rate, data format and gain. Instead it will use the last configured rate as the default for the next open of the device. This has the side effect that anyone who attempts to cat a sound file to the device file will now not be able to depend on the default settings of the audio driver. However, it is extremely unlikely that anyone was using this interface because the Aserver currently keeps the device open and in a different configuration than 8000khz/mulaw which the driver uses. So, you get different results today depending on if the Aserver is running or not. When used in conjunction with PHSS_3103/PHSS_3104, sound quality will be improved for users who are continually playing the same sound sample rate, data format and gain. If any of these parameters is adjusted in order to play a sound sample, a subtle "click" will be heard the first time the audio hardware is programmed to this configuration. Subsequent attempts at playing the sound will be clean. The Aserver implements a "monitor" mode which is controlled via the utility AudioCP. When "monitor" mode is enabled, a click will be heard when the Aserver reconfigures the sample rate and audio format for monitoring to work. PHKL_3561: This patch removes OSF AES compliance involving symbolic links. It effectively forces hpux_aes_override to always be on, and cannot be overridden. PHKL_3507: Fix syncer performance problems on systems with huge buffer caches. Modified tflush() to only walk once through the buffer cache, keeping track of which buffers to write, then writing them at the end of the walk through. PHKL_3505: Indirect blocks were not being written out to disk on an fsync(2). PHKL_3472: NFS problem where updates to binaries are not recognized by system. Problem can be seen by running a binary that displays a string stored as a constant variable, then running a second binary that modifies the contant value in the first binary changing the string, and running the first binary again. Instead of displaying the new string it displays the original string. This problem will not show up on regular updates through re-compiling the application but only on binaries which are opened without truncation and written to it. The problem on binaries can also be noticed on MMFs in NFS. A NFS memory-mapped file is opened and written and then unmapped. The file is then updated through the regular file system write and closed. It then is mapped again as MMF and when read the updates done through the filesystem is not visible. Both the problems are due to a bug in rwvp(). The pages corresponding to a block are not removed from the pagecache when writing through the filesystem. So, the pagecache contains the old copy. PHKL_3434: Fix for panic cmemreserve: reservation overrun. Memory reservation routines memreserve, cmemreserve, ciomemreserve, and memunreserve have been replaced by new functions that take an extra parameter. This problem occurs because the memory reserved by the swapper in order to swap a process in (UAREA + vfds of the process being swapped in) is being exhausted. When the swapper is attempting to swap in a process, it must first reserve enough memory to bring in the process' UAREA and vfds. Swapper calculates the number of pages needed for bringing in these data structures and reserves sufficient memory. When attempting to bring in pages from UAREA, CAM will handle the IO request, but before returning it will attempt to also handle a request for an incoming LAN packet. To handle the incoming packet, the LAN driver needs memory and will eventually end up calling cmemreserve(). Unfortunately, cmemreserve() has no way of knowing that this call is not on behalf of the swapper, so some of the memory that swapper had reserved to swap in the process gets exhausted in handling the LAN package. When the swapper finally finds out that it has run out of memory, it panics. In summary, the logic for handling memory reservation for the swapper when attempting to swap in a process is flawed. The implicit assumtion that no one except the swapper will call cmemreserve() in the context of the swapper is false. PHKL_3422: A file that was being written to and had filled up the server's disk could not be read: All reads and writes to that file would fail and return ENOSPC (disk full) until all processes had closed the file. This would make it look like the file was empty even though the ll(1) showed it had a size greater than 0. This patch allows reads to succeed even if a write had failed. Writes will still fail with ENOSPC because the of the asynchronous writes of NFS don't allow the kernel to know which process or which write actually failed. PHKL_3421: When comparing two function pointers and the value of the function pointer is garbage, the system prints the following message: Pid 5868 received a SIGSEGV for stack growth failure. Possible causes: insufficient memory or swap space, or stack size exceeded maxssiz. This is erroneous and should not be printed even when comparing a garbage function pointer. This has been fixed and as usual no core is dumped. PHKL_3394: Fixes backplane networking setting of CPU number. Adds support for backplane networking with 747/100 processors. Fixes parameters required in PDC call requests 0 and 7 for VME (libvme.a) services. Adds VME options 10 and 11 for backplane networking on the 747 100 Mhz processors. The fixes to VME requests 0 and 7 allow vme_config and PDC admin modes to both set the same values of CPU numbers. CPU numbers are used in backplane networking by HP-UX and HP-RT processors, and this patch resolves a conflict between HP-UX and HP-RT when communicating with backplane networking. PHKL_3361: Fix for a "panic: crfree: credential reference overflow" which happens on an NFS client with a large inode table. The panic message should look something like this: crfree(0x04129900) : bad cr_ref -32768 panic: crfree: credential reference overflow The problem is well described in the message, namely the cr_ref field is a signed short and has been overflowed because there are too many pointers to the same credentials structure. (See struct ucred in user.h) This is most likely to happen: - when the system has been configured with a large numbers of inodes, say 10,000 or more, and - when the system is accessing lots of files across NFS. The problem has occurred when running a large ls or a large find across NFS; it has also occurred while running fbackup across NFS. The fix is more of a workaround because we cannot simply redefine the size of the cr_ref field at this time. (That would create a huge patch!) The patch simply forces the system to bypass the directory name lookup cache (dnlc), which is the root cause of many of the references, once the cr_ref fields goes beyond 0x4000. For the 10.0 release, we will increase the size of the field. This problem does not occur on the 800/9.0X releases, only on the 700/9.0 releases. PHKL_3290: This patch fixes the following problems: 1) Panic: dup biodone(). 2) Unexpected message "SCSI: bus timeout - bus = 0xXX" in the kernel message buffer. 3) EISA performance degradation after extended uptime. Defect Description: 1) There was a race condition between the setting of "temp" to "Ent_running" by the NCR SCSI controller (via the scripts) and the setting of "lbp->running" by c700_cmd_sent(). If "isc->running" pointed to the last request and a timeout occurred between the setting of "temp" and the setting of "lbp->running" to the current request, the wrong request pointer was returned. 2) The device open count was incorrect during some last closes which caused the close routine to not turn off bus timeouts. 3) The device open count was incorrect during some last closes which caused the close routine to release EISA SCSI iomap entries. Fix: 1) Zeroed "lbp->running" prior to starting a new request. If a timeout occurs and "lbp->running" is NULL, "isc->owner" is returned. 2) Fixed the device open count so that the close routine turns off the bus timeout. 3) Fixed the device open count so that the close routine release the EISA SCSI iomap entries. PHKL_3289: Invalid SCSI sense data returned to SCSI pass-thru commands; Adds support for A32 VME SCSI cards. Symptoms: Invalid SCSI sense data returned after a SCSI STATUS check condition. Defect Description: An IF statement only checked "sctl_io->sense_xfer" before copying the per bus sense buffer. If sctl_io->sense_xfer is not zeroed before the operation, the per bus sense buffer will be copied which in turn causes it to be cached. If the per bus sense buffer is currently being used by another request, this will cause a cache consistency problem, which may result in invalid sense data being return to the device driver. Fix: Now sctl_io->cdb_status and sctl_io->sense_status are checked to determine if the per bus sense buffer is owned by this request before copying the sense buffer. A32 VME SCSI interface drivers are now supported by SCSI services. PHKL_3217: This fixes a problem with the SCSI tape driver where it would unsuccessfully set density to 1600bpi for the 7980S tape drive. In effect, all tapes would be written at 6250bpi without the user's knowledge. The patch remedies the situation and allows 1600bpi tapes to be successfully written on the 7980S tape drive. SR: 1653058123 1653060392 1653064147 1653082941 1653083899 1653083907 1653085423 1653089763 1653092064 1653092627 1653099481 1653101337 1653107946 1653108472 1653112870 1653125401 1653130468 4701229757 4701248039 4701279885 4701297465 4701314302 4701315457 4701328823 4701354639 5003144683 5003148973 5003153403 5003154153 5003163493 5003168963 5003171520 5003172734 5003179754 5003181255 5003181404 5003188490 5003195370 5003197897 5003224915 5003227710 5003237537 5003262170 5003264259 5003269464 5003282087 5003338384 5003344630 5003347567 5003355768 5003374389 Patch Files: /etc/conf/graf.800/frameb_spc.h /etc/conf/graf.800/graph3.h /etc/conf/graf.800/stirom.h /etc/conf/graf/gpu_data.h /etc/conf/graf/ite.h /etc/conf/libdskless.a(dux_exec.o) /etc/conf/libdskless.a(dux_lookup.o) /etc/conf/libdskless.a(dux_mount.o) /etc/conf/libdskless.a(dux_vnops.o) /etc/conf/libhp-ux.a(asm_vm.o) /etc/conf/libhp-ux.a(audio.o) /etc/conf/libhp-ux.a(autoch.o) /etc/conf/libhp-ux.a(beep.o) /etc/conf/libhp-ux.a(bootpath.o) /etc/conf/libhp-ux.a(dconfig.o) /etc/conf/libhp-ux.a(diag1.o) /etc/conf/libhp-ux.a(eeprom.o) /etc/conf/libhp-ux.a(eisa.o) /etc/conf/libhp-ux.a(eisa_sysbrd.o) /etc/conf/libhp-ux.a(framebuf.o) /etc/conf/libhp-ux.a(graph3.o) /etc/conf/libhp-ux.a(hdl_fault.o) /etc/conf/libhp-ux.a(hdl_init.o) /etc/conf/libhp-ux.a(hdl_policy.o) /etc/conf/libhp-ux.a(hdl_trans.o) /etc/conf/libhp-ux.a(init_sent.o) /etc/conf/libhp-ux.a(io_subr.o) /etc/conf/libhp-ux.a(kbd_code.o) /etc/conf/libhp-ux.a(kern_exec.o) /etc/conf/libhp-ux.a(locore.o) /etc/conf/libhp-ux.a(machdep.o) /etc/conf/libhp-ux.a(pdc_rqst.o) /etc/conf/libhp-ux.a(pfail.o) /etc/conf/libhp-ux.a(ps2.o) /etc/conf/libhp-ux.a(s_hil_code.o) /etc/conf/libhp-ux.a(s_hil_drv.o) /etc/conf/libhp-ux.a(scsi_c700.o) /etc/conf/libhp-ux.a(scsi_changer.o) /etc/conf/libhp-ux.a(scsi_ctl.o) /etc/conf/libhp-ux.a(scsi_disk.o) /etc/conf/libhp-ux.a(scsi_floppy.o) /etc/conf/libhp-ux.a(scsi_tape.o) /etc/conf/libhp-ux.a(snakes_rs232.o) /etc/conf/libhp-ux.a(stirom.o) /etc/conf/libhp-ux.a(subr_prf.o) /etc/conf/libhp-ux.a(subr_xxx.o) /etc/conf/libhp-ux.a(sys_ki.o) /etc/conf/libhp-ux.a(sys_proc.o) /etc/conf/libhp-ux.a(vfs_bio.o) /etc/conf/libhp-ux.a(vfs_dev.o) /etc/conf/libhp-ux.a(vfs_dnlc.o) /etc/conf/libhp-ux.a(vfs_scalls.o) /etc/conf/libhp-ux.a(vfs_vm.o) /etc/conf/libhp-ux.a(vfs_vnode.o) /etc/conf/libhp-ux.a(vm_devswap.o) /etc/conf/libhp-ux.a(vm_fault.o) /etc/conf/libhp-ux.a(vm_kern.o) /etc/conf/libhp-ux.a(vm_machdep.o) /etc/conf/libhp-ux.a(vm_machreg.o) /etc/conf/libhp-ux.a(vm_mmap.o) /etc/conf/libhp-ux.a(vm_msem.o) /etc/conf/libhp-ux.a(vm_page.o) /etc/conf/libhp-ux.a(vm_pdir.o) /etc/conf/libhp-ux.a(vm_pregion.o) /etc/conf/libhp-ux.a(vm_sched.o) /etc/conf/libhp-ux.a(vm_swp.o) /etc/conf/libhp-ux.a(vm_text.o) /etc/conf/libhp-ux.a(vm_vas.o) /etc/conf/libhp-ux.a(vm_vfd.o) /etc/conf/libhp-ux.a(vsc_config.o) /etc/conf/libhp-ux.a(vsc_ioconf.o) /etc/conf/libnfs.a(klm_lckmgr.o) /etc/conf/libnfs.a(nfs_server.o) /etc/conf/libnfs.a(nfs_subr.o) /etc/conf/libnfs.a(nfs_vfsops.o) /etc/conf/libnfs.a(nfs_vnops.o) /etc/conf/libnfs.a(nfs_xdr.o) /etc/conf/libnfs.a(nfstest.o) /etc/conf/libnfs.a(spec_vnops.o) /etc/conf/libufs.a(ufs_bmap.o) /etc/conf/libufs.a(ufs_dir.o) /etc/conf/libufs.a(ufs_pmount.o) /etc/conf/libufs.a(ufs_subr.o) /etc/conf/libufs.a(ufs_vfsops.o) /etc/conf/libufs.a(ufs_vnops.o) /etc/conf/machine/eisa.h /etc/conf/machine/pde.h /etc/conf/nfs/nfs_clnt.h /usr/include/machine/pde.h /usr/include/nfs/nfs_clnt.h /usr/include/sys/audio.h /usr/include/sys/eisa.h what(1) Output: /etc/conf/graf.800/frameb_spc.h: frameb_spc.h: $Revision: 1.3.61.4 $ $Date: 95/06/18 19:42:08 $ frameb_spc.h $Date: 95/06/18 19:42:08 $ $Revision: 1.3.61.4 $ PATCH_9.03 (PHKL_5699) /etc/conf/graf.800/graph3.h: graph3.h: $Revision: 1.2.61.4 $ $Date: 95/06/18 19:4 6:16 $ graph3.h $Date: 95/06/18 19:46:16 $ $Revision: 1.2. 61.4 $ PATCH_9.03 (PHKL_5699) /etc/conf/graf.800/stirom.h: stirom.h: $Revision: 1.2.61.5 $ $Date: 95/06/18 19:4 7:43 $ stirom.h $Date: 95/06/18 19:47:43 $ $Revision: 1.2. 61.5 $ PATCH_9.03 (PHKL_5699) /etc/conf/graf/gpu_data.h: gpu_data.h: $Revision: 1.5.61.7 $ $Date: 95/06/18 19 :44:43 $ gpu_data.h $Date: 95/06/18 19:44:43 $ $Revision: 1. 5.61.7 $ PATCH_9.03 (PHKL_5699) /etc/conf/graf/ite.h: ite.h $Date: 95/06/18 19:46:48 $ $Revision: 1.11.61 .6 $ PATCH_9.03 (PHKL_5699) /etc/conf/libdskless.a(dux_exec.o): dux_exec.c $Revision: 1.5.61.6 $ $Date: 94/04/28 13:34:30 $ PATCH_9.03 (PHKL_4161) /etc/conf/libdskless.a(dux_lookup.o): dux_lookup.c $Revision: 1.7.61.11 $ $Date: 94/11/0 1 15:11:14 $ PATCH_9.03 (PHKL_4943) /etc/conf/libdskless.a(dux_mount.o): dux_mount.c $Revision: 1.8.61.13 $ $Date: 94/04/2 8 13:34:12 $ PATCH_9.03 (PHKL_4161) /etc/conf/libdskless.a(dux_vnops.o): dux_vnops.c $Revision: 1.9.61.15 $ $Date: 94/11/0 1 15:13:40 $ PATCH_9.03 (PHKL_4943) /etc/conf/libhp-ux.a(asm_vm.o): asm_vm.s $Revision: 1.50.61.11 $ $Date: 95/02/08 12 :23:42 $ PATCH_9.03 (PHKL_5049) /etc/conf/libhp-ux.a(audio.o): audio.c $Revision: 1.2.61.27 $ $Date: 94/11/21 14:29:23 $ PATCH_9.03 (PHKL_4959) /etc/conf/libhp-ux.a(autoch.o): autoch.c $Revision: 1.8.61.28 $ $Date: 95/06/20 07:0 9:45 $ PATCH_9.03 (PHKL_5160) /etc/conf/libhp-ux.a(beep.o): beep.c $Revision: 1.2.61.8 $ $Date: 94/11/21 1 4:33:21 $ PATCH_9.03 (PHKL_4959) /etc/conf/libhp-ux.a(bootpath.o): bootpath.c $Date: 95/06/18 19:38:57 $ $Revision: 1. 4.61.4 $ PATCH_9.03 (PHKL_5699) /etc/conf/libhp-ux.a(dconfig.o): dconfig.c $Revision: 1.2.61.13 $ $Date: 95/06/20 07: 11:00 $ PATCH_9.03 (PHKL_5160) /etc/conf/libhp-ux.a(diag1.o): diag1.c $Revision: 1.2.61.4 $ $Date: 95/06/20 07:11: 20 $ PATCH_9.03 (PHKL_5160) /etc/conf/libhp-ux.a(eeprom.o): eeprom.c $Revision: 1.3.61.24 $ $Date: 95/06/20 07:1 1:46 $ PATCH_9.03 (PHKL_5160) /etc/conf/libhp-ux.a(eisa.o): eisa.c $Revision: 1.3.61.27 $ $Date: 95/07/20 10:54: 29 $ PATCH_9.03 (PHKL_5832) /etc/conf/libhp-ux.a(eisa_sysbrd.o): eisa_sysbrd.c $Date: 95/06/18 19:52:50 $ $Revision: 1.2.61.5 $ PATCH_9.03 (PHKL_5699) /etc/conf/libhp-ux.a(framebuf.o): framebuf.c $Date: 95/06/20 07:16:15 $ $Revision: 1. 14.61.22 $ PATCH_9.03 (PHKL_5699) /etc/conf/libhp-ux.a(graph3.o): graph3.c $Date: 95/06/18 19:45:51 $ $Revision: 1.2. 61.18 $ PATCH_9.03 (PHKL_5699) /etc/conf/libhp-ux.a(hdl_fault.o): hdl_fault.c $Revision: 1.7.61.15 $ $Date: 93/12/07 11:08:03 $ PATCH_9.03 (PHKL_3434) /etc/conf/libhp-ux.a(hdl_init.o): hdl_init.c $Revision: 1.4.61.14 $ $Date: 94/05/1 2 16:07:21 $ PATCH_9.03 (PHKL_4263) /etc/conf/libhp-ux.a(hdl_policy.o): hdl_policy.c $Revision: 1.7.61.33 $ $Date: 96/0 6/25 11:10:12 $ PATCH_9.03 (PHKL_7852) /etc/conf/libhp-ux.a(hdl_trans.o): hdl_trans.c $Revision: 1.7.61.13 $ $Date: 95/06/15 00:30:27 $ PATCH_9.03 (PHKL_5391) /etc/conf/libhp-ux.a(init_sent.o): init_sent.c $Revision: 1.68.61.16 $ $Date: 95/06/2 0 07:10:23 $ PATCH_9.03 (PHKL_5160) /etc/conf/libhp-ux.a(io_subr.o): io_subr.c $Date: 95/06/18 20:43:10 $ $Revision: 1.2 .61.35 $ PATCH_9.03 (PHKL_5699) /etc/conf/libhp-ux.a(kbd_code.o): kbd_code.c $Revision: 1.10.61.28 $ $Date: 94/11/21 14:40:34 $ PATCH_9.03 (PHKL_4959) /etc/conf/libhp-ux.a(kern_exec.o): kern_exec.c $Revision: 1.85.61.24 $ $Date: 96/02/20 12:17:14 $ PATCH_9.03 (PHKL_6760) /etc/conf/libhp-ux.a(locore.o): locore.s $Revision: 1.105.61.32 $ $Date: 95/06/20 07 :06:08 $ PATCH_9.03 (PHKL_5049) /etc/conf/libhp-ux.a(machdep.o): machdep.c $Revision: 1.113.61.28 $ $Date: 96/11/ 15 13:44:22 $ PATCH_9.03 (PHKL_9229) /etc/conf/libhp-ux.a(pdc_rqst.o): pdc_rqst.c $Revision: 1.5.61.15 $ $Date: 95/06/20 07 :06:35 $ PATCH_9.03 (PHKL_5160) /etc/conf/libhp-ux.a(pfail.o): pfail.c $Revision: 1.45.61.10 $ $Date: 95/06/20 07:0 8:57 $ PATCH_9.03 (PHKL_5160) /etc/conf/libhp-ux.a(ps2.o): ps2.c $Revision: 1.2.61.15 $ $Date: 95/06/08 11:02:0 3 $ PATCH_9.03 (PHKL_5656) /etc/conf/libhp-ux.a(s_hil_code.o): s_hil_code.c $Revision: 1.2.61.18 $ $Date: 97/07/09 18:26:09 $ PATCH_9.03 (PHKL_11725) /etc/conf/libhp-ux.a(s_hil_drv.o): s_hil_drv.c $Revision: 1.2.61.13 $ $Date: 95/05/22 1 6:43:10 $ PATCH_9.03 (PHKL_5589) /etc/conf/libhp-ux.a(scsi_c700.o): scsi_c700.c $Revision: 1.2.61.94 $ $Date: 95/06/20 07:12:03 $ PATCH_9.03 (PHKL_5160) /etc/conf/libhp-ux.a(scsi_changer.o): scsi_changer.c $Revision: 1.2.61.15 $ $Date: 95/06/2 0 07:12:17 $ PATCH_9.03 (PHKL_5160) /etc/conf/libhp-ux.a(scsi_ctl.o): scsi_ctl.c $Revision: 1.2.61.88 $ $Date: 95/06/20 07:12:32 $ PATCH_9.03 (PHKL_5160) /etc/conf/libhp-ux.a(scsi_disk.o): scsi_disk.c $Revision: 1.2.61.75 $ $Date: 95/06/20 0 7:12:48 $ PATCH_9.03 (PHKL_5160) /etc/conf/libhp-ux.a(scsi_floppy.o): scsi_floppy.c $Revision: 1.2.61.23 $ $Date: 95/06/2 0 07:13:08 $ PATCH_9.03 (PHKL_5160) /etc/conf/libhp-ux.a(scsi_tape.o): scsi_tape.c $Revision: 1.2.61.32 $ $Date: 95/06/20 07:14:01 $ PATCH_9.03 (PHKL_5518) /etc/conf/libhp-ux.a(snakes_rs232.o): snakes_rs232.c $Revision: 1.3.61.9 $ $Date: 95/06/ 20 07:10:11 $ PATCH_9.03 (PHKL_5160) /etc/conf/libhp-ux.a(stirom.o): stirom.c $Date: 95/06/18 19:47:22 $ $Revision: 1.2. 61.6 $ PATCH_9.03 (PHKL_5699) /etc/conf/libhp-ux.a(subr_prf.o): subr_prf.c $Revision: 1.58.61.9 $ $Date: 95/02/08 1 2:26:05 $ PATCH_9.03 (PHKL_5049) /etc/conf/libhp-ux.a(subr_xxx.o): subr_xxx.c $Date: 95/06/18 19:48:32 $ $Revision: 1. 52.61.16 $ PATCH_9.03 (PHKL_5699) /etc/conf/libhp-ux.a(sys_ki.o): sys_ki.c $Revision: 1.8.61.20 $ $Date: 94/04/2 8 13:35:22 $ PATCH_9.03 (PHKL_4161) /etc/conf/libhp-ux.a(sys_proc.o): sys_proc.c $Revision: 1.45.61.13 $ $Date: 95/08/ 29 08:40:41 $ PATCH_9.03 (PHKL_4500) /etc/conf/libhp-ux.a(vfs_bio.o): vfs_bio.c $Revision: 1.15.61.56 $ $Date: 95/03/1 4 15:30:12 $ PATCH_9.03 (PHKL_5358) /etc/conf/libhp-ux.a(vfs_dev.o): vfs_dev.c $Date: 95/03/15 13:08:34 $ $Revision: 1.9.61.5 $ PATCH_9.03 (PHKL_5348) /etc/conf/libhp-ux.a(vfs_dnlc.o): vfs_dnlc.c $Revision: 1.11.61.7 $ $Date: 94/07/29 16 :25:20 $ PATCH_9.03 (PHKL_4605) /etc/conf/libhp-ux.a(vfs_scalls.o): vfs_scalls.c $Revision: 1.11.61.17 $ $Date: 97/09/0 5 17:06:25 $ PATCH_9.03 (PHKL_12426) /etc/conf/libhp-ux.a(vfs_vm.o): vfs_vm.c $Revision: 1.7.61.44 $ $Date: 96/11/06 10:35:07 $ PATCH_9.03 (PHKL_9149) /etc/conf/libhp-ux.a(vfs_vnode.o): vfs_vnode.c $Revision: 1.8.61.15 $ $Date: 94/04/19 13:54:22 $ PATCH_9.03 (PHKL_4110) /etc/conf/libhp-ux.a(vm_devswap.o): vm_devswap.c $Revision: 1.8.61.20 $ $Date: 94/05/12 16:07:06 $ PATCH_9.03 (PHKL_4263) /etc/conf/libhp-ux.a(vm_fault.o): vm_fault.c $Revision: 1.10.61.22 $ $Date: 93/12/06 17:43:13 $ PATCH_9.03 (PHKL_3434) /etc/conf/libhp-ux.a(vm_kern.o): vm_kern.c $Revision: 1.4.61.11 $ $Date: 93/12/06 14:39:53 $ PATCH_9.03 (PHKL_3434) /etc/conf/libhp-ux.a(vm_machdep.o): vm_machdep.c $Revision: 1.146.61.58 $ $Date: 95/06/ 20 07:09:10 $ PATCH_9.03 (PHKL_5391) /etc/conf/libhp-ux.a(vm_machreg.o): vm_machreg.c $Revision: 1.8.61.19 $ $Date: 94/02/16 13:44:26 $ PATCH_9.03 (PHKL_3795) /etc/conf/libhp-ux.a(vm_mmap.o): vm_mmap.c $Revision: 1.7.61.45 $ $Date: 94/05/12 16:05:24 $ PATCH_9.03 (PHKL_4263) /etc/conf/libhp-ux.a(vm_msem.o): vm_msem.c $Revision: 1.2.61.4 $ $Date: 94/01/09 1 9:07:12 $ PATCH_9.03 (PHKL_3601) /etc/conf/libhp-ux.a(vm_page.o): vm_page.c $Revision: 1.80.61.13 $ $Date: 93/12/06 17:17:38 $ PATCH_9.03 (PHKL_3434) /etc/conf/libhp-ux.a(vm_pdir.o): vm_pdir.c $Revision: 1.8.61.26 $ $Date: 96/02/28 14: 37:41 $ PATCH_9.03 (PHKL_6869) /etc/conf/libhp-ux.a(vm_pregion.o): vm_pregion.c $Revision: 1.8.61.23 $ $Date: 95/06/15 00:29:56 $ PATCH_9.03 (PHKL_5391) /etc/conf/libhp-ux.a(vm_sched.o): vm_sched.c $Revision: 1.48.61.32 $ $Date: 95/06/30 11:17:23 $ PATCH_9.03 (PHKL_5763) /etc/conf/libhp-ux.a(vm_swp.o): vm_swp.c $Revision: 1.42.61.19 $ $Date: 94/04/ 28 13:34:49 $ PATCH_9.03 (PHKL_4161) /etc/conf/libhp-ux.a(vm_text.o): vm_text.c $Revision: 1.49.61.27 $ $Date: 97/01/ 20 09:28:41 $ PATCH_9.03 (PHKL_9868) /etc/conf/libhp-ux.a(vm_vas.o): vm_vas.c $Revision: 1.9.61.18 $ $Date: 95/06/30 02:08:45 $ PATCH_9.03 (PHKL_5747) /etc/conf/libhp-ux.a(vm_vfd.o): vm_vfd.c $Revision: 1.10.61.11 $ $Date: 95/06/30 11:15:51 $ PATCH_9.03 (PHKL_5763) /etc/conf/libhp-ux.a(vsc_config.o): vsc_config.c $Date: 95/06/18 19:40:34 $ $Revision: 1.2.61.38 $ PATCH_9.03 (PHKL_5699) /etc/conf/libhp-ux.a(vsc_ioconf.o): vsc_ioconf.c $Revision: 1.2.61.21 $ $Date: 95/06/20 07:10:00 $ PATCH_9.03 (PHKL_5160) /etc/conf/libnfs.a(klm_lckmgr.o): klm_lckmgr.c $Revision: 1.4.61.7 $ $Date: 95/09/08 11:49:31 $ PATCH_9.03 (PHKL_6050) /etc/conf/libnfs.a(nfs_server.o): nfs_server.c $Revision: 1.14.61.22 $ $Date: 96/02/ 20 12:16:55 $ PATCH_9.03 (PHKL_6760) /etc/conf/libnfs.a(nfs_subr.o): nfs_subr.c $Revision: 1.12.61.14 $ $Date: 96/02/ 20 12:16:26 $ PATCH_9.03 (PHKL_6760) /etc/conf/libnfs.a(nfs_vfsops.o): nfs_vfsops.c $Revision: 1.6.61.19 $ $Date: 94/04/2 8 13:33:15 $ PATCH_9.03 (PHKL_4161) /etc/conf/libnfs.a(nfs_vnops.o): nfs_vnops.c $Revision: 1.15.61.32 $ $Date: 94/07/2 9 16:26:40 $ PATCH_9.03 (PHKL_4605) /etc/conf/libnfs.a(nfs_xdr.o): nfs_xdr.c $Revision: 1.6.61.6 $ $Date: 94/04/11 10:28:42 $ PATCH_9.03 (PHKL_4048) /etc/conf/libnfs.a(nfstest.o): nfstest.c $Revision: 1.4.61.6 $ $Date: 94/04/28 13:33:10 $ PATCH_9.03 (PHKL_4161) /etc/conf/libnfs.a(spec_vnops.o): spec_vnops.c $Date: 95/03/15 13:08:05 $ $Revision: 1.6.61.6 $ PATCH_9.03 (PHKL_5348) /etc/conf/libufs.a(ufs_bmap.o): ufs_bmap.c $Revision: 1.21.61.9 $ $Date: 94/02/16 13:38:30 $ PATCH_9.03 (PHKL_3795) /etc/conf/libufs.a(ufs_dir.o): ufs_dir.c $Revision: 1.10.61.11 $ $Date: 96/02/20 1 2:17:39 $ PATCH_9.03 (PHKL_6760) /etc/conf/libufs.a(ufs_pmount.o): ufs_pmount.c $Revision: 1.4.61.13 $ $Date: 95/01/20 23:15:11 $ PATCH_9.03 (PHKL_4710) /etc/conf/libufs.a(ufs_subr.o): ufs_subr.c $Revision: 1.25.61.9 $ $Date: 93/12/13 16:46:01 $ PATCH_9.03 (PHKL_3505) /etc/conf/libufs.a(ufs_vfsops.o): ufs_vfsops.c $Date: 95/03/15 13:07:42 $ $Revision: 1.11.61.9 $ PATCH_9.03 (PHKL_5348) /etc/conf/libufs.a(ufs_vnops.o): ufs_vnops.c $Revision: 1.18.61.29 $ $Date: 95/03/1 5 13:07:31 $ PATCH_9.03 (PHKL_5348) /etc/conf/machine/eisa.h: eisa.h: $Revision: 1.3.61.13 $ $Date: 95/06/18 19:48 :52 $ eisa.h $Date: 95/06/18 19:48:52 $ $Revision: 1.3.61 .13 $ PATCH_9.03 (PHKL_5699) /etc/conf/machine/pde.h: pde.h: $Revision: 1.24.61.15 $ $Date: 95/06/20 07:08 :43 $ PATCH_9.03 (PHKL_5160) /etc/conf/nfs/nfs_clnt.h: nfs_clnt.h $Revision: 1.8.61.9 $ $Date: 95/08/29 08:42:07 $ PATCH_9.03 (PHKL_4161) 10.1 /usr/include/machine/pde.h: pde.h: $Revision: 1.24.61.15 $ $Date: 95/06/20 07:08 :43 $ PATCH_9.03 (PHKL_5160) /usr/include/nfs/nfs_clnt.h: nfs_clnt.h $Revision: 1.8.61.9 $ $Date: 95/08/29 08:42:07 $ PATCH_9.03 (PHKL_4161) 10.1 /usr/include/sys/audio.h: audio.h $Date: 95/08/28 16:12:24 $ $Revision: 1 .3.61.16 $ PATCH_9.03 (PHKL_4959) /usr/include/sys/eisa.h: eisa.h: $Revision: 1.3.61.13 $ $Date: 95/06/18 19:48 :52 $ eisa.h $Date: 95/06/18 19:48:52 $ $Revision: 1.3.61 .13 $ PATCH_9.03 (PHKL_5699) sum(1) Output: 12442 3 /etc/conf/graf.800/frameb_spc.h 15682 6 /etc/conf/graf.800/graph3.h 28789 33 /etc/conf/graf.800/stirom.h 65289 10 /etc/conf/graf/gpu_data.h 32155 42 /etc/conf/graf/ite.h 11418 13 /etc/conf/libdskless.a(dux_exec.o) 23848 25 /etc/conf/libdskless.a(dux_lookup.o) 48429 32 /etc/conf/libdskless.a(dux_mount.o) 38836 45 /etc/conf/libdskless.a(dux_vnops.o) 51238 22 /etc/conf/libhp-ux.a(asm_vm.o) 53880 74 /etc/conf/libhp-ux.a(audio.o) 14437 158 /etc/conf/libhp-ux.a(autoch.o) 7139 7 /etc/conf/libhp-ux.a(beep.o) 40722 8 /etc/conf/libhp-ux.a(bootpath.o) 13270 25 /etc/conf/libhp-ux.a(dconfig.o) 13479 16 /etc/conf/libhp-ux.a(diag1.o) 36347 28 /etc/conf/libhp-ux.a(eeprom.o) 21802 56 /etc/conf/libhp-ux.a(eisa.o) 20514 4 /etc/conf/libhp-ux.a(eisa_sysbrd.o) 5884 28 /etc/conf/libhp-ux.a(framebuf.o) 11760 42 /etc/conf/libhp-ux.a(graph3.o) 12889 18 /etc/conf/libhp-ux.a(hdl_fault.o) 58483 9 /etc/conf/libhp-ux.a(hdl_init.o) 29050 21 /etc/conf/libhp-ux.a(hdl_policy.o) 26596 15 /etc/conf/libhp-ux.a(hdl_trans.o) 25671 34 /etc/conf/libhp-ux.a(init_sent.o) 27889 38 /etc/conf/libhp-ux.a(io_subr.o) 57666 27 /etc/conf/libhp-ux.a(kbd_code.o) 25499 23 /etc/conf/libhp-ux.a(kern_exec.o) 22560 109 /etc/conf/libhp-ux.a(locore.o) 21443 57 /etc/conf/libhp-ux.a(machdep.o) 47204 11 /etc/conf/libhp-ux.a(pdc_rqst.o) 31167 13 /etc/conf/libhp-ux.a(pfail.o) 5353 46 /etc/conf/libhp-ux.a(ps2.o) 29641 24 /etc/conf/libhp-ux.a(s_hil_code.o) 41987 23 /etc/conf/libhp-ux.a(s_hil_drv.o) 7489 206 /etc/conf/libhp-ux.a(scsi_c700.o) 4942 29 /etc/conf/libhp-ux.a(scsi_changer.o) 4416 142 /etc/conf/libhp-ux.a(scsi_ctl.o) 57327 58 /etc/conf/libhp-ux.a(scsi_disk.o) 65526 53 /etc/conf/libhp-ux.a(scsi_floppy.o) 3066 97 /etc/conf/libhp-ux.a(scsi_tape.o) 52160 12 /etc/conf/libhp-ux.a(snakes_rs232.o) 38477 12 /etc/conf/libhp-ux.a(stirom.o) 48705 27 /etc/conf/libhp-ux.a(subr_prf.o) 24272 25 /etc/conf/libhp-ux.a(subr_xxx.o) 15875 48 /etc/conf/libhp-ux.a(sys_ki.o) 38794 20 /etc/conf/libhp-ux.a(sys_proc.o) 39231 57 /etc/conf/libhp-ux.a(vfs_bio.o) 27400 16 /etc/conf/libhp-ux.a(vfs_dev.o) 37742 12 /etc/conf/libhp-ux.a(vfs_dnlc.o) 65493 33 /etc/conf/libhp-ux.a(vfs_scalls.o) 37236 52 /etc/conf/libhp-ux.a(vfs_vm.o) 44415 15 /etc/conf/libhp-ux.a(vfs_vnode.o) 49564 23 /etc/conf/libhp-ux.a(vm_devswap.o) 62861 19 /etc/conf/libhp-ux.a(vm_fault.o) 5551 12 /etc/conf/libhp-ux.a(vm_kern.o) 33473 103 /etc/conf/libhp-ux.a(vm_machdep.o) 47045 22 /etc/conf/libhp-ux.a(vm_machreg.o) 43786 33 /etc/conf/libhp-ux.a(vm_mmap.o) 56340 15 /etc/conf/libhp-ux.a(vm_msem.o) 20207 23 /etc/conf/libhp-ux.a(vm_page.o) 39962 33 /etc/conf/libhp-ux.a(vm_pdir.o) 49631 23 /etc/conf/libhp-ux.a(vm_pregion.o) 6416 31 /etc/conf/libhp-ux.a(vm_sched.o) 43083 13 /etc/conf/libhp-ux.a(vm_swp.o) 22340 30 /etc/conf/libhp-ux.a(vm_text.o) 42109 24 /etc/conf/libhp-ux.a(vm_vas.o) 62427 26 /etc/conf/libhp-ux.a(vm_vfd.o) 20736 37 /etc/conf/libhp-ux.a(vsc_config.o) 25727 14 /etc/conf/libhp-ux.a(vsc_ioconf.o) 34754 11 /etc/conf/libnfs.a(klm_lckmgr.o) 31508 51 /etc/conf/libnfs.a(nfs_server.o) 11323 29 /etc/conf/libnfs.a(nfs_subr.o) 26220 16 /etc/conf/libnfs.a(nfs_vfsops.o) 4951 51 /etc/conf/libnfs.a(nfs_vnops.o) 56442 19 /etc/conf/libnfs.a(nfs_xdr.o) 12768 7 /etc/conf/libnfs.a(nfstest.o) 31537 17 /etc/conf/libnfs.a(spec_vnops.o) 10454 10 /etc/conf/libufs.a(ufs_bmap.o) 37260 34 /etc/conf/libufs.a(ufs_dir.o) 62800 8 /etc/conf/libufs.a(ufs_pmount.o) 35509 18 /etc/conf/libufs.a(ufs_subr.o) 63370 22 /etc/conf/libufs.a(ufs_vfsops.o) 31255 56 /etc/conf/libufs.a(ufs_vnops.o) 30277 47 /etc/conf/machine/eisa.h 30673 20 /etc/conf/machine/pde.h 54220 7 /etc/conf/nfs/nfs_clnt.h 30673 20 /usr/include/machine/pde.h 54220 7 /usr/include/nfs/nfs_clnt.h 22237 49 /usr/include/sys/audio.h 30277 47 /usr/include/sys/eisa.h Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHKL_3217 PHKL_3289 PHKL_3290 PHKL_3361 PHKL_3394 PHKL_3421 PHKL_3422 PHKL_3434 PHKL_3472 PHKL_3505 PHKL_3507 PHKL_3561 PHKL_3572 PHKL_3578 PHKL_3600 PHKL_3601 PHKL_3602 PHKL_3617 PHKL_3620 PHKL_3621 PHKL_3756 PHKL_3791 PHKL_3795 PHKL_3798 PHKL_3913 PHKL_3929 PHKL_3940 PHKL_3975 PHKL_3986 PHKL_3992 PHKL_4029 PHKL_4048 PHKL_4054 PHKL_4099 PHKL_4110 PHKL_4158 PHKL_4161 PHKL_4174 PHKL_4226 PHKL_4247 PHKL_4263 PHKL_4268 PHKL_4323 PHKL_4324 PHKL_4500 PHKL_4605 PHKL_4676 PHKL_4710 PHKL_4777 PHKL_4895 PHKL_4937 PHKL_4943 PHKL_4959 PHKL_5049 PHKL_5076 PHKL_5137 PHKL_5160 PHKL_5165 PHKL_5348 PHKL_5358 PHKL_5391 PHKL_5518 PHKL_5536 PHKL_5589 PHKL_5656 PHKL_5699 PHKL_5747 PHKL_5763 PHKL_5832 PHKL_5994 PHKL_6050 PHKL_6760 PHKL_6869 PHKL_7852 PHKL_9149 PHKL_9229 PHKL_9868 PHKL_10222 PHKL_11725 Equivalent Patches: None Patch Package Size: 1620 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. Copy the patch to your /tmp directory and unshar it: cd /tmp cp patch_source/PHKL_12426 . sh PHKL_12426 3. Become root and run update: /etc/update [-r [kernel_gen_file]] -s \ /tmp/PHKL_12426.updt PHKL_12426 Update moves the original software to /system/PHKL_12426/orig. Keep this file to recover from any potential problems. You should move the .text file to /system/PHKL_12426 for future reference. To put this patch on a magnetic tape and update from the tape drive, use dd: dd if=PHKL_12426.updt of=/dev/rmt/0m bs=2048 Special Installation Instructions: None