Dear Caldera Customer, Support Level Supplement (SLS) ptf4037d, the SCO UnixWare 2.1.3 fdisk and sd01, svc and sysdump Driver Update, addresses all of the issues listed below. SLS ptf4037b addressed these issues: 1. The time that the kernel spent processing interrupts was counted as idle time instead of system time. This would cause the output of monitoring programs such as rtpm(1) to be inaccurate (particularly on a heavily-loaded system that processes many interrupts). 2. The system could panic during shutdown with the message "Unknown trap type 0x00000201 in kernel mode" if an unexpected interrupt 15 was received. This reserved interrupt could be generated by certain hardware (for example, a network card). Correct behavior is for the system to catch the interrupt, print a warning message, and continue the shutdown. SLS ptf4037c addressed this issue: 3. The system fails to complete a sysdump during a panic. SLS ptf4037c also supersedes SLS ptf3363 for UnixWare 2.1.3 systems. This includes fixes for the following issues which were previously addressed in SLS ptf3363: 4. fdisk failed with disks larger than 64GB. SLS ptf3363 allowed UnixWare to work with disks greater than the 64GB limitation, and the maximum partition size handled by fdisk is now 2 terabytes. Note: This changes the size of the maximum disk that fdisk can deal with. It does not change the maximum filesystem size, which is still 2GB. 5. Systems running the Online Data Manager (ODM) software on configurations with encapsulated, mirrored root disks sometimes hang during a panic. 6. Possible data corruption occurs when running heavy disk-intensive i/o. 7. A memory leak occurs in the 56-, 512- or 1982-byte kma pool as seen by sar(1M) and rtpm(1M). 8. Messages appear in the osmlog file recording failures of the fork() or exec() system calls due to a shortage of kernel memory. 9. The prtvtoc(1M) command fails to complete. SLS ptf4037d additionally addresses these issues: 10. On a system with large memory (1GB or more) and having SYSDUMP_SELECTIVE enabled (which is the default), there is a problem to generate a forced dump. The system starts to display 5 "." and then seems to hang for around 20-30 minutes (depending on the number of pages in the page table) then after it dumps the rest OK. (If you disable SYSDUMP_SELECTIVE on the kernel, the system is able to dump fine). 11. Panic in the timeout code on KMA consistency check. SLS ptf4037d contains these files: /etc/conf/pack.d/sd01/Driver.o /etc/conf/pack.d/svc/Driver_atup.o /etc/conf/pack.d/svc/Driver_mp.o /etc/conf/pack.d/sysdump/Driver_atup.o /etc/conf/pack.d/sysdump/Driver_mp.o /usr/lib/drf/fdisk.boot /usr/sbin/diskformat /usr/sbin/disksetup /usr/sbin/edvtoc /usr/sbin/fdisk /usr/sbin/prtconf /usr/sbin/prtvtoc Software Notes and Recommendations ---------------------------------- SLS ptf4037d should only be installed on: SCO UnixWare Application Server Release 2.1.3 SCO UnixWare Personal Edition Release 2.1.3 SLS ptf4037d depends upon SLS ptf4047e. SLS ptf4047e must be installed before the installation of SLS ptf4037d. SLS ptf4037d supersedes SLS ptf3363; however, it is not necessary to remove SLS ptf3363 before installing SLS ptf4037d. Installation Instructions ------------------------- 1. Download the ptf4037d.Z file to the /tmp directory on your machine. 2. As root, uncompress the file and add the package to your system using these commands: $ su Password: # uncompress /tmp/ptf4037d.Z # pkgadd -d /tmp/ptf4037d # rm /tmp/ptf4037d 3. Reboot the system after installing this SLS package. The release notes displayed prior to installation can be found in: /var/sadm/pkg/ptf4037/install/ptf4037.txt Removal Instructions -------------------- 1. As root, remove the package using these commands: $ su Password: # pkgrm ptf4037 2. Reboot the system after removing this package. If you have questions regarding this SLS, or the product on which it is installed, please contact your software supplier.