Patch-ID# 109715-16 Keywords: driver hsip panic, netra ft 1800 u4ft mtu/mru modem rts/dtr hsip_loop Synopsis: SunHSI/P 3.0: HSIP driver, test hardness, multiboard, loopback Date: Aug/31/2004 Install Requirements: Reboot after installation Solaris Release: 8 9 SunOS Release: 5.8 5.9 Unbundled Product: High Speed Serial Interface HSI/P Unbundled Release: 3.0 Xref: Topic: Relevant Architectures: sparc BugId's fixed with this patch: 4347266 4360574 4365776 4386387 4458402 4496362 4617096 4652929 4696699 4701939 4724279 4797381 4833594 4916727 5013450 Changes incorporated in this version: 5013450 Patches accumulated and obsoleted by this patch: Patches which conflict with this patch: Patches required with this patch: Obsoleted by: Files included with this patch: /kernel/drv/HSIP /kernel/drv/HSIP.conf /kernel/drv/sparcv9/HSIP /opt/SUNWconn/HSIP/bin/hsip_dump /opt/SUNWconn/HSIP/bin/hsip_dump_it /opt/SUNWconn/HSIP/bin/hsip_init /opt/SUNWconn/HSIP/bin/hsip_loop /opt/SUNWconn/HSIP/man/man7d/hsip.7d /opt/SUNWconn/bin/hsip_dump /opt/SUNWconn/bin/hsip_dump_it Problem Description: 5013450 All hsip transmissions pause if one link is stopped when data is buffered (from 109715-15) 5013450 All hsip transmissions pause if one link is stopped when data is buffered (from 109715-14) 4916727 Canput failure dma2 (from 109715-13) 4833594 HSI patch 109715-11 causes errors and warnings when running traffic (from 109715-12) 4797381 in case of Kernel Memory exhaustion x25 links goes down (from 109715-11) 4696699 HSIP depends on qprocsareon() 4496362 can't do cpu dr with hsi/p drivers loaded (from 109715-10) 4724279 panic in freebs after canputnext failure. (from 109715-09) 4701939 SunHSI_PCI_3.0 package fails Safe Default Permissions (from 109715-08) 4652929 HSI/P links fail due to receive overun errors. (from 109715-07) 4617096 Problem with hsi/p 2.0, need debug driver. (from 109715-06) (from 109715-05) 4458402 HSI serial card intermittenly panics on "cfgadm disconnect" call from console (from 109715-04) (from 109715-03) (from 109715-02) 4365776 system is panic on using PAD 4360574 HSIP watchdog continues to check_access once the driver has failed 4386387 Installation of HSI/P 3.0 packages causes Starcat to panic (from 109715-01) 4347266 System panics with HSI Patch Installation Instructions: -------------------------------- For Solaris 2.0 - 2.6 releases, refer to the Install.info file and/or the README within the patch for instructions on using the generic 'installpatch' and 'backoutpatch' scripts provided with each patch. For Solaris 7 and 8 releases, refer to the man pages for instructions on using 'patchadd' and 'patchrm' scripts provided with Solaris. Any other special or non-generic installation instructions should be described below as special instructions. The following example installs a patch to a standalone machine: example# patchadd /var/spool/patch/109715-01 The following example removes a patch from a standalone system: example# patchrm 109715-01 For additional examples please see the appropriate man pages. Special Install Instructions: ----------------------------- After installing this patch, you can choose to do the following things to allow the new driver to take effect. Option 1: Teardown all your network settings associated with the driver, unload the driver. Finally restore all network settings. 1.1. Find out all the network settings associated with the device driver. Use the following command: ifconfig -a You can redirect the output to a file to help recall how the interfaces were setup. ifconfig -a > interface.setup 1.2. Begin tearing down all the interfaces use the ifconfig command to bring down all the device interfaces and unplumb them. Use the following command. ifconfig down unplumb. You can use the 'interface.setup' file to help you identify the intefaces that need this step. 1.3. Now kill any processes that may have opened the driver directly. In these case you can use the 'ps' command to find these processes. The following command can help. ps -ef | grep With this list of process using the device you can begin to stop all of them. You may want to record the processes in a file so they can be restarted afterwards. 1.4. Once you have completely stopped everything using driver using step 1.2. and 1.3 you can now unload the driver. To do that you must first find the module id for the driver, this is done using the following command. modinfo | grep This will typically give the following oupput. 84 60ab4000 132da 143 1 device (device for doing stuff v1.18) The first number in the above line is the module id for the device driver. Now you can use that information to modunload the device driver. Using teh following command. modunload -i 85 Once the driver is unload the next time the driver is loaded it will pick up the latest driver. 1.5. Now you can begin restoring all the connections, you can use the 'interface.setup' file to help you restore the correct inet address, netmask and so on. 1.6. If possible try and restore the applications which were stopped in step 1.3. This approach will provide the minimum disruption to the usage of the system. And is a preferred alternative to a complete reboot. Option 2: Reboot the system to load newly installed driver. README -- Last modified date: Tuesday, August 31, 2004