The latest variant for RTU 6.2 is Variant 32. ================================================================================ RT-9000 Version 6.2V32 Release Notes January 8, 1998 1. What's In This Kit The RT-9000 version 6.2V32 kit includes the following items: 1. One 1/4-inch cartridge tape: Qty Label 1 RT-9000 V6.2V32 2. These release notes. 2. Overview of Features RT-9000 Version 6.2V32 is a variant of RTU 6.2 and RTU 6.2B that exists only for RT-9000 platforms. The 6.2V32 release is intended to correct the following problems: o The jerky behavior or slow execution of X applications displaying over the net has been fixed. o Two new kernel configuration parameters (vba_nmap1 and vba_nmap2) have been added. These parameters can be assigned a value ranging from 100 to 4096, and will dictate the number of resource map entries. Increasing the resource map size will reduce the memory available to the system. (SCR 6866) o Situations which could cause a "duplicate soo_close" panic or could lead to kernel segmentation faults related to premature socket closure have been eliminated. (SCR 6803) o Conditions permitting astpause(2) to time out and to return to user space without delivering a pendng ast have been eliminated. (SCR 7034) o Running rt-90sps or mpadvise(MPA_CLK_SET) operations on CPU 4 will no longer cause CPU 4 processes to hang. (SCR 6860) RT-9000 Version 6.2V32 Release Notes Page 1 o A system hang, sometimes caused by simultaneous, multiple attempts to change a process' pgrp, no longer occurs. (SCR 7053) o Improved receive latency in lnexos driver by using a dedicated lightweight process. (SCR 6995) o Rescheduling interrupts are less likely to be ignored. (SCR 7057) o Kernel segmentation faults which could occur when running a threaded program under dbx(1) or by sending stop or continue signals to a threaded program have been eliminated. (SCRs 6925, SCR 7064) o Systems with more than 384 MB of physical memory will now boot properly. Panics on SCSI device timeouts have been eliminated; the timeout message appearing on the console is now advisory. (SCR 7105, SCR 7096) An updated man page for mt, reflecting this change, has been attached to these Release Notes for your convenience. o A known problem exists where device numbers greater than 127 cannot be used. As a work around, the following major device numbers have been freed up for use by customers on the 9000 Series machines. Block devices: 64 through 126 Character devices: 6, 9, 11 through 16, 19, 22, 24, 29 through 34, 36 through 37, 48, 54 through 56, 60, 66, 74 through 78, 110 through 126. o Concurrent use of non-symmetric drivers no longer causes the system to hang. A common case of this was suspending and resuming operations to a tape in conjunction with a cpio command. Fixed segment fault in strwsrv routine. (SCR 7101) Process hangs related to the use of punlock(2) or its derivatives plock(3) and rtplock(3) have been eliminated. (SCR 7042) RT-9000 Version 6.2V32 Release Notes Page 2 o Asts are no longer lost when an uninitialized X connection is closed (e.g. when certain XOpenDisplay(3x) failure occures. (SCR 7141, SCR 7148) o Fixed various race conditions affecting the state of a TCP transport endpoint. (SCR 7104) Fixed various tcp state machine problems that could leave a tcp connection in CLOSE_WAIT state and therefore prevent the same server process from being started as it says "Address already in use". (SCR 6843) Fixed various race conditions causing sendto()/connect() to return errno of EPROTO. (SCR 7157) o A driver dependent problem with restarting an interrupted read(2) or write(2) to slow devices has been found and corrected. (SCR 7170) The sdad SCSI driver will now allow the use of a 3.5" floppy drive. (SCR 7110) Externally mapped memory references included in disk or tape I/O, ,while not supported in RTU 6.2, will no longer panic the system. This panic previously occurred on some ada coredumps. (SCR 7172) o A potential race condition and points of contention in swap management have been eliminated. The swap algorithm's dependency on the "fast heap" has been greatly reduced. (SCR 7188) o Fixed the problem with appending to a NFS mounted file. (SCR 7202) The problem where the Real Time dedicated processes could hang if they disable all processor interrupts and perform serialized system calls has been fixed. (SCR 7182) The phone number listed in the licensing software for customers outside the US to call Oceanport, NJ has been changed to the correct number. (SCR 7208) RT-9000 Version 6.2V32 Release Notes Page 3 o The make(1) command now supports filenames longer than fourteen characters, which may exist on xfs filesystem. (SCR 7213) o The problem with possible boot up hang for systems with four MN-808s have been fixed. (SCR 7187) Fixed the file ownership and group of some files which were set incorrectly during the installation of RTU 6.2. (SCR 6957) o When a UNIX socket is closed, a read at the other end of the socket would incorrectly return an error (EIO). This fix ensures that a read in these circumstances returns 0, indicating that the other end has disconnected. (SCR 7308) o Fixed the kernel panic due to Access Violation in ucbsig. (SCR 7255) o Fixed ls(1) to handle long filename (for xfs filesystem) correctly when meta character is given from the command line. (SCR 7248) o Fixed potential system panics caused by corruption of streams service queue. Fixed potential SRAM corruption causing a crash in the ie driver. Fixed deadlock situation caused by using ctrl-O. (SCR 7099) o Corrected INTMAP configurable to ignore interrupt levels that are not redirected to another CPU. (SCR 7425) Disable broadcast interrupts as a workaround for a hardware problem where the address output during a VME IACK cycle may be interpreted as a request for a broadcast interrupt. (SCR 7450) o Fixed SCSI Tape Driver so that it will not return I/O error on partial read or partial write when EOM is encountered. This will correct the problems to restoring data from multi-volume cpio tapes. (SCR 7114 and SCR 7323) RT-9000 Version 6.2V32 Release Notes Page 4 o Fixed sockets to prevent ioctl's going downstream on all socket calls. (SCR 7181) Fixed MP and parameter validation socket problems for send, sendmsg, and sendto. (SCR 7183) Allow the processing of closure of lingering sockets in TCP. (SCR 7462) o Fixes the problem of getting inter processor interrupt on a busy Real-Time processor. (SCR 7595) o Prevents corruption of integral ethernet SRAM by the Intel 82596. o Fixes 'tar' to return error when the tape can not be written either because of no tape or write protected tape. (SCR 7594) o A process being paged in would cause ipirs to be sent to realtime processes. This mechanism has been changed, allowing hardware coherency to flush any impacted cache lines. Fixes the problem that the process table initialization routine was not clearing the cpu history field p_cpumapped. (SCR 7661) o Fixes sdad driver, so that 1st access to floppy drive does not fail. (SCR 7571) o Fixes deadlock in TCP code. (SCR 7659) o Fixed year 2000 and beyond date problems. o The problem of direct I/O operations on small files has been fixed. (SAR HM12099) 3. Prerequisites This kit is only to be loaded onto 9000 Series machines running 6.2, 6.2B, or 6.2 Variant versions of the RTU operating system. If you are installing RTU Version 6.2V32 on a running system you will need approximately 20,000 disk blocks on your system ("/") partition before you begin installing RTU Version 6.2V32 on top of RT-9000 Version 6.2V32 Release Notes Page 5 your current installation. RT-9000 Version 6.2V32 Release Notes Page 6 4. Installation Procedure ** Read these release notes in their entirety before installing RT-9000 6.2V32.** To install the RT-9000 6.2V32 software kit, perform the following steps: 1. Login as root. 2. The /update directory, used to hold files from the cpio image previous to installation, must be empty. Change directory to /update and remove all the files and directories you find there. 3. Reboot to single-user mode using /etc/reboot: # /etc/reboot -s 4. Make sure you are in the AT&T universe: # universe att 5. Make sure your current directory is root: # cd / 6. Place the RT-9000 6.2V32 tape into the drive and read it: # cpio -ivmCdu < /dev/rctp 7. Run the 6.2V32 software installation script: # /install/i_rtu_6.2V Successful installation will be indicated by the finished installation message of the install script. Original copies of certain files modified by the installation script are saved in the directory /PRE_RTU_6.2V. To save space after the installation, you may remove this directory. RT-9000 Version 6.2V32 Release Notes Page 7 5. Notes o Swap Space If your Maxion system is used for software development, particularly for large applications, the default swap space should equal 1 to 1.5 times the amount of physical memory. If you need to add more swap space see Configuring Multiple Swap Files in the System Administrator's Guide Maxion Supplement and Swap File Changes in the System Admin Guide. o Crashdumps Systems equipped with 4 x 128 MB of memory must always use 5 GB tape cartridges for full crashdumps. Theoretically 4 x 128 or 512 MB should fit on a 525 MB cartridge tape, but some 525 MB cartridge tapes (depending on quality and/or media condition) will not store sufficient data for the crashdump. Systems with 4 x 128 MB memory and 525 MB cartridge tape should take selective dumps to disk. o Interrupted read(2) or write(2) A driver dependent problem with restarting an interrupted read(2) or write(2) to a slow device has been found and corrected. When an application is either compiled in the UCB universe or using ASTs, interrupted reads and writes to slow devices should, if no characters have been transfered, automatically restart after processing the interrupting signal/AST. For some type of device drivers, however, it has been found that the read/write system call incorrectly returned EINTR rather than restarting. The VS-16M serial line mux is known to have exhibited this problem. Though this problem is now fixed when accessing devices through device nodes located on an RTU file system, this problem may still exist when accessing devices nodes on an XFS file system. For this reason it is not recommended, unless specifically addressed in XFS release notes, that RT-9000 Version 6.2V32 Release Notes Page 8 character special device nodes be placed on XFS file systems. RT-9000 Version 6.2V32 Release Notes Page 9 CONTENTS 1. What's In This Kit............................................. 1 2. Overview of Features........................................... 1 3. Prerequisites.................................................. 5 4. Installation Procedure......................................... 7 5. Notes.......................................................... 8 RT-9000 Version 6.2V32 Release Notes Page i