Patch-ID# 106739-13 Keywords: 2.0 FDDI PCI Duplicate MAC address, AP 2.4, memory leak, CRC Synopsis: SunFDDI/P 2.0: Enhancements Date: Oct/03/2002 Install Requirements: Reboot after installation Solaris Release: 2.5.1 2.6 7 SunOS Release: 5.5.1 5.6 5.7 Unbundled Product: FDDI/P Unbundled Release: 2.0 Xref: Topic: Relevant Architectures: sparc BugId's fixed with this patch: 4118407 4165372 4170537 4173818 4180456 4180458 4180459 4182118 4188989 4196468 4199680 4216595 4240739 4242746 4251610 4261525 4309496 4325086 4332529 4335326 4343234 4379269 4381953 4397244 4406119 4407183 4410444 4416511 4422787 4435423 4485758 Changes incorporated in this version: 4485758 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: /etc/opt/SUNWconn/pf/bin/pf_fddidaemon /etc/opt/SUNWconn/pf/bin/pf_install_agents /etc/opt/SUNWconn/pf/bin/pf_macid /etc/opt/SUNWconn/pf/bin/pf_smtmon /etc/opt/SUNWconn/pf/bin/pf_stat /etc/opt/SUNWconn/pf/sbin/pf_snmd /etc/rc0.d/K98pf_fddidaemon /etc/rc1.d/K98pf_fddidaemon /kernel/drv/sparcv9/pf /opt/SUNWconn/pf/include/sys/pf.h /opt/SUNWconn/pf/include/sys/pfsmt.h /opt/SUNWconn/pf/man/man1m/pf_snmd.1m /opt/SUNWconn/pf/man/man7/pf.7 /etc/rc2.d/S98pf_fddidaemon /etc/rcS.d/K98pf_fddidaemon /kernel/drv/pf Problem Description: 4485758 Interrupt level 6 not serviced while trnsmitting UDP pkts via FDDI cards (from 106739-12) 4435423 pf driver passes 4 byte crc up stream (from 106739-11) 4410444 recursive mutex_enter panic on pci fddi 4407183 UE450 pf (fddi) panics when testing with ttcp 4406119 pf driver passes truncated packets to customer driver 4381953 high order bits of pcm_state of pf_stat needs to be masked 4422787 FDDI/P 2.0 patch 106739-10 is missing pfsmt.h file 4416511 FDDI driver is causing sytems panics (from 106739-10) 4397244 excessive use of the pf_stat utility causes memory leak 4379269 DR panicing on resume of pci fddi driver 4332529 memory leak in pf_addtonet() (from 106739-09) 4335326 PCI FDDI product needs changes to work with AP 2.4 and later 4309496 U80 panics with recursive mutex_enter in pf_attachreq in build02 (from 106739-08) 4343234 "Duplicate MAC address pf0" Warning on FDDI 2.0 (from 106739-07) 4325086 FDDI/P dual attach sends wrong SIF, Status Information Frames 4261525 driver fails on secondary PCIA bus (from 106739-06) 4188989 system was hanged up in shutting down with a message of FDDI, "mailbox expired". 4251610 FDDI panic during the stress test (from 106739-05) 4240739 panic in Solaris 8 4242746 panic when kmem_flags=0x1f (from 106739-04) 4216595 PF FDDI Driver panic with BAD TRAP: alignment error (from 106739-03) 4118407 ultra 30'S fddi/p hang under heavy netwrok load 4165372 LLC frames without SNAP encoding not seen at higher layer driver 4196468 LLC2 frames (X.25) not seen at higher layer driver 4199680 pf_mtu not supported by the driver (from 106739-02) 4182118 memory leak in smtfc_setup_smtrsphdr 4180456 nf_install_agents has incorrect fddi default path 4180458 nf_snmd does not work if nf0 is not present 4180459 man pages could use corrections (from 106739-01) 4170537 fddi_p 1.0 Duplicate MAC address seen on interface pf0 4173818 fddi not cognizant of AP metdevice type mnf 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/104945-02 The following example removes a patch from a standalone system: example# patchrm 104945-02 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: Thursday, October 3, 2002