Patch Name: PHNE_10585 Patch Description: s700_800 10.10 Cumulative Mux and Pty Patch Creation Date: 97/03/26 Post Date: 97/05/03 Hardware Platforms - OS Releases: s700: 10.10 s800: 10.10 Products: N/A Filesets: OS-Core.CORE-KRN OS-Core.UX-CORE Automatic Reboot?: Yes Status: General Superseded Critical: No (superseded patches were critical) PHNE_8414: CORRUPTION PHNE_7600: HANG PHNE_6317: PANIC CORRUPTION Path Name: /hp-ux_patches/s700_800/10.X/PHNE_10585 Symptoms: PHNE_10585: VTIME parameter is not working correctly when asynchronous I/O is enabled - SIGIO is not being generated. PHNE_9741: RTS/CTS hardware flow control signals are not reset when a direct port is closed. PHNE_9437: 1 Console output suspended leading to possible hung system. 2 A delay in character processing is observed when EOF characters are received while the terminal is in canonical mode and then switches to raw mode. PHNE_8414: Data loss observed when using block mode termio over a telnet connection. PHNE_7600: 1 System appears hung while running telnet sessions. 2 Data loss on K-series built in mux ports. PHNE_6317: 1 Tty device read hang 2 An increased number of Ierrs and Oerrs seen from a 'netstat -i' command after simultaneous heavy mux traffic and any lan traffic indicating poor lan performance. 3 Data page fault in nvs_callout(). 4 Erroneous FLT chassis code displayed on console status line. 5 Data overruns detected on K-series built in mux ports (also seen as data loss). 6 Fixes a problem where TTY output data may not be transmitted if data is queued up for transmission when close of the port occurs. 7. Fixes a panic problem where the pty driver attempts to copy more data to the ioctl argument buffer than what the file system has allocated for. Defect Description: PHNE_10585: VTIME parameter is not working correctly when asynchronous I/O is enabled - SIGIO is not being generated. PHNE_9741: RTS/CTS hardware flow control signals are not reset when a direct port is closed. PHNE_9437: 1 Console output suspended leading to possible hung system. This defect only occurs on systems where the console device is sending abnormally large amounts for flow control characters (XON & XOFF) to the console port. The Eliko LCD terminal is one such device. Another was a PC running an application that sent many flow control characters regardless of output flow. This defect should not be experienced by the vast majority of users. 2 A delay in character processing is observed when EOF characters are received while the terminal is in canonical mode and then switches to raw mode. PHNE_8414: Data loss observed when using block mode termio over a telnet connection. PHNE_7600: 1 System appears hung while running telnet sessions. Telnet in infinite loop because pty (line discipline) falsely indicates that data is available. 2 Data loss on K-series built in mux ports. Data loss may occur on built in mux ports when no flow control is used, data is being received, and the key switch is turned to either enable or disable the AP functionality. PHNE_6317: 1 Tty device read hangs - mostly seen from getty, hang at login prompt. 2 There is a known problem involving the built-in lan port and the NIO muxes and EISA muxes, due to traffic levels on the GSC/HSC bus. This problem results in outgoing packets on the built-in 802.3 lan port being cut off, and incoming packets being dropped. If an increased number Ierrs and Oerrs are seen in 'netstat -i' command output after heavy mux traffic, this problem should be suspected and this patch installed. 3 Data page fault in nvs_callout() while running telnet. 4 Erroneous FLT chassis code displayed on consoles attached to A1703-60022 console muxes. 5 On K-series built in mux ports, input data overruns were generated when no input flow control was being used. For programs that do not check for parity and framing errors this could appear as lost data. 6 Fixes a problem where TTY output data may not be transmitted if data is queued up for transmission when close of the port occurs. 7. Fixes a panic problem where the pty driver attempts to copy more data to the ioctl argument buffer than what the file system has allocated for. This was caused by a race condition between the master closing and slave ioctl trapping. SR: 1653207795 5003346031 1653189472 1653182519 4701339457 5003332551 5003321349 5000715284 4701310854 1653153759 4701308080 4701308122 4701306522 5000711184 4701313080 Patch Files: /usr/conf/lib/libhp-ux.a(hptt0.o) /usr/conf/lib/libhp-ux.a(mux2.o) /usr/conf/lib/libhp-ux.a(mux3.o) /usr/conf/lib/libhp-ux.a(tty_pty.o) /sbin/lib/NMUX16.FW /sbin/lib/NIAPMUX.FW what(1) Output: /usr/conf/lib/libhp-ux.a(hptt0.o): PATCH_10.10: hptt0.o 1.8.102.13 97/03/26 PHNE_1058 5 /usr/conf/lib/libhp-ux.a(mux2.o): PATCH_10.10: mux2.o 1.7.102.6 97/01/07 PHNE_9741 /usr/conf/lib/libhp-ux.a(mux3.o): PATCH_10.10: mux3.o 1.4.102.2 96/12/04 PHNE_9437 /usr/conf/lib/libhp-ux.a(tty_pty.o): PATCH_10.10: tty_pty.o 1.12.102.7 96/02/16 PHNE_6 317 /sbin/lib/NMUX16.FW: NMUX.download; Rev: 02.30 Date: 95/12/13 /sbin/lib/NIAPMUX.FW: NMUX.download; Rev: 01.40 Date: 96/03/18 cksum(1) Output: 2982919497 42876 /usr/conf/lib/libhp-ux.a(hptt0.o) 2207247375 59656 /usr/conf/lib/libhp-ux.a(mux2.o) 1411923173 12328 /usr/conf/lib/libhp-ux.a(mux3.o) 1616935220 26440 /usr/conf/lib/libhp-ux.a(tty_pty.o) 2868079491 139295 /sbin/lib/NMUX16.FW 1585300595 143429 /sbin/lib/NIAPMUX.FW Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHNE_6317 PHNE_7600 PHNE_8414 PHNE_9437 PHNE_9741 Equivalent Patches: None Patch Package Size: 480 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 PHNE_10585 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHNE_10585.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/PHNE_10585.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/PHNE_10585. 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 PHNE_10585.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/PHNE_10585.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: For S700 patch installations ignore swinstall warnings about the following files - mux2.o, mux3.o, NMUX16.FW, NIAPMUX.FW