AlphaServer SC patch kit: ========================== AlphaServer SC Version : SCv2.5 UK1 Kit Name(s): Tru64 CSP 1096.00 Release Date: April 10th 2003 PTR: 153-1-3737 IPMT Number: N/A You will need to build and deploy kernels and reboot all nodes to install this patch. This patch can and should be installed on the management station. Description of Patch: ===================== This patch contains changes to std_kern.mod to fix the following problems: 1. A fix for a problem with interrupt levels in the Tru64 Unix kernel's complex lock code in std_kern.mod. The most obvious symptom of a node experiencing this problem is console messages like the ones below. These can appear on any node but are most commonly seen on cluster heads or file serving nodes. 06/Mar/2003 21:15:05 06/Mar/2003 21:15:10 NOTE: icssvr_daemon_from_pool: invalid IPL 4, svc=12, op=24 06/Mar/2003 21:15:10 06/Mar/2003 21:15:11 NOTE: icssvr_daemon_from_pool: invalid IPL 4, svc=12, op=24 06/Mar/2003 21:15:11 06/Mar/2003 21:15:12 NOTE: icssvr_daemon_from_pool: invalid IPL 4, svc=12, op=24 This bug can affect any Tru64 Unix machine under high load conditions. Under these conditions a thread can return from the complex lock code in std_kern.mod with interrupts disabled. This situation can cause the thread using the lock to hang later if it goes into code that requires it to receive interrupts. These interrupts cannot be delivered. 2. A "kernel memory fault" panic in simple_lock when called by fuser. Kit checksum: ============= # cksum T64V51AB21-C0109600-17390-20030315.tar 2707779719 3891200 T64V51AB21-C0109600-17390-20030315.tar Updated files: ============== A list of the files included in this patch is given below along with the cksum values for each file. 1298156716 1690682 /sys/BINARY/std_kern.mod Prerequisites: ============== This is a UK1 patch and will not install or work on V2.5 SSB. Instructions: ============= This patch is provided as an sc_dupatch installable kit. Unpack it into a directory that is NFS mounted on all domains e.g. /nfs0/cspkit and install it as follows: On the Management Station (if Used): ----------------------------------- Install the patch using the following commands: #/usr/sbin/sc_dupatch -install -kit /nfs0/cspkit/patch_kit -name -note -noroll -nolevel2 -noauto -patch all Rebuild your kernel # doconfig -c HOSTNAME Copy the new kernel to /vmunix Reboot the machine # shutdown -r now On Domains: ----------- Install the patch using the following commands: # sra command -domains all -member 1 -command '/usr/sbin/sc_dupatch -install -kit /nfs0/CSPkit/patch_kit -name -note -noroll -nolevel2 -noauto -patch all' Now Build and Deploy the Kernels: Make sure all nodes are up so that kernels will be built on all nodes # sra command -domains all -member 1 -command 'BuildKernels' # sra command -domains all -member 1 -command 'DeployKernels' Shutdown the Domains: # sra command -domains all -member 1 -command 'shutdown -ch now' Now boot All nodes: # sra boot -domains all Installation is complete at this point. Note: ====== if you encounter a message similiar to the following : ./sys/BINARY/nfs.mod: its origin can not be identified. then rerun sc_dupatch with the -deps_only flag as follows: # /usr/sbin/sc_dupatch -install -kit /tmp/CSPkit/patch_kit -name -note -noroll -nolevel2 -noauto -deps_only -patch all A full description of -deps_only is provided below: *********************************************************** ----- Details of -deps_only option ----------------- Patches from UNIX support have previously been supplied to AlphaServer SC customers in a manual install format. That is, patches were installed by the customer running a script to copy the patch to the correct location. The standard UNIX support patches for non-SC customers have always been supplied using the CSP (Customer Specific Patch) format and are installed using the dupatch tool. Patches for SC customers are now also being provided in CSP format and these patches need to be installed using the sc_dupatch tool. sc_dupatch does some dependency checking to ensure the patches already on the machine are correct. It does this by comparing the chksums of files on the system with its own dependency list. If you have manually installed a patch that is on the dependency list for this new patch, then sc_dupatch will report an error and not install the patch. That is because sc_dupatch is not aware of patches installed manually. If sc_dupatch reports an error indicating a failure to install one or more patches, check whether this error message was generated by sc_dupatch detecting a mismatch caused by the existence of a manually installed patch. If youre satisfied that the conflict does arise from a manually-installed patch which you want to override, then a simple workaround is available in the form of the new deps_only switch. This has been introduced to cater specifically for such situations. It turns off the inventory-checking mechanism so that the pre-install checking is restricted to dependency-checking only. Simply re-run the install command with the deps_only flag to skip this inventory check and allow the installation to proceed.