Patch-ID# 106922-17 Keywords: driver HSIP panic, netra ft 1800 u4ft mtu/mru modem RTS/DTR hsip_loop Synopsis: SunHSI/P 2.0: HSIP driver, test hardness, multiboard, loopback Date: May/02/2003 Install Requirements: Reboot after installation Solaris Release: 2.5.1 2.6 7 SunOS Release: 5.5.1 5.6 5.7 Unbundled Product: High Speed Serial Interface HSI/P Unbundled Release: 2.0 Xref: Topic: Relevant Architectures: sparc BugId's fixed with this patch: 4173271 4176340 4186226 4186274 4193089 4193100 4193106 4194442 4200727 4202343 4214838 4214841 4222405 4237476 4239146 4242959 4249891 4278066 4347266 4360574 4365776 4370937 4430419 4617096 4652929 4696699 4724279 4797381 Changes incorporated in this version: 4797381 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/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/bin/hsip_stat /opt/SUNWconn/HSIP/man/man1m/hsip_init.1m /opt/SUNWconn/HSIP/man/man7d/hsip.7d /opt/SUNWconn/bin/hsip_dump /opt/SUNWconn/bin/hsip_dump_it /platform/SUNW,Ultra-4FT/kernel/drv/HSIP /kernel/drv/HSIP Problem Description: 4797381 in case of Kernel Memory exhaustion x25 links goes down (from 106922-16) 4696699 HSIP depends on qprocsareon() (from 106922-15) 4724279 panic in freebs after canputnext failure. (from 106922-14) 4652929 HSI/P links fail due to receive overun errors. (from 106922-13) 4617096 Problem with hsi/p 2.0, need debug driver. (from 106922-12) (from 106922-11) 4430419 bad throughput with hsi/p if Sun box is receiver (from 106922-10) (from 106922-09) (from 106922-08) 4365776 system is panic on using PAD 4360574 HSIP watchdog continues to check_access once the driver has failed 4370937 customer has hsi/p 2.0 with patch 106922-07 and machine panics (from 106922-07) 4242959 hsi/p signaling is different than hsi/s 4347266 System panics with HSI 4249891 HSI/P driver 2.0 panics on debug kernels 4278066 Ultra Enterprise 300 panics with HSIP (from 106922-06) 4239146 Panic on Sheffield, ddi_dma_unbind_handle within pcc334close. 4237476 Shutdown split master to run level 2, never completed. 4222405 HSI driver not fully hardened (from 106922-05) 4214841 even with loopback=yes set at one end, ttcp over PPP works at times 4214838 mtu/mru parameters are not enforced 4193106 DTR/RTS do not become low after loop=echo is not set anymore. 4193100 hsip_loop -s 2048000 -t 4 hihp0 ignores the speed (from 106922-04) (from 106922-03) 4202343 hsip driver detects hardware fault, pppd locks up (from 106922-02) 4200727 multiple boards running port lockup and error message "cannot bind rx msgbuf" (from 106922-01) 4173271 rxc=baud/pll with sync PPP causes problems - hangs, panics or CRC errors 4176340 hsi/p driver panics system restarting sync PPP @ 1500000 bps with a bad cable 4186274 Once the TX and/or RX data lines are inverted, they cannot be non-inverted 4186226 loopback=echo does not seem to work on HSI/P 4193089 HSI/P 2.0 T patch man page could use some fixes 4194442 system panics when test harness tries to offline hsip 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 release, 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/106922-07 The following example removes a patch from a standalone system: example# patchrm 106922-07 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: Friday, May 2, 2003