Patch Name: PHNE_5903 Patch Description: s700_800 10.00 cumulative kernel patch for Telnet Creation Date: 95/11/03 Post Date: 95/12/01 Hardware Platforms - OS Releases: s700: 10.00 s800: 10.00 Products: N/A Filesets: Networking.NET-KRN Automatic Reboot?: Yes Status: General Release Critical: Yes PHNE_5903: PANIC CORRUPTION ABORT PHNE_5201: PANIC Path Name: /hp-ux_patches/s700_800/10.X/PHNE_5903 Symptoms: PHNE_5903: The following symptoms correspond to the descriptions in the defect descriptions field for PHNE_5903: 1. The system will panic with an error message of: panic: (display==0xbe00, flags==0x0) sbdrop The stack will show sbdrop and nvs_input on the top. 2. The system will panic with an error message of: panic: (display==0xbe00, flags==0x0) m_free: freeing free mbuf The stack will show m_free and soreceive on the top. 3. The system will panic with an error message of: panic: (display==0xbe00, flags==0x0) receive 1 The stack will show soreceive and recvit on the top. 4. The kernel portion of the Telnet server drops data on other connections while attempting to receive data from its own Telnet client. 5. The kernel portion of the Telnet server puts data in the wrong order while sending it to the Telnet client. 6. The kernel portion of the Telnet server drops connections with a log message of: nvs_telnet (normal): ioctl(SIOCJNVS): Device busy or a log message of: nvs_telnet (output only): ioctl(SIOCJNVS): Device busy 7. The kernel portion of the Telnet server is slow handling binary input from the Telnet client. PHNE_5201: The following symptoms correspond to the descriptions in the defect descriptions field for PHNE_5201: 1. The system will panic with an error message of: panic: (display==0xba00, flags==0x0) sbdrop The stack will show sbdrop and nvs_input on the top. Defect Description: PHNE_5903: The following defect descriptions are for PHNE_5903: 1. The problem is that two instances of nvs_input are executing at the same time and thus attempting socket buffer data drops (sbdrop) at the same time. This can happen any time data arrives from the Telnet client as the kernel portion of the Telnet server is being started for that connection. NOTE: The problem was not completely corrected by PHNE_5201 because that patch synchronized nvs_input execution without using a semaphore. Thus, the possibility still existed that two instances of nvs_input could execute at the same time and cause the same problem. 2. The problem is that an instance of nvs_input and an instance of soreceive are executing at the same time and thus attempting socket buffer frees (m_free) at the same time. This can happen any time data has been queued for the Telnet server as the kernel portion of the Telnet server is being stopped for that connection. 3. The problem is that two instances of nvs_input are executing at the same time or an instance of nvs_input and an instance of soreceive are executing at the same time and one of the functions is attempting socket buffer drops (sbdrop) or frees (m_free) on socket buffers that belong to other connections. 4. The problem is that two instances of nvs_input are executing at the same time or an instance of nvs_input and an instance of soreceive are executing at the same time and one of the functions is attempting socket buffer drops (sbdrop) or frees (m_free) on socket buffers that belong to other connections. 5. The problem is that two instances of nvs_output are executing at the same time and thus attempting to send data to the Telnet client at the same time. This can happen any time data arrives from the application as the kernel portion of the Telnet server is being started for that connection. 6. The problem is that data has been queued for the Telnet server as the kernel portion of the Telnet server is being started for that connection. This causes the Telnet server to assume that the connection is already in use by another instance of a Telnet server and to thus drop the connection. 7. The problem is that the kernel portion of the Telnet server is being stopped with each IAC data character encountered in binary input from the Telnet client. This causes control to be passed to the user space portion of the Telnet server even though an IAC data character can be processed in the kernel portion of the Telnet server. PHNE_5201: The following defect descriptions are for PHNE_5201: 1. The problem is that two instances of nvs_input are executing at the same time and thus attempting socket buffer data drops (sbdrop) at the same time. This can happen any time data arrives from the Telnet client as the kernel portion of the Telnet server is being started for that connection. SR: 1653146472 5000713271 4701281899 Patch Files: /usr/conf/lib/libinet.a(tty_nvs.o) /usr/conf/lib/libinet.a(nvsisr.o) what(1) Output: /usr/conf/lib/libinet.a(tty_nvs.o): tty_nvs.c $Date: 95/11/03 16:00:07 $ $Revision: 1.3.110.9 $ PHNE_5903 FILESET NETIPC: lib nipc: Version: A.09.00 FILESET NETINET: lib inet: Version: A.10.00 /usr/conf/lib/libinet.a(nvsisr.o): nvsisr.c $Revision: 1.1.110.5 $ $Date: 95/11/03 13:0 0:58 $ PHNE_5903 FILESET NETIPC: lib nipc: Version: A.09.00 FILESET NETINET: lib inet: Version: A.10.00 cksum(1) Output: 6544465 8320 /usr/conf/lib/libinet.a(tty_nvs.o) 2417943135 5728 /usr/conf/lib/libinet.a(nvsisr.o) Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHNE_5201 Equivalent Patches: PHNE_5977: s700: 10.01 s800: 10.01 PHNE_6378: s700: 10.10 s800: 10.10 Patch Package Size: 70 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_5903 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHNE_5903.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_5903.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. The cluster clients must be shut down as described in step 5b. By default swinstall will archive the original software in /var/adm/sw/patch/PHNE_5903. 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_5903.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_5903.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: None