|HP Tru64 UNIX: Technical Updates for the Version 5.1B and Higher Operating System and Patches > Technical Updates for the Version 5.1B and Higher
Operating System and Patches
The AlphaServer ES47/ES80/GS1280 is susceptible to minor performance penalties when the Tru64 UNIX environmental monitoring daemon (envmond) is running, or when an application uses the hwmgr command to query the attributes of a sensor in the hardware manager's device hierarchy. Also, the use of hwmgr or envmond can lead to delays in the timely servicing of interrupts.
This is most likely to be noticeable when running applications that are sensitive to increased interrupt latencies. In these cases, envmond should be looked at closely as a possible source of performance degradation until further notice (it is possible that future versions of envmond will not use hwmgr). Additionally, users with root access should avoid manually querying the hardware sensors using the hwmgr -get attr command.
Environmental monitoring on an AlphaServer GS1280 may act incorrectly if an environmental event such as a power supply or fan failure or an over-temperature condition is detected when the system is booting. When this occurs you will see the following message on your console:
In most configurations, you can ignore this message. The machine check data will have been logged into the binary error log as usual. Proceed with determining the root cause of the environmental event using the binary error log.
Each CPU on the AlphaServer ES47/ES80/GS1280 series has the capacity to handle I/O interrupts from either a locally attached I/O adapter or from another CPU that has been offlined. However, each CPU is limited to handling the I/O interrupts of two CPUs total, including its own local I/O. Therefore, on a system with X I/O hoses, the largest number of CPUs that can be offline at any one time is (X/2). Attempts to offline more CPUs will result in the following error message from psradm:
This adapter kit and cables replaces the y-cable based solution previously supported on AlphaServer DS15 systems. The following sections describe the configuation requirements for the shared SCSI bus.
See section 4.10.1 of the DS15 Owner's Guide for more information: http://h18002.www1.hp.com/alphaserver/download/ek-ds150-og-a01-web.pdf
You can use the information in the Cluster Hardware Configuration Technical Update for the 3X-KZPEA-DB Ultra3 SCSI PCI Host Bus Adapter (http://h30097.www3.hp.com/docs/updates/kzpea/TITLE.HTM) to configure the shared bus. Note that there are minor differences when configuring the Alphaserver DS15:
If this happens, you can correct the problem by unplugging the keyboard and mouse, waiting a few seconds, and reconnecting them. If this fails to correct the problem, connect the devices to a different USB port.
A sensor error can potentially indicate a false over-temperature condition on AlphaServer DS10, DS10L, and TS10 systems. While the sensor accurately reports the temperature, it falsely reports the high temperature threshold. This false reporting of the threshold value can cause the Insight Management SMP Agents to forward false traps, and potentially result in the Tru64 UNIX environmental monitoring daemon (envmond(8)) initiating the shutdown process. However, this false reporting condition is temporary and the high temperature threshold soon returns to normal, at which point the shutdown is cancelled.
To work around this problem, use the envconfig utility to manually set the high temperature threshold to its current default value. While this does not change the value, the act of setting it manually forces envmond to use the manually applied value. Once manually set, the ENVMON_HIGH_THRESH variable persists in the /etc/rc.config database. This will permanently work around the issue for current and future envmond sessions. To manually set the variable, follow these steps:
The maximum number of standard I/O hoses (IDE buses) allowed for an initial install of Tru64 UNIX Version 5.1B from the CD-ROM is eight. Any I/O drawer connected to a hose that has more than eight must be disconnected or powered down during a fresh install from the Tru64 UNIX CD-ROM.
There is a console error on XP1000 workstations that prevents you from using IDE CD-ROMs attached to the secondary port as boot devices. The secondary IDE devices are seen at the console on the XP1000 as follows:
dqa0.0.0.207.0 (master primary) dqa126.96.36.199.0 (slave primary)
dqb0.0.1.207.0 (master secondary) dqb188.8.131.52.0 (slave secondary)
During some operations of the Environmental Monitoring daemon, and the use of some hwmgr commands, these systems may experience time loss. This time loss is caused by problems with the console callbacks for environmental information.
CPUs that have I/O hoses attached to them can only be taken off line if another CPU without I/O attached is present in the system . A failure to adhere to this restriction will cause the psradm command to return an error.
With the capacity-on-demand process, the codconfig [cpu_id_list] command lets you specify which CPUs you have paid for and which are spares. The command is supposed to mark the others as spare and then take them off line. Once a CPU is marked as spare, the hwmgr command and Manage CPUs SUITLET will not let you put them on line until you use the ccod -l or ccod -p command to either loan or purchase the CPU.
The workaround to the problem is to use the codconfig [cpu_id_list] command to mark the CPUs as spare, and then use either the hwmgr command or the Manage CPUs SUITLET to take them off line (sometimes referred to as offlining them). In the following example, N is the CPU number.
SCSI errors experienced by the Adaptec controller that require SCSI bus resets could cause PCI bus faults. These faults will be seen as a “Machine Check System Uncorrectable” panic. This will require the system to be booted after the machine check. A fix for this problem will be included in a future release.
Repeated reboots of the system may cause a kernel memory fault panic, but does not result in the loss of data. A reboot after the panic should be successful. A fix for this problem will be included in a future release.
The USB keyboard driver does not support non-U.S. locales, and setting the system's language to anything other than 36 (U.S./English) causes the keyboard to be interpreted as a U.S./English keyboard anyway.
For example, on the Japanese keyboard with the SRM variable "language" set to 50 (Japanese JIS), Shift-2 produces a double quote (") character, while on the U.S./English keyboard it produces the at sign (@). With this problem, keyboards set to Japanese will produce the ampersand (&).