Patch Name: PHKL_10023 Patch Description: s700 10.10 force EISA ENABLE bit on before driver init Creation Date: 97/02/17 Post Date: 97/02/18 Hardware Platforms - OS Releases: s700: 10.10 Products: N/A Filesets: OS-Core.CORE-KRN Automatic Reboot?: Yes Status: General Release Critical: Yes PHKL_10023: OTHER This patch affects the initial boot of a system. PHKL_7381: PANIC Path Name: /hp-ux_patches/s700/10.X/PHKL_10023 Symptoms: PHKL_10023: When an EISA card is initialized for the first time, it will be configured by eisa_config(1m) AFTER system powerup (from the bcheckrc script) unless the CFG file was loaded manually using eisa_config. If the card's driver init routine is expecting that the card's ENABLE bit has already been turned on (by the OS), then it may fail, since the bit may not be on. If this happens, then "ioscan -f" will show the card as "CLAIMED", but it will not be possible to use it. For example, if the device can be installed with insf, then insf may fail with a message such as: Cannot get ... config info from "". No such device or address If a special device CAN be created for the associated major number, then attempts to open or use it will fail. Furthermore, if the system is rebooted again, then all will be OK, since this time the card's config info is present in NVM RAM and its driver will both attach and init during system powerup. The problem will not manifest itself again, until the card is "removed" using eisa_config, and a reboot is attempted with the card in place. PHKL_7381: panic: data page fault at boot Panic is too early for dump, but pcsq.pcoq is wsio_claim() Defect Description: PHKL_10023: The defect is that under certain circumstances an EISA driver's attach and init routines can be executed before the EISA subsystem has the chance to turn on the EISA ENABLE bit on the associated EISA card. This is most likely to happen the very first time the system is brought up with the new EISA card in it. eisa_config(1m) attempts to configure and initialize any new cards that it finds in the system, and it does this in "automatic mode" (-a option) in a startup script that runs AFTER all other drivers have been brought up. If the init routine depends on the ENABLE bit being set then the driver will attach, but be unusable because the init routine failed. Here's how to recognize the presence of the defect: 1) When a new card is placed in a system which has the driver and configuration file (.CFG) already installed on it and is then rebooted, AND 2) the card attaches OK (ioscan -f shows it as CLAIMED) BUT 3) the driver is still unusable. insf may fail if the device is known to it, or an attempt to create a special file or open or read/write to the special file fails. The exact failure may be driver-specific. AND 4) when the system is rebooted, and for all subsequent reboots with the system configuration unchanged, those things that failed in 3) now work. then this defect is very likely at the root of the problem. PHKL_7381: If an EISA driver developed prior to release 10.0 is not modified for the new 10.0 I/O system, it has limited configuration support. When booting with such an unmodified driver in 10.10, the system may panic with a data page fault in the function wsio_claim(); the panic is too early to create a dump. The bug was caused by some code consolidation in 10.10, which inadvertently references a pointer that is not initialized for a pre-10.0 driver. The fix was to check said pointer before using it. SR: 1653168013 5003355727 Patch Files: /usr/conf/lib/libhp-ux.a(eisa_cdio.o) /usr/conf/lib/libhp-ux.a(etest.o) /usr/conf/lib/libhp-ux.a(wsio_cdio.o) what(1) Output: /usr/conf/lib/libhp-ux.a(eisa_cdio.o): eisa_cdio.c $Date: 97/02/17 16:37:32 $ $Revision: 1. 3.89.7 $ PATCH_10.10 (PHKL_10023) /usr/conf/lib/libhp-ux.a(etest.o): etest.c $Date: 97/02/17 16:38:53 $ $Revision: 1.8.89 .4 $ PATCH_10.10 (PHKL_10023) /usr/conf/lib/libhp-ux.a(wsio_cdio.o): wsio_cdio.c $Date: 97/02/17 16:38:56 $ $Revision: 1. 3.89.12 $ PATCH_10.10 (PHKL_10023) cksum(1) Output: 3188058327 19468 /usr/conf/lib/libhp-ux.a(eisa_cdio.o) 1637343590 15364 /usr/conf/lib/libhp-ux.a(etest.o) 3482846885 17368 /usr/conf/lib/libhp-ux.a(wsio_cdio.o) Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHKL_7381 Equivalent Patches: PHKL_10024: s800: 10.10 PHKL_10025: s700: 10.20 PHKL_10026: s800: 10.20 Patch Package Size: 110 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 PHKL_10023 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHKL_10023.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/PHKL_10023.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/PHKL_10023. 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 PHKL_10023.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/PHKL_10023.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: None